NextDNS rewrites Bunny DNS
Migrate DNS from NextDNS to Bunny.
3 record types move as they are. Nothing else needs special handling.
Free preview. Read-only. Nothing changes until you apply.
What works differently
Generated from the same provider capability data the migration engine uses.
Moves as-is
- A
- AAAA
- CNAME
A straightforward move.
A typical NextDNS zone at Bunny
Example records for example.com. Open any flagged row to read why it changed.
NextDNS Bunny
- ExactA@
192.0.2.70
- ExactAAAA@
2001:db8::70
- ExactMX@
10 mx1.mail.example.net. +1
- ExactTXT@
"v=spf1 include:_spf.example.net -all"
- ExactCAA@
0 issue "letsencrypt.org"
- ExactTXT_dmarc
"v=DMARC1; p=reject; rua=mailto:dmarc@example.com"
- ExactSRV_sip._tls
100 1 443 sip.example.net.
- ExactCNAMEwww
example.com.
| Status | Type | Name | At Bunny | TTL | Details |
|---|---|---|---|---|---|
| Exact | A | @ |
| 5m | |
| Exact | AAAA | @ |
| 5m | |
| Exact | MX | @ |
| 1h | |
| Exact | TXT | @ |
| 1h | |
| Exact | CAA | @ |
| 1h | |
| Exact | TXT | _dmarc |
| 1h | |
| Exact | SRV | _sip._tls |
| 1h | |
| Exact | CNAME | www |
| 1h |
How the move works
- 1
Connect NextDNS
Connect NextDNS with read-only access (API key + profile ID).
- 2
Connect Bunny
Connect Bunny (Account API key). Write access is only used when you apply.
- 3
Review the preview
Check every record marked Review or Unsupported. Each one explains what changes and why.
- 4
Apply to Bunny
We snapshot the Bunny zone, write in batches, and leave NextDNS untouched.
- 5
Verify
We query Bunny's own nameservers for every record and compare the answers before you switch.
- 6
Switch nameservers
Lower TTLs a day or two ahead, remove any DS record if DNSSEC is on, then point the domain at the new nameservers at your registrar.
Good to know about NextDNS
- NextDNS is a filtering resolver, not an authoritative DNS host: only the profile's rewrites are managed, and they answer only for devices that use that profile.
- Rewrites map a name to an IP address (A/AAAA) or another name (CNAME); MX, TXT, SRV, CAA and all other types cannot be migrated, and rewrites have no TTL setting.
- Zones are grouped from rewrite names (a rewrite for example.com also covers www.example.com rewrites); there are no nameservers to delegate to.
Access we need: The account API key (X-Api-Key). NextDNS keys cannot be scoped or made read-only, so the same key is used for preview and apply.
Good to know about Bunny
- Pull Zone, Script and Flatten records, and disabled records, aren't migrated. Redirect records are read as URL redirects to recreate by hand.
- Records that use smart routing (latency or geolocation) or CDN acceleration are flagged and never changed by us.
- An apex CNAME is flattened by Bunny, so it can point at any hostname.
Access we need: The account API key has full access. There is no read-only key, so rotate it after the migration.
Questions
Will there be downtime moving from NextDNS to Bunny?
Not if both providers serve the same answers during the switch. The records are copied to Bunny and verified before you change nameservers, so resolvers get the same answer from either side while caches expire.
Do I have to delete anything at NextDNS?
No. We never write to NextDNS. Keep the old zone for a week after cutover so you can switch back instantly if anything looks wrong.
What about DNSSEC?
If DNSSEC is on, remove the DS record at your registrar and wait for it to expire before switching nameservers. Then enable DNSSEC at Bunny and publish its new DS record. The cutover plan walks you through each step.
Ready to see your own zone?
Start a free preview