Hundreds of DNS records to move when switching to a new DNS host
Clicking records one by one works for 10 records, not 100+. Every serious DNS host (Cloudflare, Route 53, NS1) supports zone import in BIND format and an API. With an export and a script the migration takes an hour, not a week.
Try this first
- 1Export the current zone in BIND format. For providers that do not offer it, use dig AXFR (if allowed) or a script that queries each record type.
- 2Clean the export: forgotten records you wanted to remove anyway, and SOA/NS lines that should not move.
- 3Import into the new DNS host via their import tool. Cloudflare ingests BIND, Route 53 takes JSON via CLI.
- 4Before the NS flip, compare dig @old-ns versus dig @new-ns for at least 20 key records (apex, www, mail, mx, txt bundle).
- 5Lower TTLs the day before to 300 seconds, flip NS records at the registrar, and monitor for 48 hours.
When to bring us in
If your zone has a lot of custom config (DNSSEC, dynamic records, geo routing) and you do not know BIND, we can script the migration.
See also
- Domain expires tomorrow and nobody saw the emailAn expired domain doesn't transfer instantly. There's a redemption window, but you pay extra.
- Unsure whether to enable auto-renewDisabling auto-renew only makes sense for domains you'll truly drop. For anything live, just keep it on.
- New registrar asks for auth code, can't find itEPP code or transfer code is the password to move a domain from registrar A to B.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.