Define what is changing
A domain registrar, a DNS provider, a web host and an email provider may be four different companies. Before making changes, write down which service you intend to replace. Moving a website does not necessarily require changing nameservers; changing registrars does not necessarily require moving DNS. This distinction keeps the audit focused and helps prevent unrelated services from being disturbed.
Find the domain’s current authoritative nameservers in the registrar account and confirm where its active DNS zone is managed. An old-looking DNS dashboard may contain records that are no longer in use. If possible, compare its records with answers from the authoritative nameservers. Keep a dated copy of the current settings and note who has access to the registrar and both DNS providers. Store that inventory securely rather than placing account details or credentials in a shared document.
Inventory records by the service they support
Export the current zone if the provider offers that option, then review it manually. Record each name, record type, value and time to live (TTL). Include the root domain, www, other hostnames and any wildcard records. A and AAAA records often direct web traffic; CNAME records may connect hostnames to hosted services. Note redirects separately: a redirect configured in a provider’s web interface may not appear in a DNS export.
Give email its own checklist. Copy MX records and their priorities, along with TXT records used for SPF, DKIM and DMARC. Check for verification records required by mail platforms and other services. Also look for CAA, SRV and any less familiar record types; do not discard a record simply because its purpose is unclear. A DKIM DNS record contains a public key, but private signing keys and account passwords should never be copied into the audit.
For each record, note whether the associated service is still used and who can confirm that. The aim is not to clean up the zone during the move. Preserve uncertain records until their purpose is understood; removing unused entries can be a separate, deliberate task.
Check settings that a record export may miss
Some DNS providers offer features that do not transfer as ordinary records. Examples include root-domain aliasing, traffic rules, failover, dynamic DNS updates and provider-managed redirects. Ask whether the new provider supports the same behavior and how it represents it. A copied value is not enough if the feature behind that value changes.
Inspect delegation and security settings as well. If a subdomain has its own NS records, identify who manages that child zone and preserve the delegation. If the domain uses DNSSEC, check for a DS record at the registrar and plan how signing will work at the new provider. Changing nameservers while leaving an incompatible DS record in place can make the domain fail DNSSEC validation. Record the intended sequence before touching either setting. If nameservers use hostnames within the domain itself, also check whether registrar-managed glue addresses need attention.
Build and compare the replacement zone
Create the zone at the new DNS provider before updating nameservers at the registrar. Compare its records with the inventory line by line, paying attention to hostnames that interfaces may display differently. For example, one interface may show the full hostname while another shows only the label relative to the zone. Check that mail priorities, TXT values and IPv6 addresses have not been omitted or altered.
Where the provider allows it, query its assigned nameservers directly to check their answers before the switch. Test representative names for the website, mail and any important subdomains. This confirms what the new nameservers are prepared to serve; it does not prove that every visitor will immediately use them. If you plan to lower TTLs to ease a later change, do so ahead of time and remember that previously cached answers can remain until their original TTL expires.
Prepare for the switch and verify afterward
Keep the old DNS zone available during the transition, and avoid changing application destinations at the same time unless the move requires it. After updating nameservers, check that the registrar lists the intended nameservers and that the new authoritative servers answer for the domain. Verify a few important records again, then test the services they support: load the website, check relevant subdomains, and confirm that mail can be sent and received using safe test messages.
Different resolvers may use cached information for a while, so a single successful lookup is not a complete check. If something fails, compare the observed answer with both zone inventories and confirm which nameserver supplied it. Keeping a clear pre-change record, an unchanged old zone and a list of service owners makes problems easier to identify without guessing or exposing credentials.



