Skip to content
dnsmigrator

Bunny DNS Netnod Primary DNS

Migrate DNS from Bunny to Netnod.

12 record types move as they are. 1 things work differently at Netnod, and the preview shows exactly which of your records they affect.

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
  • MX
  • TXT
  • NS
  • SRV
  • CAA
  • PTR
  • HTTPS
  • SVCB
  • TLSA

Apex CNAMEs need a different shape

Netnod doesn't allow a CNAME at the zone apex, but its ALIAS record does the same job. We convert them automatically.

A typical Bunny zone at Netnod

Example records for example.com. Open any flagged row to read why it changed.

Bunny Netnod

  • 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.

How the move works

  1. 1

    Connect Bunny

    Connect Bunny with read-only access (Account API key).

  2. 2

    Connect Netnod

    Connect Netnod (API token (Authorization: Token)). Write access is only used when you apply.

  3. 3

    Review the preview

    Check every record marked Review or Unsupported. Each one explains what changes and why.

  4. 4

    Apply to Netnod

    We snapshot the Netnod zone, write in batches, and leave Bunny untouched.

  5. 5

    Verify

    We query Netnod's own nameservers for every record and compare the answers before you switch.

  6. 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 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.

Good to know about Netnod

  • Netnod publishes no public API reference; the adapter follows Netnod's official Go client, and TTL limits are not documented.
  • Each change replaces a whole name+type set, so records disabled in the Netnod portal are dropped when that set is edited.
  • New zones get Netnod's default nameservers; zone transfer keys and NOTIFY targets must be set up with Netnod separately.

Access we need: A Primary DNS API token for the account. Netnod tokens are not split into read and write scopes, so the same token is used for preview and apply.

Questions

Will there be downtime moving from Bunny to Netnod?

Not if both providers serve the same answers during the switch. The records are copied to Netnod 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 Bunny?

No. We never write to Bunny. 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 Netnod and publish its new DS record. The cutover plan walks you through each step.

Related migrations

Ready to see your own zone?

Start a free preview