DNS

DNS Propagation

Check DNS propagation across major global public resolvers — see whether your A, MX, TXT and other records have updated worldwide.

About DNS Propagation

Queries a domain's DNS records across 14 major public resolvers (Google, Cloudflare, Quad9 and others), showing whether they're all returning the same, current answer. DNS changes don't apply everywhere instantly — different resolvers hold cached records for different lengths of time based on TTL, and users on different ISPs can see old values for hours after a change. This tool answers whether a change has actually gone through everywhere yet, or you're only seeing it because your own resolver already picked it up. Discrepancies between resolvers point directly at which networks are still serving stale data.

The TTL that actually governs how long propagation takes is the value set before the change, not the new record's TTL — lowering TTL only helps future changes, since a resolver that already cached the old record holds it for that original duration regardless.

📖 Read more in our Knowledge Base →

Resolvers Checked

Google (x2)
Cloudflare (x2)
Quad9 (x2)
AdGuard
Alternate DNS (x2)
CleanBrowsing
Verisign
Yandex
Neustar
NextDNS

Related Tools

What this check actually tests

The tool asks 14 large public resolvers for the same record at once: Google, Cloudflare, Quad9, AdGuard, CleanBrowsing, Verisign, Yandex, Neustar, NextDNS and Alternate DNS (some with two addresses). These services are anycast: one address is served by many sites around the world, and the query is answered by the site nearest to our server. So the result shows whether the major public resolvers have the new answer, not what every country sees.

Why resolvers disagree after a change

DNS has no push. Each resolver keeps a record until its TTL expires, then asks again. A resolver that cached the old record one minute before your change keeps serving it for the full old TTL. That's why the old TTL decides how long you wait, not the new one. Read more in DNS propagation explained.

Changing a record without waiting

  1. One or two days before the change, lower the record's TTL to 300 seconds.
  2. Wait at least the old TTL so every cache picks up the short value.
  3. Make the change. Caches now expire within 5 minutes.
  4. When everything shows the new value, raise the TTL again.

If one resolver stays wrong

  • Ask your authoritative servers directly with DNS Lookup to confirm they all serve the new value. One outdated secondary nameserver will keep handing out the old answer.
  • Changed nameservers at the registrar? The parent zone's NS records have their own TTL, often 1–2 days.
  • Google and Cloudflare let you clear their cache for one name: developers.google.com/speed/public-dns/cache and one.one.one.one/purge-cache.