Skip to content
dnsmigrator

Netlify DNS Google Cloud DNS

Migrate DNS from Netlify to Cloud DNS.

9 record types move as they are. 1 things work differently at Cloud DNS, 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
  • MX
  • TXT
  • NS
  • SRV
  • CAA
  • SPF

Alias records are converted

Netlify alias records become CNAMEs below the apex. At the apex they need static addresses, and the preview shows which ones.

A typical Netlify zone at Cloud DNS

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

Netlify Cloud DNS

  • ExactA@

    192.0.2.70

  • ExactAAAA@

    2001:db8::70

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

  • ExactCNAMEwww

    example.com.

How the move works

  1. 1

    Connect Netlify

    Connect Netlify with read-only access (Personal access token).

  2. 2

    Connect Cloud DNS

    Connect Cloud DNS (Service account key (JSON)). 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 Cloud DNS

    We snapshot the Cloud DNS zone, write in batches, and leave Netlify untouched.

  5. 5

    Verify

    We query Cloud DNS'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 Netlify

  • NETLIFY and NETLIFYv6 site records are read as an ALIAS (apex) or CNAME to the site's netlify.app hostname, and we never change or delete them on Netlify.
  • Netlify DNS doesn't support DNSSEC, so turn it off at the registrar before switching nameservers.
  • Netlify has no record update endpoint, so each change is a delete followed by a create.

Access we need: A personal access token has full access to your teams. Netlify tokens can't be read-only.

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.

Questions

Will there be downtime moving from Netlify to Cloud DNS?

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

No. We never write to Netlify. 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 Cloud DNS 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