How to reduce website and email downtime when moving DNS?

Domain directory and time display linked to web and email components.
During DNS migration, web, email and verification records are checked together.

DNS migration is the preparation of domain name records in the new authoritative DNS service and the controlled change of routing. Changing the nameserver alone without checking the website, email and verification records together may affect services.

Are domain name transfer and DNS migration the same?

The domain registrar, authoritative DNS service, and web hosting may serve separate roles. Changing one does not mean that the others will necessarily change. Before starting the process, record which role is in which provider.

The organization's authorized access to the domain account, renewal status, and required approvals must be verified. Dependent access on a third party's account can make migration and repatriation difficult.

How to create a list of records to be moved?

Examine service and ownership verification records for MX, SPF, DKIM, DMARC, as well as A, AAAA, and CNAME. Check with business owners for subdomains that appear to be unused. Don't assume that automatic scanning finds every record.

Cloudflare's preparation guide explains extracting existing zone data and evaluating pre-migration records. TTL and DNSSEC dependencies, if any, should be planned according to the migration schedule.

Technical reference: Cloudflare — Preparing for DNS migration.

Does lowering TTL provide instant switching?

Previously cached responses are available for their duration. Therefore, the TTL change made at migration time does not update all queriers immediately. It is important to keep the old service accessible for a while and prepare the new region in advance.

The method of changing the authority chain in domain names using DNSSEC should be verified with the providers. Deleting records unconsciously or ignoring the old DS record may cause a validation error.

What checks are made after the change?

  • Compare results from proxy servers and different DNS resolvers.
  • Try the main and important subdomains of the website.
  • Test external email reception and sending from different applications.
  • Check that verification and service records are available on the new service.
  • Complete the monitoring and acceptance criteria without shutting down the legacy service.

Technical reference: Cloudflare — DNS traversal and verification.

With current provider and registration list domain and DNS management You can evaluate its scope.

Official sources

Technical documentation and legislation may change; The relevant version and current text should be checked before application.

Frequently Asked Questions

Will old e-mails be moved when DNS is changed?

No. DNS routing and transferring data in the mailbox are separate processes.

If the website opens, is DNS migration OK?

Email, subdomains, and other services should also be tested; Opening the home page is not enough.

Let's leave a mark together

Let's write the next chapter of your story together.

Let's Talk About Your Project
Let's Start Together