Skip to content
dnsmigrator

Google Cloud DNS LuaDNS

Migrate DNS from Cloud DNS to LuaDNS.

12 record types move as they are. 3 things work differently at LuaDNS, 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
  • PTR
  • HTTPS
  • TLSA
  • SSHFP

Routing policies are flattened

LuaDNS has no routing policies. Weighted, geo and latency sets collapse into one set of answers, and failover keeps only the primary. Each one is flagged for review.

TTLs below 60s are raised

LuaDNS's minimum TTL is 60 seconds. Shorter TTLs are raised to 60s and shown as translated.

A typical Cloud DNS zone at LuaDNS

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

Cloud DNS LuaDNS

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

How the move works

  1. 1

    Connect Cloud DNS

    Connect Cloud DNS with read-only access (Service account key (JSON)).

  2. 2

    Connect LuaDNS

    Connect LuaDNS (Account email + API key (HTTP Basic)). 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 LuaDNS

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

  5. 5

    Verify

    We query LuaDNS'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 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 LuaDNS

  • FORWARD (email forwarding), REDIRECT (web redirect) and FAILOVER records are LuaDNS features that are not read or written; recreate them in the dashboard.
  • The free plan enforces a 300-second minimum TTL and a 30-record limit; paid plans allow 60 seconds.
  • If the account uses LuaDNS Git integration, the next git build replaces API-made changes unless the zone file covers them with an ignore() rule.

Access we need: API access turned on in Settings and an API key, global or restricted to the zone. LuaDNS keys have no read-only mode, so the same key is used for preview and apply.

Questions

Will there be downtime moving from Cloud DNS to LuaDNS?

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