Enter a domain and record type to see whether a DNS change has reached the rest of the internet. The checker asks 15 public resolvers in North America, Europe and Asia, and compares each answer with what your domain’s authoritative nameservers say right now.
How to read the results
| Status | Meaning |
|---|---|
| Current | This resolver gives the same answer as your nameservers. Visitors using it see the change. |
| Old answer | It still holds a cached copy from before your change. It will ask again when the TTL shown runs out. |
| Different | Several answers came back at once. Sites on a CDN or location-based DNS give each region its own address on purpose, so this is normal for them. |
| NXDOMAIN | The resolver says the name does not exist. If you only just created it, that “does not exist” answer is cached too, for the time in your zone’s SOA record. |
| SERVFAIL | The resolver could not get a valid answer, often because of broken DNSSEC or nameservers that do not respond. |
| No reply | The resolver did not answer in time. Try again in a minute. |
The authoritative answer at the top is the truth: it comes straight from the nameservers listed for your domain. If that answer is wrong, no amount of waiting will fix it. Change the record at your DNS host first.
How long does DNS propagation take?
| Change | Usually visible everywhere within |
|---|---|
| A, AAAA, CNAME, MX or TXT record | The old record’s TTL, often 5 minutes to 1 hour |
| New record that did not exist before | Up to the SOA negative-cache time, often 1 hour |
| Nameserver change at the registrar | Up to 24 to 48 hours |
The full explanation, with the reasons each one varies, is in what is DNS propagation and how long does it take.
Why your own computer may disagree
This tool asks public resolvers directly, so it does not see the copy cached by your browser, your computer or your router. If the tool shows the new answer but your browser does not, flush your DNS cache or try another network, such as your phone on mobile data.
Make the next change faster
- A day before the change, lower the record’s TTL to 300 seconds.
- Make the change.
- Check it here. Most resolvers update within five minutes.
- Raise the TTL back to 3600 once everything shows the new answer.
Check it from the command line
dig @8.8.8.8 example.com A +short
dig @1.1.1.1 example.com A +short
dig example.com NS +short
The first two ask Google and Cloudflare. The third lists your nameservers; ask one of them directly with dig @ns1.example-dns.com example.com A to see the authoritative answer.
Questions people ask
Can I force DNS to propagate faster?
No. Resolvers keep a cached copy until its TTL runs out and nobody can reach in and clear it. You can only plan ahead by lowering the TTL before the change.
Why does the checker show the new IP but my site still shows the old one?
Your own device or network has an older copy cached, or the old server is still serving the site under the same name. Flush your DNS cache, then check the server is answering for the domain, using how to point a domain to a server.
Which resolvers does this tool use?
Google Public DNS, Cloudflare, Quad9, OpenDNS, Lumen, UltraDNS, Hurricane Electric, Comodo, Control D, DNS.WATCH, AdGuard, Yandex, KT, DNSPod and CleanBrowsing. Together they answer for a large share of the world’s internet users.
Related
- What is a nameserver?
- DNS record types explained
- How to change hosts without downtime
- SPF, DKIM and DMARC checker
Moving a site and want the DNS part done properly? Tell us what is moving and we will plan the cutover so nothing goes dark.
