BIND zone file Vultr DNS
Import a zone file into Vultr DNS.
9 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
- CNAME
- MX
- TXT
- NS
- SRV
- CAA
- SSHFP
PTR, DS, HTTPS, SVCB, TLSA, NAPTR, LOC, CERT, URI, DHCID, DNAME, OPENPGPKEY, RP, SMIMEA aren't available
TTLs below 60s are raised
A typical Zone file zone at Vultr
Example records for example.com. Open any flagged row to read why it changed.
Zone file Vultr
- ExactA@
192.0.2.60
- 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.
- TranslatedAfast
192.0.2.61
TTL 30s is outside the allowed range. Set to 60s.
- ExactSSHFPssh
4 2 9d97e98f8af710c7e4f3b5b0b1f1b8c0c7e2a4b8c5a0e3b1f8d2c7a9b0e1f2a3
- ExactCNAMEwww
example.com.
| Status | Type | Name | At Vultr | TTL | Details |
|---|---|---|---|---|---|
| Exact | A | @ |
| 1h | |
| Exact | MX | @ |
| 1h | |
| Exact | TXT | @ |
| 1h | |
| Exact | CAA | @ |
| 1h | |
| Exact | TXT | _dmarc |
| 1h | |
| Exact | SRV | _sip._tls |
| 1h | |
| Translated | A | fast |
| 1m | |
| Exact | SSHFP | ssh |
| 1h | |
| Exact | CNAME | www |
| 1h |
How the move works
- 1
Connect Zone file
Paste or upload the zone file you want to move.
- 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 Zone file 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 Zone file
- Zone files can't express provider features like proxying, alias records or routing policies.
Access we need: No credentials. Everything stays in your browser until you choose to save it.
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 Zone file 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 Zone file?
No. We never write to Zone file. 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