DNS Propagation Checker
Check whether the change you made to your DNS records has reached popular resolvers like Google, Cloudflare and Quad9.
Compared with the current record
Each server's answer is compared with the current record on the domain's authoritative server. Servers that differ are still holding the old record in their cache.
TTL and caching
DNS servers keep a record in their cache for its TTL. When the record changes, a server holding the old one picks up the new record once that time runs out.
Popular public DNS servers
Google, Cloudflare, Quad9, OpenDNS, AdGuard, Yandex and other widely used public DNS servers are queried at the same time.
What is DNS propagation?
DNS propagation is the process of a change to a DNS record reaching DNS servers across the internet. The change takes effect on the authoritative server immediately, but public DNS servers such as Google and Cloudflare keep the old record cached until its TTL runs out and keep returning the old answer until then.
The tool compares the current record on your domain's authoritative server with the answers of 16 public DNS servers, including Google, Cloudflare, Quad9, OpenDNS and AdGuard. It shows each server's answer, the time left in its cache and whether it is up to date, and works out when servers holding the old record will refresh at the latest.
How to use
- 1Enter the domain and choose the record type (A, AAAA, CNAME, MX, NS or TXT).
- 2Press Check.
- 3If some servers give a different answer, look at the time left in their cache; the new record appears once it runs out.
Frequently asked questions
How long does a DNS change take to take effect?
The old TTL of the record decides: if the TTL was 3600 seconds, the change reaches all servers within an hour at the latest. For nameserver changes, the TTL at the top-level domain (TLD) is usually one or two days, so it can take 24-48 hours.
Is there a way to speed up the change?
You cannot remotely clear an old record from a cache. If you lower the TTL to a small value such as 300 seconds a few days before a planned change, the old record stays cached for at most five minutes when you make it. You can clear the DNS cache on your own computer (ipconfig /flushdns on Windows).
Some servers give a different answer. Is that a problem?
If you have just changed the record, it is normal; those servers keep returning the old record until their cache expires. For domains that answer by location, such as Google or CDNs, it is expected that each server gets a different but valid address.
Are the servers queried from different parts of the world?
No. The queries are made from our server. Most of these public DNS servers use anycast, so the data centers closest to us answer; the results show how your record looks in the caches of these popular servers.
Why are Turkish operators' DNS servers not on the list?
The DNS servers of operators such as Türk Telekom, Turkcell and Vodafone only answer queries from their own subscribers, so they cannot be queried from outside. They pick up changes by the same rule, when the TTL of the old record runs out.