Name.com Porkbun

Migrate DNS from Name.com to Porkbun.

8 record types move as they are. 1 things work differently at Porkbun, 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

TTLs below 600s are raised

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

A typical Name.com zone at Porkbun

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

Name.com Porkbun

TranslatedA@
192.0.2.70
TTL 300s is outside the allowed range. Set to 600s.
TranslatedAAAA@
2001:db8::70
TTL 300s is outside the allowed range. Set to 600s.
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 each record at Name.com translates to Porkbun
Status	Type	Name	At Porkbun	TTL
Translated	A	@	192.0.2.70	10m
Translated	AAAA	@	2001:db8::70	10m
Exact	MX	@	10 mx1.mail.example.net. 20 mx2.mail.example.net.	1h
Exact	TXT	@	"v=spf1 include:_spf.example.net -all"	1h
Exact	CAA	@	0 issue "letsencrypt.org"	1h
Exact	TXT	_dmarc	"v=DMARC1; p=reject; rua=mailto:dmarc@example.com"	1h
Exact	SRV	_sip._tls	100 1 443 sip.example.net.	1h
Exact	CNAME	www	example.com.	1h

How the move works

1
Connect Name.com
Connect Name.com with read-only access (Username + API token (Core API, HTTP Basic)).
2
Connect Porkbun
Connect Porkbun (API key + secret API key). 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 Porkbun
We snapshot the Porkbun zone, write in batches, and leave Name.com untouched.
5
Verify
We query Porkbun'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 Name.com

Only A, AAAA, ANAME, CNAME, MX, NS, SRV and TXT records are supported (no CAA or PTR).
The minimum TTL is 300 seconds and TXT values are limited to about 512 characters.
Only domains registered at Name.com can be managed, and apex NS records follow the domain's nameservers.

Access we need: Name.com API tokens are account-wide with no read-only scope; the same token is used for preview and apply.

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.

Questions

Will there be downtime moving from Name.com to Porkbun?

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

No. We never write to Name.com. 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 Porkbun and publish its new DS record. The cutover plan walks you through each step.

Ready to see your own zone?

Start a free preview