Why DNS Propagation Takes Time (And How to Check It)

"DNS propagation" makes it sound like a change has to physically travel around the world, spreading server by server until it reaches everyone. That's not quite what's happening — the real explanation is caching, and understanding it makes the whole process far less mysterious.

It's not propagation, it's caching expiring

When you update a DNS record, the authoritative nameserver for your domain has the new value the moment you save it. The delay isn't the new record spreading outward — it's every other resolver on the internet that already cached the old value waiting for that cached copy to expire before it asks the authoritative server again.

TTL controls how long the wait is

Every DNS record has a TTL (time-to-live), which tells resolvers how long they're allowed to keep using a cached answer before re-checking. A record with a 3600-second (1 hour) TTL means any resolver that already cached the old value won't ask again for up to an hour. A record with an 86400-second (24 hour) TTL could show stale results for a full day, even though the authoritative server has had the correct answer the entire time.

This is why experienced network engineers lower a record's TTL well in advance of a planned migration — dropping it to something like 300 seconds a day or two beforehand means that by the time the actual cutover happens, most caches have already refreshed on the short TTL, and the real change propagates (in the caching sense) within minutes instead of hours.

Different resolvers, different cache states

Because every resolver — your ISP's, your company's internal DNS, public resolvers like Cloudflare's 1.1.1.1 or Google's 8.8.8.8, and any DNS-over-HTTPS provider your browser might be using — caches independently, it's completely normal to see a new IP address from one resolver and the old one from another during the transition window. This isn't a sign anything is broken; it's every cache expiring on its own independent timer.

How to actually verify a change

Querying a domain's authoritative nameservers directly bypasses every intermediate cache and shows you the current, real answer — which is exactly what our DNS Lookup tool does. If that shows the correct new record but your own machine still resolves the old one, the difference is your local resolver's cache, not the DNS change itself, and it'll clear on its own once the TTL expires.