🌍 DNS Propagation Checker
Query the same DNS record from Cloudflare, Google, Quad9, and AdGuard to compare propagation and consistency.
📖 What this check tells you
A DNS change does not take effect everywhere at once. Each resolver caches the previous answer for the length of the TTL and keeps serving the old value until it expires. This check queries several public resolvers — Cloudflare (1.1.1.1), Google (8.8.8.8), Quad9, AdGuard — with the same question and compares what comes back. While the answers disagree, propagation is still in progress; it is finished once they all agree.
| Item | What it means | How to fix it |
|---|---|---|
| All resolvers agree | Every resolver queried returned the same record. Propagation is complete. | Nothing to do. Move on to verifying the switchover. |
| Some resolvers stale | Old and new values are mixed. That resolver simply still holds a live cache entry; it is not a misconfiguration. | Wait out the TTL that was in place before the change — an hour if it was 3600. If you are in a hurry, Google's Flush Cache and Cloudflare's purge tool can drop the resolver-side entry. |
| No answer anywhere (NXDOMAIN) | The record does not exist. This is not a propagation issue at all. | Check the record name in the zone editor: spelling, a trailing dot, and the subdomain depth. If the domain was just transferred, the authoritative name servers may not have switched yet, so check the NS records too. |
| TTL is very long | With a TTL of 86400 (24 hours), the next change you make will linger for a full day. | If a change is coming, lower the TTL to 300 a day or two beforehand. Put it back afterwards and your steady-state query volume is unaffected. |
Browsers and operating systems keep their own DNS caches. If every resolver agrees but your machine still sees the old value, flush the OS cache (sudo dscacheutil -flushcache on macOS, ipconfig /flushdns on Windows) and Chrome's at chrome://net-internals/#dns.