Skip to content

DNS Propagation Checker - Compare Public Resolvers

What this DNS propagation checker does

Enter a domain and record type and the tool asks five major public DNS resolvers for the same record at the same moment. It lines up their answers, tells you whether they agree, and highlights any resolver that returns something different. Each answer shows the TTL the resolver has left on its cached copy, which tells you how long it will keep serving that value.

The five are Google, three Cloudflare services and AliDNS. It does not query hundreds of ISP resolvers around the world. Those five handle a large share of DNS traffic, so if they all agree, most visitors are seeing your new record. The queries run in your browser over DNS-over-HTTPS, so results reflect the resolver nodes nearest to you.

Why DNS changes take time to appear

DNS has no push mechanism. When you edit a record, your nameservers update straight away, but resolvers that already cached the old record keep using it until its TTL expires. "Propagation" is just those caches running out one by one. A resolver that has never been asked for the name will fetch the new value immediately, which is why one resolver can show the change while another does not.

Example

Say you move example.com to a new host and change its A record from 203.0.113.10 to 198.51.100.20. The old record had a TTL of 3600. Ten minutes later, Google and AliDNS return the new address, while Cloudflare 1.1.1.1 still returns 203.0.113.10 with about 50 minutes left. The checker shows "4 of 5 resolvers agree" and highlights the Cloudflare row. Check again once that TTL has run out and all five should match.

Reading the results

Answers are compared as sets, so record order and small formatting differences between resolvers (quotes, trailing dots, letter case) are ignored. TTLs are not compared, because each cache counts down on its own. A resolver that times out or returns an error is shown as differing. For domains with very many TXT records, a resolver may return only part of the set; if just one resolver differs on a large TXT lookup and the record you changed is present, that is usually the reason. If every resolver returns NXDOMAIN, the name does not exist at all: check for a typo or a missing record at your DNS host.

Tips for a smooth change

  • Lower the TTL to 300 seconds at least one old-TTL period before the change.
  • Keep the old server running until every resolver shows the new value.
  • For MX changes, keep the old mail server accepting mail for a day.
  • Check NS records after changing nameservers at your registrar; the parent zone TTL is often 48 hours.

To see every record type for one resolver, use the DNS lookup. After moving email providers, confirm your new setup with the SPF and DMARC checker.

Related Tools

Frequently Asked Questions

How long does DNS propagation take?
It depends on the TTL of the old record. Resolvers keep serving a cached answer until its TTL runs out, so a record with a 300 second TTL updates within about five minutes and one with 86400 seconds can take a day. Nameserver changes at the registrar often take 24 to 48 hours because the parent zone uses long TTLs.
Which resolvers does this tool check?
Google Public DNS (8.8.8.8), Cloudflare 1.1.1.1, Cloudflare 1.1.1.2 (malware blocking), Cloudflare 1.1.1.3 (malware and adult content blocking) and AliDNS (223.5.5.5). These are the public resolvers that allow DNS-over-HTTPS queries from a web page.
Is this the same as checking from 100 locations worldwide?
No. Sites that show a world map query many smaller resolvers in different countries. This tool compares a handful of the largest public resolvers, which serve a big share of internet users. It tells you whether your change is live on the resolvers most people use. It is not a global survey.
Why does one resolver still show the old value?
It cached the record before you changed it. The TTL left column shows how long it will keep that copy. Wait for it to expire and check again. Cloudflare's resolvers and Google also run many separate caches, so two lookups a minute apart can briefly disagree.
Can I make propagation faster?
Lower the record's TTL to 300 seconds a day before you plan to change it. After the change, caches expire within five minutes. Google and Cloudflare also have public cache-flush pages if you need to clear a single name sooner.