Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

← All guides

Domains & DNS

DNS cutover validation: prove the new destination before and after the switch

Published August 2026 · 2 min read · Updated 2026-09-05

DNS cutover validation is the proof that authoritative nameservers, recursive resolvers, and the application all agree after a change. Checking one browser on one network is not enough because it may be using a cached answer, a local hosts entry, or a different DNS path than customers.

Validate authoritative servers first

Query every authoritative nameserver for the changed record and confirm they return the intended value, TTL, and zone serial where relevant. A mismatch between authoritative servers should be fixed before blaming public propagation.

For delegated zones, confirm the parent still points to the expected nameserver set.

Compare several recursive resolvers

Query the resolver used by your network and at least a few independent recursive services. Differences during TTL expiry can be normal; persistent differences after the old TTL window deserve investigation.

Record the exact answer and timestamp from each resolver. A generic “propagated” badge is not enough evidence.

Test the service by hostname

DNS success only proves address selection. Verify TLS certificate coverage, HTTP status, redirects, application login, forms, background jobs, mail routes, and other functions that depend on the hostname.

When a CDN or reverse proxy is involved, separately confirm the origin configuration where practical.

Define a cutover-complete threshold

Keep the source environment until authoritative data is correct, representative recursors return the new path, real traffic is reaching the destination, and changing application data is coherent.

  • Check every authority.
  • Sample independent recursive resolvers.
  • Test the actual application hostname.
  • Retain source until traffic and writes are verified.

Next step

Validate records, authoritative nameservers, TLS and the application from multiple resolvers so a DNS cutover is confirmed beyond one local cache.

Explore DotMoose domains and DNS

Keep reading

Related guides.

CAA record planning: control which certificate authorities may issue for a domain

Plan CAA records around the certificate providers you use, subdomains and incident contacts, then verify issuance will still work before enforcing restrictions.

Read the guide

CNAME chain problems: why extra DNS aliases can break or slow resolution

Trace CNAME chains, loops, missing terminal records and provider restrictions, then shorten unnecessary aliases without changing the intended hostname.

Read the guide

DKIM selector rotation: change signing keys without breaking verification

Rotate DKIM selectors by publishing the new key first, switching signers, monitoring authentication and retaining the old selector long enough for queued mail.

Read the guide

More domains & dns guides

We will handle the move. You check it first.

Your current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.

Start my free moveSee plans and prices
See pricesFree move