Porkbun Hurricane Electric DNS
Migrate DNS from Porkbun to Hurricane Electric.
12 record types move as they are. 1 things work differently at Hurricane Electric, and the preview shows exactly which of your records they affect.
Free preview. Read-only. Nothing changes until you apply.
Porkbun to Hurricane Electric DNS migration differences
Generated from the same provider capability data the migration engine uses.
Moves as-is
- A
- AAAA
- ALIAS
- CNAME
- MX
- TXT
- NS
- SRV
- CAA
- SSHFP
- HTTPS
- SVCB
TLSA, PORKBUN_URLFWD aren't available
A typical Porkbun zone at Hurricane Electric
Example records for example.com. Open any flagged row to read why it changed.
Porkbun Hurricane Electric
- 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 Hurricane Electric | 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 |
Set up the connections
Use the provider-specific credential guides before you preview, then keep the migration checklist beside the cutover plan.
How the move works
- 1
Connect Porkbun
Connect Porkbun with read-only access (API key + secret API key).
- 2
Connect Hurricane Electric
Connect Hurricane Electric (Account username + password (+ TOTP)). 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 Hurricane Electric
We snapshot the Hurricane Electric zone, write in batches, and leave Porkbun untouched.
- 5
Verify
We query Hurricane Electric'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 forwards are migrated as PORKBUN_URLFWD records (301, 302, 307 or masked, with path and wildcard options). Porkbun gives them no TTL, so they read back with the 600-second default.
- Remove records that conflict with a forward at the same name first, as Porkbun requires; the ALIAS/CNAME records it creates for forwarding 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 Hurricane Electric
- Dynamic DNS records keep their own update keys, which can't be read back and must be set again after a move.
Access we need: Hurricane Electric has no API keys or scoped roles; access means full control of the whole account.
Questions
Will there be downtime moving from Porkbun to Hurricane Electric?
Not if both providers serve the same answers during the switch. The records are copied to Hurricane Electric 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 Hurricane Electric and publish its new DS record. The cutover plan walks you through each step.
Ready to see your own zone?