Understand what changes during a DNS provider move
A DNS provider hosts the authoritative records that tell visitors and other services how to reach your domain. Moving providers usually means building a zone at the new provider and then changing the domain’s nameserver delegation through your registrar. The domain registration and the website host do not necessarily move with it. Those services may stay where they are, but their DNS records must still be present in the new zone.
The safest approach is to treat the move as a copy-and-verify project, not a chance to tidy records while changing providers. A record that looks unfamiliar could support an old but still-used application, an email service, or domain verification. If you also need to redesign the zone, make that a separate change where possible. It will be easier to identify the cause of a problem when fewer things change at once.
Make a complete inventory before editing anything
Export the existing zone if your provider offers that option, then compare the export with what appears in its DNS dashboard. Record each name, type, value, and TTL, including entries for the root domain and subdomains. Look for A and AAAA addresses, CNAME aliases, MX mail routes, TXT records, CAA restrictions, and less visible entries such as SRV records or wildcard names. Note whether a value is entered as a complete hostname or is automatically expanded by the provider.
Pay particular attention to email-related TXT records, including SPF, DKIM, and DMARC. A missing record may not stop a website from loading, so a website-only check cannot confirm that the zone is complete. Also list services configured outside ordinary DNS records, such as provider-managed redirects, traffic proxying, or dynamic DNS updates. Those features may need separate setup at the new provider rather than a copied record.
If you have access to the current provider’s zone file, handle it carefully: it may contain internal hostnames or service details. Keep account passwords, API keys, and private keys out of notes and test commands. You need record values for the migration, not credentials embedded in a checklist.
Build and check the new zone first
Create the zone at the new provider while the old nameservers remain active. Enter the inventoried records and review the provider’s defaults before relying on them. Some providers automatically add records, flatten certain aliases, or offer a proxy mode that changes how an address is returned. Match the existing behavior deliberately rather than assuming that two similarly named settings work the same way.
Where practical, query the new provider’s authoritative nameservers directly before changing the delegation. Check a representative set of names and record types: the main website name, an important subdomain, MX records, and email authentication records. Compare their answers with your inventory, including whether a name returns no record. If the new provider supplies multiple nameservers, check more than one. Direct queries let you inspect the prepared zone even though ordinary visitors are still using the old provider.
Plan the delegation and DNSSEC change together
Once the new zone is ready, update the domain’s nameservers at the registrar to the exact set assigned by the new provider. Do not remove the old zone immediately. Resolvers may continue to use previously cached delegation information for a while, so both providers should serve the intended records during the transition. Lowering record TTLs in advance can help with later record changes, but it does not instantly clear cached answers or nameserver delegation.
If DNSSEC is enabled, check how the new provider signs the zone and what DS information the registrar requires. A DS record that points to keys no longer used by the authoritative provider can make a domain fail validation. Follow the providers’ DNSSEC migration procedures and verify the registrar’s DS setting as part of the change. If your domain uses nameservers under the domain itself, check whether registrar-side glue records also need updating.
Verify the move and keep a rollback path
After updating the delegation, check which nameservers the registrar lists and compare answers from the old and new authoritative servers. Then test through ordinary DNS resolvers and use the services that matter: load the website and key subdomains, and confirm that mail can be received and sent as expected. DNS answers can differ during the transition because of caching; a single successful lookup does not prove that every resolver has switched.
Keep the old provider active until the delegation has settled and your checks show that the new zone works. Save the original record inventory and nameserver settings so you can investigate or reverse the change if needed. If a service fails, first check whether its record exists on the new authoritative servers; then examine the delegation, DNSSEC settings, and cached answers. That sequence helps distinguish a missing record from a transition that is still in progress.



