Google Cloud DNS NextDNS rewrites
Migrate DNS from Cloud DNS to NextDNS.
3 record types move as they are. 3 things work differently at NextDNS, and the preview shows exactly which of your records they affect.
Free preview. Read-only. Nothing changes until you apply.
What works differently
Generated from the same provider capability data the migration engine uses.
Moves as-is
- A
- AAAA
- CNAME
Routing policies are flattened
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 NextDNS
Example records for example.com. Open any flagged row to read why it changed.
Cloud DNS NextDNS
- ExactA@
192.0.2.40
- UnsupportedMX@
Not migrated
NextDNS doesn't support MX records through its API.
- UnsupportedTXT@
Not migrated
NextDNS doesn't support TXT records through its API.
- UnsupportedCAA@
Not migrated
NextDNS doesn't support CAA records through its API.
- UnsupportedTXT_dmarc
Not migrated
NextDNS doesn't support TXT records through its API.
- UnsupportedSRV_sip._tls
Not migrated
NextDNS doesn't support SRV records through its API.
- ReviewAeu
192.0.2.41 +1
Geo routing isn't available at the destination. All 2 answers are served together as simple round-robin.
- TranslatedCNAMEwww
example.com.
TTL 3600s is outside the allowed range. Set to 300s.
| Status | Type | Name | At NextDNS | TTL | Details |
|---|---|---|---|---|---|
| Exact | A | @ |
| 5m | |
| Unsupported | MX | @ | Not migrated | — | |
| Unsupported | TXT | @ | Not migrated | — | |
| Unsupported | CAA | @ | Not migrated | — | |
| Unsupported | TXT | _dmarc | Not migrated | — | |
| Unsupported | SRV | _sip._tls | Not migrated | — | |
| Review | A | eu |
| 5m | |
| Translated | CNAME | www |
| 5m |
How the move works
- 1
Connect Cloud DNS
Connect Cloud DNS with read-only access (Service account key (JSON)).
- 2
Connect NextDNS
Connect NextDNS (API key + profile ID). 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 NextDNS
We snapshot the NextDNS zone, write in batches, and leave Cloud DNS untouched.
- 5
Verify
We query NextDNS'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 NextDNS
- NextDNS is a filtering resolver, not an authoritative DNS host: only the profile's rewrites are managed, and they answer only for devices that use that profile.
- Rewrites map a name to an IP address (A/AAAA) or another name (CNAME); MX, TXT, SRV, CAA and all other types cannot be migrated, and rewrites have no TTL setting.
- Zones are grouped from rewrite names (a rewrite for example.com also covers www.example.com rewrites); there are no nameservers to delegate to.
Access we need: The account API key (X-Api-Key). NextDNS keys cannot be scoped or made read-only, so the same key is used for preview and apply.
Questions
Will there be downtime moving from Cloud DNS to NextDNS?
Not if both providers serve the same answers during the switch. The records are copied to NextDNS 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 NextDNS and publish its new DS record. The cutover plan walks you through each step.
Ready to see your own zone?
Start a free preview