DNS propagation check across global resolvers

Track how quickly DNS changes are spreading worldwide after updates to A, MX, TXT, NS, and other records. This helps reduce guesswork during migrations, incident recovery, and post-change validation.

If you need record-level detail, run DNS Lookup. For domain ownership and lifecycle context, use Whois Search.

Why resolvers disagree

DNS has no push mechanism. When you change a record, nothing notifies the world's resolvers; each one simply keeps serving its cached answer until the record's TTL (time to live) expires, then fetches a fresh copy on the next query. A record published with a 3600-second TTL can therefore show the old value on one resolver and the new value on another for up to an hour, and that split is exactly what this checker makes visible. Large public resolvers such as Google and Cloudflare also run many independent cache nodes behind one IP, so even the same resolver can briefly give different answers from different locations.

Negative answers get cached too. If you queried the name before creating the record, resolvers may hold onto the "does not exist" response for the time set in the zone's SOA record. That is why a brand-new subdomain sometimes takes longer to appear than an edit to an existing one.

How to read the results

All resolvers agreeing on the new value means the change has effectively propagated. A mix of old and new values is normal mid-rollout; note which providers still show the old answer and recheck after the TTL window passes. If every resolver still returns the old value long after your TTL expired, stop waiting: the change probably never reached the authoritative nameservers, so verify you edited the zone that the domain's NS records actually delegate to.

Quick FAQ

Why do some regions update slower? Resolver cache behavior and TTL settings create staggered refresh times between providers and geographies.

Can I speed propagation up? Only in advance. Lower the TTL to 300 seconds a day before a planned change, make the change, then raise the TTL again once everything settles.

How often should I recheck? During active changes, compare snapshots every 10 to 15 minutes until results are consistently aligned.

Stuck with one resolver that never updates? Work through the DNS propagation troubleshooting checklist to isolate whether the problem is caching, delegation, or the record itself.