DNS Propagation Checker

What is DNS propagation?

DNS propagation is the delay between the moment you change a DNS record and the moment every resolver on the internet starts serving the new value. When you edit a record at your DNS host, your authoritative nameserver updates instantly. But the thousands of recursive resolvers run by ISPs, public providers, and corporate networks do not query that authoritative server for every request — they keep a cached copy. Until each of those cached copies expires, users pointed at that resolver keep seeing the old value.

So propagation is not really data "spreading" across the world. It is the world's caches gradually expiring and re-fetching your record. That distinction explains almost everything about how propagation behaves — including why it is unpredictable and why you cannot force it.

Why does DNS propagation take time? (TTL)

The single most important factor is TTL — Time To Live. Every DNS record carries a TTL value, measured in seconds, that tells resolvers how long they may cache it before checking again. A record with a TTL of 3600 can be cached for one hour; a resolver that grabbed it 50 minutes ago will keep serving the old value for another 10 minutes no matter what you do.

Two things make real-world propagation slower than the TTL alone suggests:

• Caches expire at different times. Resolvers around the world fetched your record at different moments, so their caches expire on a staggered schedule rather than all at once.
• Some resolvers ignore short TTLs. A number of ISP resolvers enforce a minimum cache time and will hold a record longer than its TTL asks, which is why "full" propagation is often quoted as up to 24–48 hours even for low-TTL records.

Registrar-level nameserver (NS) changes are the slowest of all, because they also involve the top-level domain's servers and registry caches. Those are the changes most likely to take a day or two.

How long does DNS propagation take?

There is no single number — it depends on the record's TTL and the type of change. The table below gives realistic expectations for common scenarios.

Treat these as guidance, not guarantees — the honest answer is "as long as the longest cache in the path," which you cannot see directly. That is why checking across many resolvers is the only reliable way to know.

How to check DNS propagation across global resolvers

Checking from your own computer is misleading: your OS, browser, and router all cache DNS, so you might see the old value long after propagation is done — or the new value before most of the world has it. The reliable method is to query multiple independent resolvers and compare what each returns.

1. Enter your domain in the DNS Dingo checker and pick the record type you changed (A, AAAA, MX, CNAME, TXT, or NS).
2. Run the global check. DNS Dingo queries several major public DNS-over-HTTPS resolvers — including Google, Cloudflare, and Quad9 — so you see what different networks are currently returning.
3. Compare the answers. When every resolver returns your new value, propagation is effectively complete for those networks. If some still return the old value, the TTL has not fully expired there yet — wait and re-check.

travel_explore Open the Global DNS Checker

DNS propagation troubleshooting

If a change seems stuck, work through this checklist before assuming something is broken:

• Confirm the change is correct at the source. Check the record at your authoritative nameserver first — a typo there means nothing will ever propagate correctly. The DNS record lookup shows exactly what the domain is publishing.
• Flush your local cache. Run ipconfig /flushdns on Windows or sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder on macOS, then restart your browser. This clears the stale answer your own device is holding.
• Check from a resolver, not your browser. Use a global checker so you are reading real resolver caches rather than your local one.
• Wait for the old TTL, not the new one. If the old record had a 24-hour TTL, resolvers may hold it for up to 24 hours regardless of the new TTL you just set.
• For NS changes, allow up to 48 hours. Registrar and registry caches make nameserver moves the slowest kind of change.
• Still seeing the old value everywhere after 48 hours? Re-check that the record actually saved at your host, that you edited the correct zone, and that no CDN or proxy (such as a Cloudflare orange-cloud record) is overriding it.

For mail-specific propagation — confirming a Google Workspace or Microsoft 365 cutover — use the dedicated MX record lookup to see the new mail servers and their priority.