You changed a DNS record, saved it, and waited, but the old value still shows. Is the change broken, or is it simply still spreading? The DNS Propagation Checker answers that question by asking two major public resolvers, Google Public DNS and Cloudflare DNS, for the same record at the same time and showing whether they agree. If they return the same answers, the record looks consistent. If they differ, the change may still be propagating, or the domain may use location-based answers.
Propagation is one of the most misunderstood parts of running a website, because there is no single moment when a change becomes visible everywhere. Different resolvers update at different times, governed by caching rules and TTL values. This article explains what the checker shows, how to run it, how to interpret agreement and disagreement, and why a two-resolver snapshot is useful but not a complete worldwide check.
What Is the DNS Propagation Checker Tool?
The DNS Propagation Checker is a free online tool that queries the same DNS record from two public resolvers and compares the answers. You enter a domain name and choose a record type, A, AAAA, MX, TXT, NS, or CNAME, and the tool sends the query to Google Public DNS and to Cloudflare DNS (1.1.1.1), both over DNS-over-HTTPS from your browser. Each resolver result is shown separately, with its own table of Name, Type, TTL, and Value, and a comparison line states whether the two answer sets match.
DNS propagation is the process by which a changed record spreads from the authoritative name servers to the resolvers that clients actually ask. Resolvers cache records for the TTL period, so after a change, some resolvers still serve the old value until their cached copy expires, while others have already fetched the new one. During that window, different visitors can see different answers for the same domain, and different checkers can disagree, even though every part of the system is working correctly. The checker makes that window visible instead of mysterious.
The tool is explicit about its scope. Its closing note states that it checks two major public resolvers from your browser, and that full worldwide propagation checks need servers in many locations, so this is a useful snapshot, not a complete global check. That framing is important: agreement between Google and Cloudflare is a good sign, but it does not prove that every resolver worldwide has updated, and disagreement does not prove that anything is broken. The checker is a fast, honest snapshot from two viewpoints that matter, because both resolvers serve very large numbers of users.
How to Use the DNS Propagation Checker Tool
- Enter the domain name. In the “Domain name” field, type a domain without http://, for example example.com. The tool cleans pasted URLs automatically, keeping only the host name, and it accepts subdomains, so you can check the exact host name you changed.
- Choose a record type. Use the “Record type” dropdown to pick A, AAAA, MX, TXT, NS, or CNAME. Check the type you actually changed: an A record change will not show up in an MX check, and a TXT verification record must be checked as TXT.
- Press Check Propagation. The tool validates the host name, then shows that it is querying public DNS resolvers. Both queries run in parallel, so the check is usually quick.
- Read each resolver result. Results appear under two headings, one for Google Public DNS and one for Cloudflare DNS (1.1.1.1). Each section shows either a table of records or a message that no records were returned, with the status note explaining why. If one resolver query fails, that section reports the failure instead of silently omitting the resolver.
- Read the comparison line. When both resolvers answered, a line states whether they return the same answers or different answers. Same answers mean the record looks consistent across these resolvers. Different answers mean the record may still be propagating, or the domain may use location-based answers that legitimately differ by resolver location.
- Read the scope note. The closing note reminds you that this is a two-resolver snapshot, not a worldwide check. Keep that in mind before concluding that propagation is complete everywhere.
The comparison is based on the sorted answer values from each resolver, so the order in which records are returned does not cause a false mismatch. Only genuine differences in the answer values produce a “different answers” verdict. TTL values are shown in each table but do not affect the comparison, because TTLs legitimately count down at different rates on different resolvers.
Key Features of the DNS Propagation Checker Tool
- Two major resolvers side by side. Google Public DNS and Cloudflare DNS are two of the most widely used public resolvers. Checking both gives a meaningful snapshot of what a large share of internet users will see.
- Six record types. A, AAAA, MX, TXT, NS, and CNAME cover the records involved in website moves, mail setup, verification, and name server changes.
- Per-resolver detail tables. Each resolver gets its own full table with name, type, TTL, and value, so you can see exactly what differs, not just that something differs.
- Automatic comparison verdict. The tool compares the answer sets and states the conclusion in plain language, including the location-based answer possibility, so a difference is not automatically treated as a failure.
- Independent failure handling. If one resolver fails, the other result is still shown, with the failure explained in the failed section. A single resolver outage does not blank the whole check.
- Honest scope labeling. The result states that this is a snapshot from two resolvers, not a complete global check, preventing overconfidence from a single agreeing result.
Practical Use Cases
Confirming a website move
After pointing a domain to a new server, the owner checks the A record here. If both resolvers show the new address, the move has reached these major resolvers and most visitors should see the new server soon, subject to their own resolver caching. If Google shows the new address and Cloudflare still shows the old one, propagation is in progress, and the owner should wait for the old TTL to expire before investigating further. Checking again after the TTL period should show agreement.
Verifying mail and verification records
MX and TXT changes affect email delivery and service verification. A new MX record that shows on one resolver but not the other means some mail may still go to the old server, so the old server should keep accepting mail until both agree. A TXT verification record that shows on both resolvers is ready for the verification button in the other service, while a record showing on neither suggests the record was saved in the wrong zone or with a wrong host name.
Diagnosing “works for me, not for them” reports
When one person sees a new site and another sees the old one, the cause is often resolver caching rather than a browser or device problem. Showing that two major resolvers disagree demonstrates the mechanism, and the TTL values show how long the disagreement should last. The fix is usually patience, plus clearing the local DNS cache where appropriate, rather than changing the record again, which would restart the waiting period.
Checking name server changes
Changing NS records moves DNS control to a new provider, and it is the slowest change to propagate because parent-zone caching is involved. Checking the NS type here shows which name servers each resolver reports. Disagreement after an NS change can persist longer than for other types, and both sets of name servers should serve the same records during the transition so that visitors are unaffected whichever set their resolver reports.
Detecting location-based DNS answers
Some domains use GeoDNS or CDN routing that returns different addresses depending on where the query comes from. In that case, persistent disagreement between resolvers is expected and correct, not a propagation problem. The checker comparison line mentions this possibility explicitly. If the answers differ consistently long after any change, and both addresses serve the site correctly, location-based routing is the likely explanation.
Tips and Best Practices
- Lower the TTL before a planned change. Set the TTL to 300 seconds a day or two before the change, so old values expire quickly. After the change has propagated and settled, you may raise the TTL again.
- Check the exact host name and type you changed. A change to www.example.com will not appear in a check of example.com, and an A change will not appear in a TXT check. Precision here prevents false alarms.
- Wait out the old TTL before changing the record again. Editing a record repeatedly restarts confusion and can extend the inconsistent period. Make the change once, correctly, then wait.
- Keep old services running during the transition. For website moves, keep the old server serving the site, or redirecting, until propagation completes. For mail, keep the old mail server accepting mail until MX records agree.
- Use this checker with the single-resolver DNS Lookup. The DNS Lookup tool gives the detailed Google view for one type, while this checker adds the Cloudflare comparison. Together they give both depth and a second opinion.
- Do not promise visitors an exact propagation time. TTLs give a maximum wait, not a guarantee, and some resolvers and ISPs ignore low TTLs. Say “usually within a few hours” rather than naming a minute.
Limitations
The checker queries two resolvers only. The internet has thousands of resolvers, including ISP resolvers, corporate resolvers, and resolvers in many countries, and any of them can lag behind the two checked here. A worldwide propagation check requires servers in many locations, which this browser-based tool does not have. Agreement here is encouraging but not conclusive, and it should not be presented to clients as proof of global propagation.
The tool also checks one record type at a time, does not query authoritative name servers directly, and cannot distinguish a genuinely slow propagation from a resolver that is ignoring TTLs or serving a stale copy for other reasons. If one resolver query fails, no comparison is possible for that run, and the tool reports the failure rather than guessing. For critical changes, such as a major migration, complement this snapshot with checks from other locations and networks, and monitor real visitor traffic on both old and new servers during the transition.
Frequently Asked Questions
How long does DNS propagation take?
It depends on the TTL of the old record and on resolver behavior. With a 300-second TTL, major resolvers usually update within minutes, but some ISP resolvers can take hours. With a 24-hour TTL, a full day is possible. The TTL in the result is the best guide to the expected wait.
Why do the two resolvers disagree?
Usually because one still holds a cached copy of the old record while the other has fetched the new one. Location-based answers can also cause legitimate, persistent differences. Wait for the TTL period, then check again before assuming an error.
Does this tool check the whole world?
No. It checks Google Public DNS and Cloudflare DNS only, and it says so in the result. Those are two important viewpoints, but a complete global check needs many more locations. Treat agreement as a good sign, not as worldwide proof.
What should I do if the resolvers agree but I still see the old site?
Your device or browser may be caching the old address or the old page. Clear the browser cache, flush the local DNS cache for your operating system, or test in a private browsing window and from another network. Your own ISP resolver may also lag behind the two public resolvers.
Can I speed up propagation?
You cannot force resolvers to drop cached records, but lowering the TTL before a change shortens the maximum wait for future changes. Some public resolvers offer cache-flush pages, but those only affect that resolver, not the whole internet.
Why check NS records for propagation?
Because an NS change moves control of the whole zone to a new provider. Until resolvers agree on the new name servers, some visitors queries go to the old provider and some to the new one, so both must serve identical records during the transition.
Related Tools
Use these tools to investigate the records and servers behind a propagation result.
- DNS Lookup – detailed single-resolver lookup for any record type.
- Website IP Finder – list the addresses a domain resolves to.
- Website Uptime Checker – check whether the site responds on the new server.
- HTTP Header Checker – read the headers the new server sends.
- What Is My IP Address – see your own address when comparing networks.