Porkbun ClouDNS
Migrate DNS from Porkbun to ClouDNS.
11 record types move as they are. 1 things work differently at ClouDNS, 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
- ALIAS
- CNAME
- MX
- TXT
- NS
- SRV
- CAA
- TLSA
- SSHFP
HTTPS, SVCB aren't available
A typical Porkbun zone at ClouDNS
Example records for example.com. Open any flagged row to read why it changed.
Porkbun ClouDNS
- 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.
| Status | Type | Name | At ClouDNS | TTL | Details |
|---|---|---|---|---|---|
| Exact | A | @ |
| 5m | |
| Exact | AAAA | @ |
| 5m | |
| Exact | MX | @ |
| 1h | |
| Exact | TXT | @ |
| 1h | |
| Exact | CAA | @ |
| 1h | |
| Exact | TXT | _dmarc |
| 1h | |
| Exact | SRV | _sip._tls |
| 1h | |
| Exact | CNAME | www |
| 1h |
How the move works
- 1
Connect Porkbun
Connect Porkbun with read-only access (API key + secret API key).
- 2
Connect ClouDNS
Connect ClouDNS (API user auth ID (or sub-user ID/name) + password). 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 ClouDNS
We snapshot the ClouDNS zone, write in batches, and leave Porkbun untouched.
- 5
Verify
We query ClouDNS'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 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 ClouDNS
- TTLs must be one of ClouDNS's fixed values (60, 300, 900, 1800, 3600, 21600 … 2592000); other TTLs are rounded up.
- Web redirects (CLOUDNS_WR) are ClouDNS-only and are written as plain 301 redirects without frame options.
- The API is rate limited to about 20 requests per second per IP, so large zones apply record by record and take a while.
Access we need: A read-only API sub-user with the zones delegated is enough for the preview; applying needs a read-and-write sub-user or a main API user.
Questions
Will there be downtime moving from Porkbun to ClouDNS?
Not if both providers serve the same answers during the switch. The records are copied to ClouDNS 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 ClouDNS and publish its new DS record. The cutover plan walks you through each step.
Ready to see your own zone?
Start a free preview