Skip to content
DNSmigrator

Bunny DNS Rackspace Cloud DNS

Migrate DNS from Bunny to Rackspace.

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

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

Bunny to Rackspace DNS migration differences

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

Moves as-is

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

Apex CNAMEs need a different shape

Rackspace doesn't allow a CNAME at the apex and has no alias record for external hostnames. These become static A/AAAA records, which don't follow the target if its IPs change.

TTLs below 300s are raised

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

A typical Bunny zone at Rackspace

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

Bunny Rackspace

  • ExactA@

    192.0.2.70

  • ExactAAAA@

    2001:db8::70

  • ExactMX@

    10 mx1.mail.example.net. +1

  • ExactTXT@

    "v=spf1 include:_spf.example.net -all"

  • UnsupportedCAA@

    Not migrated

    Rackspace doesn't support CAA records through its API.

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

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

  2. 2

    Connect Rackspace

    Connect Rackspace (Cloud account username and 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 Rackspace

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

  5. 5

    Verify

    We query Rackspace'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

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

Good to know about Rackspace

  • Apex NS and SOA records are managed by Rackspace and can't be changed.
  • PTR records are only managed through Rackspace's reverse-DNS API for its own cloud devices, so they aren't migrated.
  • TTLs below 300 seconds are raised to 300.
  • Rackspace removes quote and backslash characters from TXT data.
  • Changes run as asynchronous Rackspace jobs; we wait for each job to finish, so large plans take longer.
  • New domains use the connection's SOA contact email, or hostmaster@<domain> when none is set.
  • Subdomains that Rackspace hosts as separate domains are listed as their own zones.

Access we need: Use a dedicated account user with the DNS Admin product role (dnsaas:admin). DNS Creator can't delete records, and DNS Observer is read-only, which is enough for a source connection.

Questions

Will there be downtime moving from Bunny to Rackspace?

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