Domains & DNS
Domain nameserver migration: move DNS hosting without dropping records
Published August 2026 · 2 min read · Updated 2026-09-05
A nameserver migration changes who is authoritative for an entire DNS zone. That can affect websites, email, verification records, subdomains, APIs, and third-party services simultaneously, so the safe sequence is copy, compare, delegate, observe, and only then retire the old DNS service.
Inventory the current authoritative zone
Export or query A, AAAA, CNAME, MX, TXT, CAA, SRV, subdomain delegations, DKIM selectors, DMARC, SPF, verification tokens, and any wildcard records. Record TTLs and DNSSEC state.
Check for provider-specific synthetic records or flattening that may not copy literally.
Build the new zone before delegation
Create equivalent records at the new DNS provider and query its authoritative servers directly before the registrar nameserver change. Make sure mail and service-specific records were not omitted because they are invisible on the homepage.
If DNSSEC is active, coordinate DS/signing according to the old/new provider procedures.
Change delegation without deleting the source
Update nameservers at the registrar/registry and monitor parent delegation plus recursive answers. Keep the old zone serving the same data through the cache/registry transition.
Avoid changing website IPs at the same moment unless there is a strong reason; one change at a time is easier to validate.
Retire only after public convergence
Verify multiple resolvers, web, mail, subdomains, API endpoints, and certificate renewal paths. Remove the old zone only when it is no longer authoritative or receiving meaningful queries.
- Export the complete zone.
- Prebuild/test the new authority.
- Coordinate DNSSEC.
- Keep old DNS through the transition.
Next step
Copy the zone, compare authoritative answers, lower risk before delegation changes and keep the old DNS service available until the new nameservers are proven.
Explore DotMoose domains and DNS