Google Cloud DNS Rackspace Cloud DNS
Migrate DNS from Cloud DNS to Rackspace.
7 record types move as they are. 2 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.
Cloud DNS 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
CAA, PTR, DS, HTTPS, SVCB, TLSA, SSHFP, NAPTR aren't available
TTLs below 300s are raised
A typical Cloud DNS zone at Rackspace
Example records for example.com. Open any flagged row to read why it changed.
Cloud DNS Rackspace
- ExactA@
192.0.2.40
- 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.
- ReviewAeu
192.0.2.41 +1
Geo routing isn't available at the destination. All 2 answers are served together as simple round-robin.
- ExactCNAMEwww
example.com.
| Status | Type | Name | At Rackspace | TTL | Details |
|---|---|---|---|---|---|
| Exact | A | @ |
| 5m | |
| Exact | MX | @ |
| 1h | |
| Exact | TXT | @ |
| 1h | |
| Unsupported | CAA | @ | Not migrated | — | |
| Exact | TXT | _dmarc |
| 1h | |
| Exact | SRV | _sip._tls |
| 1h | |
| Review | A | eu |
| 5m | |
| Exact | CNAME | www |
| 1h |
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
Connect Cloud DNS
Connect Cloud DNS with read-only access (Service account key (JSON)).
- 2
Connect Rackspace
Connect Rackspace (Cloud account username and 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 Rackspace
We snapshot the Rackspace zone, write in batches, and leave Cloud DNS untouched.
- 5
Verify
We query Rackspace'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 Cloud DNS
- Routing policies (weighted round robin, geolocation, failover) don't carry over to most providers.
- Apex CNAMEs are not allowed.
Access we need: roles/dns.reader for the preview, roles/dns.admin to apply.
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 Cloud DNS 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 Cloud DNS?
No. We never write to Cloud DNS. 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.
Ready to see your own zone?