Skip to content
dnsmigrator

Porkbun Google Cloud DNS

Migrate DNS from Porkbun to Cloud DNS.

12 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
  • TLSA
  • SSHFP
  • HTTPS
  • SVCB

Alias records are converted

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

A typical Porkbun zone at Cloud DNS

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

Porkbun 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 Porkbun

    Connect Porkbun with read-only access (API key + secret API key).

  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 Porkbun 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 Porkbun

  • API Access must be turned on per domain, and only domains registered at Porkbun can be managed.
  • The minimum TTL is 600 seconds and a zone holds at most 2,500 records.
  • URL forwarding is not migrated; the ALIAS/CNAME records Porkbun creates for it are copied as plain records.

Access we need: Porkbun keys have no read-only mode. Restrict the key to the domains you move and turn on API Access for each of them.

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 Porkbun 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 Porkbun?

No. We never write to Porkbun. 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