DNS Propagation: How Long It Takes and Why Results Differ by Location
How long does DNS propagation take? Learn why record changes appear at different times worldwide, what TTL and caching do, and how to speed it up.
Check my DNS records instantly: see whether your changes are live worldwide. Test A, AAAA, CNAME, MX, NS, TXT and more against 60 public resolvers on every continent, with TTLs, response times and a live map.
60 public resolvers in 47 countries answer your query directly, and nothing is cached on our side. Enter a domain above, or try an example:
Querying 60 resolvers…
CheckMyDNS sends your query straight to public recursive resolvers across North America, Europe, Asia, Africa, South America and Oceania, then shows what each one answers right now.
Type a domain or hostname such as example.com or mail.example.com. For reverse DNS, enter an IP address and choose PTR.
Choose A for websites, MX for email, NS after a nameserver change or TXT for SPF, DKIM and verification records. Add an expected value to match against.
Green means a resolver returns the new value, amber means a different answer is still cached, and red means no answer. Share the link or export to CSV.
The phrase covers two different jobs, and the right tool depends on which one you're after.
You own a domain and just changed where it points: a new hosting IP, a new mail provider, a new set of nameservers. You want to know whether the rest of the internet has noticed. That's what the checker at the top of this page does: it asks resolvers worldwide and shows you every answer.
Your website loads slowly, a page says “server not found”, or you've just switched to a privacy-focused resolver and want proof it worked. That's about the resolver your own computer, phone or router talks to, and you can read it straight off the device in under a minute.
Built for sysadmins, developers and site owners who need to know exactly where a change has landed, and where it hasn't.
Google, Cloudflare, Quad9, regional ISPs and national resolvers. Every result tells you who answered and from where.
See the remaining cache TTL and how fast each resolver replied, so you know when stale answers will expire.
Tell us the new value and every location is checked against it, so there is no more eyeballing long lists of IPs.
Leave the page open and CheckMyDNS re-checks every 30 seconds, updating the map as resolvers pick up your change.
Every check has its own link (send it to a client or teammate) or download the full result set as CSV.
Select a card to run that lookup for the domain in the search box.
There is no global “push” for DNS. Each recursive resolver keeps a cached copy of your record for as long as its TTL (time to live) allows, and only asks your nameservers again once that copy expires. That is why some locations update in seconds while others take hours.
Pro tip: lower the TTL to 300 seconds a day before a planned migration, make the change, then raise it again once every location here shows the new value.
Want the full story? Read about how long DNS propagation really takes, what TTL does and how to change nameservers without downtime.
ipconfig /flushdnssudo dscacheutil -flushcache; sudo killall -HUP mDNSResponderresolvectl flush-cacheschrome://net-internals/#dnsEvery platform and browser, with what each command actually does: how to flush your DNS cache.
Step-by-step articles written for site owners and sysadmins. No jargon without an explanation.
How long does DNS propagation take? Learn why record changes appear at different times worldwide, what TTL and caching do, and how to speed it up.
Want to check my DNS settings? Find which DNS server your Windows, Mac, Linux, Android or iPhone device uses, and how to see who really answers.
Commands to flush the DNS cache on Windows, macOS, Linux, Chrome, Firefox, Android and iPhone, plus what flushing does and what it can't fix.
DNS propagation is the time it takes for a change to your DNS records (a new IP address, mail server or nameserver) to be seen by DNS resolvers around the world. Resolvers cache answers for the record's TTL (time to live), so each one only picks up your change after its cached copy expires.
Most record changes are visible within minutes to a few hours, depending on the TTL of the old record. Nameserver (NS) changes at the registry can take up to 24 to 48 hours because top-level domains such as .com publish NS records with a 48-hour TTL.
Every resolver caches records independently. A resolver that looked up your domain recently will keep serving the old answer until its TTL runs out, while another location that never cached it will already return the new value. Seeing mixed results is normal while a change is propagating.
Enter your domain above, choose the record type (for example A for a website or MX for email) and press Check DNS. CheckMyDNS queries 60 public resolvers in 47 countries at once. When every location returns your new value (or matches the expected value you entered), propagation is complete.
You cannot force other resolvers to drop their cache, but you can plan ahead: lower the TTL of the record to 300 seconds a day or two before the change, make the change, then raise the TTL again once it has propagated. Flushing your own computer and browser DNS cache also helps you see the new result sooner.
Your computer, browser or internet provider is probably still using a cached answer. Flush your local DNS cache, try a different network or browser, and check here whether resolvers worldwide already return the new IP address.
If you know the value your record should have (such as your new server IP), enter it as the expected value. Each resolver is then marked as propagated only when its answer contains that value, so you can see exactly where the old record is still cached.
Yes. CheckMyDNS is completely free, needs no account and works on any device. Beyond DNS propagation you can also run WHOIS, IP address, email blacklist and DMARC checks.