Vercel DNS Vultr DNS

Migrate DNS from Vercel to Vultr.

8 record types move as they are. 2 things work differently at Vultr, 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
CAA
CNAME
MX
NS
SRV
TXT

Alias records are converted

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

HTTPS isn't available

Vultr can't store HTTPS records through its API. They're marked Unsupported with the reason, never dropped silently.

A typical Vercel zone at Vultr

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

Vercel Vultr

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 each record at Vercel DNS translates to Vultr DNS
Status	Type	Name	At Vultr	TTL
Exact	A	@	192.0.2.70	5m
Exact	AAAA	@	2001:db8::70	5m
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 Vercel
Connect Vercel with read-only access (Access token (+ team ID)).
2
Connect Vultr
Connect Vultr (API key (personal access token)). 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 Vultr
We snapshot the Vultr zone, write in batches, and leave Vercel untouched.
5
Verify
We query Vultr'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 Vercel

Records Vercel adds for project domains (such as the apex ALIAS and CAA) are read with a comment and never changed by us. Edit them in the project's domain settings.
Domains must already be added to the Vercel account or team. We can't create them.
Vercel DNS doesn't support DNSSEC, and the minimum TTL is 60 seconds.

Access we need: An access token scoped to the team that owns the domains. Vercel tokens can't be read-only.

Good to know about Vultr

Vultr API keys can't be limited to read-only, so use a dedicated user that only has the Manage DNS permission.
If API Access Control is enabled, requests from IP addresses that aren't on the allow-list are rejected.
TXT values can't contain double quotes.

Access we need: A user with the Manage DNS permission for both preview and apply. Vultr keys have no read-only mode.

Questions

Will there be downtime moving from Vercel to Vultr?

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

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

Ready to see your own zone?

Start a free preview