Domain Propagation

Domain propagation is how a DNS change reaches visitors, not a single switch that updates every system at once. When you swap nameservers or an A record, resolvers across networks stop using their stale copies at different times, so some people see the new site while others still see the old one.

Why it spreads gradually

Resolvers and ISPs cache DNS answers for the record's TTL. If the old TTL was 86400, a resolver may hold the previous value for up to 24 hours even after you changed it at the origin. Delegating to new nameservers usually moves slower than editing one record, because resolvers also cache the NS and glue data.

So there is no single duration for propagation. Your origin server can already answer correctly while a visitor whose cache has not expired is still sent to the old IP address. That is caching, not broken hosting.

Checking across resolvers

Run dig +trace example.com to follow authority from the root down to your zone. To compare caches, query different public resolvers:

dig A example.com @8.8.8.8
dig A example.com @1.1.1.1
dig A example.com @9.9.9.9

Different answers mean some resolvers have not expired yet. Aggregator sites check many locations at once, but dig from a terminal gives the most honest read.

Testing the new server early

You can verify the destination before pointing the public at it. Add a line 1.2.3.4 example.com to your device's hosts file, or send the Host header manually. On Windows the hosts file sits in C:\Windows\System32\drivers\etc\hosts, on Linux in /etc/hosts. Remove the line afterward so you do not pin a stale IP.

Flush your local cache after a change: ipconfig /flushdns on Windows, sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder on macOS, resolvectl flush-caches on Linux.

What to watch

Do not change nameservers twice in a row; each change restarts the cache cycle. If you are also moving email, keep the MX records pointed correctly so mail does not misfire. A proxy or Cloudflare adds its own cache layer, so new content needs a purge there, not just a DNS edit. During a hosting migration, confirm the destination server is live before you steer DNS to it. DNS propagation is also different from a domain transfer: a transfer moves registrar records and can take days, while propagation is only caches expiring.

FAQ