DNS Propagation
Query Cloudflare, Google, Quad9 and OpenDNS in parallel.
DNS propagation for serversaurus.com.au
| Resolver | A records |
|---|---|
| Cloudflare 1.1.1.1 | 103.209.24.199 |
| Google 8.8.8.8 | 103.209.24.199 |
| Quad9 9.9.9.9 | timeout or non-json |
| OpenDNS | timeout or non-json |
Unique IPs seen: 103.209.24.199
About DNS Propagation
This tool queries four major public DNS resolvers in parallel for the same A record, then compares the answers. The four resolvers (Cloudflare 1.1.1.1, Google 8.8.8.8, Quad9 9.9.9.9, OpenDNS) each operate large global anycast networks with independent caches, so consistency across all four is a strong signal that your DNS change has propagated. Divergence means at least one resolver still serves a cached older value.
When to use it
Run this immediately after pointing your domain at a new server or CDN. The faster the resolvers converge on the new IP, the faster real users see your changes. Use it during a migration window to know when it is safe to decommission the old origin. Web hosting providers also use it to confirm that recent NS or A changes have reached the major resolver networks.
How to read the results
All four resolvers returning the same IP is the success signal. If three match and one differs, the divergent resolver is still serving from cache, which usually clears within the original TTL. Resolvers reporting timeouts or errors typically mean the authoritative nameservers are slow or filtering the query. Persistent divergence after the TTL window points to a configuration error on the authoritative side.
Frequently asked questions
How long does propagation usually take? ▾
It depends on the previous TTL. If the old record had a TTL of 300 seconds, most resolvers update within five minutes. A 24 hour TTL means full propagation can take a day. Reduce TTLs to 60 or 300 seconds 24 hours before any planned change.
Why does only one resolver show the old IP? ▾
That resolver's cache has not yet expired. It will refresh on the next query after the cached entry ages out. You can verify by waiting a few minutes and re-running the check, or by querying that resolver directly with dig @1.1.1.1 yourhostname.
Does this tool query my local DNS too? ▾
No. Local resolvers, including your ISP and your home router, are not part of the public query. Their behaviour is independent. You can clear local caches by restarting your network interface or running ipconfig /flushdns on Windows.
What if all four resolvers fail? ▾
All four failing usually means the authoritative nameservers for your domain are unreachable or returning errors. Verify the NS records are correct, your DNS provider is up, and the zone is active. Try the DNS lookup tool to query directly.