What is DNS Propagation?
When you change a DNS record, the new value does not appear everywhere at once. "DNS propagation" is the delay while resolvers around the world let their cached copies of the old record expire and pick up the new one. Understanding it explains why a change you made an hour ago still is not live for everyone.
What is DNS propagation?
DNS propagation is the period during which a DNS change spreads across the network of resolvers that cache DNS data. Until every resolver's cached copy of the old record expires, some users are still served the previous value. There is no central switch that updates everyone instantly — each resolver refreshes on its own schedule.
Why propagation takes time
DNS relies on caching to stay fast and to spare authoritative servers from answering the same question millions of times. Every record carries a TTL (time to live) — the number of seconds a resolver may keep its cached answer. A record with a TTL of 3600 can be cached for up to an hour, so a resolver that fetched it ten minutes before your change keeps serving the old value for another fifty minutes.
Caches also stack. Your browser, your operating system, your router, and your ISP's resolver can each hold their own copy of a record. See DNS cache for where these live and how to clear the ones you control.
How long does DNS propagation take?
It depends on what you changed and the TTLs involved:
- Record edits (A, AAAA, CNAME, TXT, MX) — often live within minutes, and almost always within a few hours at normal TTLs.
- Nameserver (NS) or registrar changes — can take 24 to 48 hours, because TLD-level records and registry data use long TTLs and are cached aggressively.
The widely quoted "24 to 48 hours" figure is a worst case for the slowest resolvers, not a typical wait. Most changes are visible to the majority of users far sooner.
How to make changes propagate faster
You cannot speed up propagation after a change is made — the old TTL is already in flight. The trick is to plan ahead: lower the record's TTL (for example to 300 seconds) at least one full TTL interval before the change. Resolvers then hold the value for only five minutes, so the eventual switch is nearly instant. Raise the TTL back to a normal value once the change has settled.
How to check and monitor propagation
To confirm a change is live, query several resolvers in different locations — see how to check if DNS has propagated for the exact steps.
ZoneWatcher's DNS propagation monitoring watches a curated set of public resolvers for you and reports when a change has been observed everywhere, so you do not have to poll by hand.