DNS Migration Planner

Build a migration inventory

Name: @ for the domain, www for a subdomain, or a full name ending in a dot. Targets must be full hostnames. Blank proposed value keeps the current value; “-” means absent (new record or deletion). Enter TXT content without surrounding quotes.

Review and export

These are partial BIND-style record imports, not a complete authoritative zone. SOA, NS, CAA, SRV, DNSSEC and proxy settings are not generated. Nothing is looked up, uploaded, saved or applied to a provider.

Before you change traffic

1. Export the complete current DNS zone and keep account access before making changes. This workbook covers only entered A, AAAA, CNAME, MX and TXT records.
2. Inventory email MX, SPF, DKIM and DMARC, plus verification, CAA, SRV, delegated subdomains and any other records. Preserve unsupported record types separately.
3. Lower relevant TTLs at the current provider in advance, then wait at least their previous TTL. A new export alone does not lower a cached TTL.
4. Prepare the new hosting, copy files/databases and configure TLS. Test the origin before changing traffic. Plan a final data sync or maintenance window for sites with writes.
5. Import proposed records into the destination provider and compare every record. Leave proxying off unless deliberately configured for supported web records; mail hostnames must remain DNS-only.
6. If changing authoritative nameservers, coordinate DNSSEC and DS records with both providers and the registrar. Do not copy old DNSSEC keys or remove DS records on assumptions.
7. Change only the intended records or delegation. Check authoritative responses, website/TLS, forms, login and inbound/outbound email from external networks. This local tool cannot perform those checks.
8. Keep old hosting and DNS available while caches expire. If checks fail, restore the original records/delegation from verified backups; rollback is also subject to caching. Raise TTLs after the migration is stable.