Cloud platformDNS hostingCapabilities verified
Rackspace Cloud DNS
Migrate DNS zones to or from Rackspace Cloud DNS: what's supported, what access you need, and what changes for each destination.
See how a domain's records would land at Rackspace. Free and read-only.
Access we need
- Credentials
- Cloud account username and API key
- Permissions
- 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.
What Rackspace supports
The same data the translation engine uses when it plans a migration.
- Create zones through the API
- List zones through the API
- Turn on DNSSEC through the API
- Apex CNAME (flattening)
- Apex ALIAS record
- Aliases to cloud resources
- CDN proxy on records
- Routing policies
- Minimum TTL
- 300s
Record types
- A
- AAAA
- CNAME
- MX
- NS
- SRV
- TXT
Good to know
- 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.