Google Cloud DNS UltraDNS (DigiCert)
Migrate DNS from Cloud DNS to UltraDNS.
16 record types move as they are. Nothing else needs special handling.
Free preview. Read-only. Nothing changes until you apply.
Cloud DNS to UltraDNS 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
- SPF
A straightforward move.
A typical Cloud DNS zone at UltraDNS
Example records for example.com. Open any flagged row to read why it changed.
Cloud DNS UltraDNS
- ExactA@
192.0.2.40
- 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.
- 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 UltraDNS | TTL | Details |
|---|---|---|---|---|---|
| Exact | A | @ |
| 5m | |
| Exact | MX | @ |
| 1h | |
| Exact | TXT | @ |
| 1h | |
| Exact | CAA | @ |
| 1h | |
| 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 UltraDNS
Connect UltraDNS (API user name and password (OAuth password grant)). 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 UltraDNS
We snapshot the UltraDNS zone, write in batches, and leave Cloud DNS untouched.
- 5
Verify
We query UltraDNS'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 UltraDNS
- Traffic-management pools (SiteBacker, Traffic Controller, Directional and Simple Load Balancing) are copied as plain answers and flagged; we never change or delete them on UltraDNS.
- Resource Distribution pools keep their pool settings when we update their answers.
- ALIAS is written as UltraDNS Apex Alias, which only works at the zone apex, can't coexist with both A and AAAA at the apex, and can't be used in statically signed zones.
- SOA, apex NS and system-generated records (such as Valimail DMARC records) are managed by UltraDNS and left untouched.
- Web Forwards and secondary or alias zones aren't migrated; secondary and alias zones are read-only.
- UltraDNS locks an account after repeated failed logins, so double-check the password before retrying.
Access we need: Create a dedicated API-only user in a group limited to DNS operations (the built-in TECHNICAL group, or a custom group with DNS read and write). A REPORTING or ungrouped user is enough for a read-only preview. The REST API doesn't support multi-factor login, so MFA must be off for this user.
Questions
Will there be downtime moving from Cloud DNS to UltraDNS?
Not if both providers serve the same answers during the switch. The records are copied to UltraDNS 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 UltraDNS and publish its new DS record. The cutover plan walks you through each step.
Ready to see your own zone?