DNS Propagation Checker
See whether a DNS change is live: we ask your domain's authoritative nameservers directly and compare their answer with three major public resolvers.
What this tool checks
“Propagation” is the common name for the time it takes until everyone sees a DNS change. Strictly speaking, DNS changes do not spread outwards: they are published once on your authoritative nameservers, and every resolver keeps serving its cached copy of the old record until the record’s TTL (time to live) expires. Then it fetches the new one.
This tool shows both sides of that process for one name and record type:
- Your authoritative nameservers. We find the nameservers of the zone and query up to four of them directly, using DNS over TCP to the server’s IPv4 address. This answer is what you have actually published: the source of truth.
- Three public resolvers: Cloudflare (1.1.1.1), Google Public DNS (8.8.8.8) and Quad9 (9.9.9.9), queried over DNS over HTTPS. These answers show what large numbers of internet users may currently receive, including cached old values.
All queries are sent from our server; your own IP address is never passed to these servers.
An honest note about locations
Many propagation checkers show a map with servers in dozens of countries. Large public resolvers are anycast networks: the same address is answered by whichever of hundreds of sites is closest to the query, and each site has its own cache. Because our queries come from a single platform, we see the cache of the site closest to our server, not a worldwide sample. What we can tell you reliably is whether your authoritative servers publish the right data, whether they agree with each other, and whether three of the most used resolvers have picked it up.
How to read the result
The result has two tables:
| Column | Meaning |
|---|---|
| Server | The resolver or the authoritative nameserver (with the IP queried). |
| Status | NOERROR, NXDOMAIN, SERVFAIL or a connection error. |
| Values | The records returned, sorted so they can be compared. |
| TTL | For resolvers, the time left in their cache. For authoritative servers, the full TTL you configured. |
| Time | How long the query took. |
At the top, a summary tells you whether all answers match. Typical situations:
- Everything matches. The change is live and the three resolvers already have it.
- Authoritative servers show the new value, resolvers the old one. The change is published; resolvers will update when their TTL runs out.
- Authoritative servers still show the old value. The change has not been saved or published. Check your DNS provider’s panel, and check that the domain uses the nameservers you think it does (see the NS lookup).
- Authoritative servers disagree with each other. A secondary server is out of date. Compare SOA serials by running the check with type SOA.
- An authoritative server times out. It may be down, blocking TCP on port 53, or not configured for the zone (a lame delegation).
Some nameservers are hosted on Cloudflare’s own network, which our platform cannot reach with a direct connection. For those we use an alternative route and mark the row accordingly.
Common problems and fixes
- Planning a change. Lower the TTL of the record to 300 seconds at least one full old TTL before the change. After the change, raise it again.
- Waiting for a nameserver change. The delegation is cached according to the TTL set by the TLD registry, often 86400 seconds or more. Keep the old provider serving correct records until the change is complete.
- A resolver keeps an old value long after the TTL. Check that you are comparing the right name and type, and that no CNAME at a higher level is involved. Use the CNAME checker to follow aliases.
- A newly created name shows NXDOMAIN on resolvers. They may have cached the non-existence from an earlier query. That negative cache is limited by the zone’s SOA minimum value.
- SERVFAIL everywhere after moving DNS provider. If the domain uses DNSSEC, the DS record at the registrar may still match the old provider’s key. See DS and DNSKEY.
Related
- DNS lookup: query one resolver with full details and a dig-style view.
- NS record guide: delegation, glue and lame servers.
- SOA record guide: serial numbers and negative caching.
- A record guide: planning address changes with low TTLs.
Frequently asked questions
Why don't you show servers in dozens of countries?
Because it would not mean much. Cloudflare, Google Public DNS and Quad9 are anycast networks: one address is served from hundreds of locations, each with its own cache. A list of 'servers in 30 countries' usually samples a few such networks and smaller resolvers. We prefer to show the authoritative answer, which is the source of truth, next to the three largest public resolvers.
How long does DNS propagation take?
There is no fixed time. A changed record reaches everyone once the old record's TTL has expired in every cache that holds it. With a TTL of 300 seconds that is about five minutes; with 86400 it can be a day. Nameserver changes depend on the TTL of the delegation at the TLD, often one or two days.
The authoritative nameservers show the new value but a resolver shows the old one. What do I do?
Wait. The resolver will refresh when its cached copy expires; the TTL column shows roughly how long that will take. Some public resolvers offer a cache purge page if you need it sooner.
My nameservers disagree with each other. Why?
One of them has an outdated copy of the zone. Look up the SOA record on each: a lower serial number identifies the server that has not synchronised. Contact your DNS provider if it persists.