Skip to content
DNSmigrator

Constellix DNS Bunny DNS

Migrate DNS from Constellix to Bunny.

9 record types move as they are. 3 things work differently at Bunny, and the preview shows exactly which of your records they affect.

Free preview. Read-only. Nothing changes until you apply.

Constellix to Bunny DNS migration differences

Generated from the same provider capability data the migration engine uses.

Moves as-is

  • A
  • AAAA
  • CNAME
  • MX
  • TXT
  • NS
  • SRV
  • CAA
  • PTR

Alias records are converted

Constellix alias records become CNAMEs at Bunny. At the apex, Bunny flattens them automatically.

TTLs below 60s are raised

Bunny's minimum TTL is 60 seconds. Shorter TTLs are raised to 60s and shown as translated.

A typical Constellix zone at Bunny

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

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

Set up the connections

Use the provider-specific credential guides before you preview, then keep the migration checklist beside the cutover plan.

How the move works

  1. 1

    Connect Constellix

    Connect Constellix with read-only access (API key + secret key (HMAC-signed requests)).

  2. 2

    Connect Bunny

    Connect Bunny (Account API key). 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 Bunny

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

  5. 5

    Verify

    We query Bunny'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 Constellix

  • Records using failover, traffic pools, IP filters, GeoProximity or regional answers are flagged and never changed by us; only the default answer is copied.
  • HINFO records and DNSSEC aren't available through the Constellix v4 API.
  • HTTP redirection records map to URL forwards for the whole hostname (301, 302 or frame); page title and keywords of frame redirects aren't copied.
  • CAA records only support the issue, issuewild and iodef tags.
  • Requests are signed with the current time, so the server clock must be accurate.

Access we need: Constellix API keys carry the permissions of the user who generated them and can't be limited to read-only. Generate them under a user that only manages the domains you're moving.

Good to know about Bunny

  • Redirect records (BUNNY_DNS_RDR) and Pull Zone records (BUNNY_DNS_PZ, by pull zone ID) are migrated. Script and Flatten records, and disabled records, aren't.
  • A Pull Zone record only works if the pull zone ID exists in the destination bunny.net account.
  • 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 Constellix 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 Constellix?

No. We never write to Constellix. 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.

Related migrations

Ready to see your own zone?

Start a free preview