Global DNS Propagation Checker
Verify whether your updated DNS records have propagated worldwide. Query 16+ geographic recursive resolvers concurrently across North America, Europe, and Asia-Pacific.
Checking servers...
Most common resolved record
Worldwide round-trip time
| Status | Server & Region | Resolved Value | RTT |
|---|
Understanding DNS Propagation Delays
When you point your domain to a new web host or CDN, why doesn't the entire internet switch immediately? DNS relies on distributed hierarchical caching designed to minimize internet traffic load:
1. Recursive Cache TTL
Every DNS response includes a TTL (Time to Live) countdown. Until an ISP recursive resolver's cache reaches zero, it serves the cached record without querying your authoritative nameserver.
2. TLD Registry Delegation
Changing authoritative nameservers (e.g., from GoDaddy to Cloudflare) requires updating the Top-Level Domain (TLD) root zone (such as Verisign for .com), which enforces longer caching policies.
3. Negative Caching (SOA)
If a user visited your site before DNS was configured, resolvers cache the NXDOMAIN negative response for the duration specified in your zone's SOA record.
Propagation FAQs
What is DNS Propagation?↓
DNS propagation is the timeframe required for updates made to your domain nameservers or DNS records (such as changing hosting IPs or MX records) to be cached and recognized by internet service providers (ISPs) and recursive DNS servers worldwide.
How long does DNS propagation take?↓
DNS propagation typically takes anywhere from a few minutes up to 24–48 hours. The duration depends predominantly on the TTL (Time to Live) value configured on the previous DNS records, your ISP caching policy, and whether you are changing authoritative nameservers (which requires updating registry root servers).
How can I accelerate DNS propagation before moving hosting?↓
Before making DNS changes, lower your record TTL to 300 seconds (5 minutes) at least 24 hours in advance. Once the old TTL expires across worldwide caches, changes will take effect almost immediately when you update your records.
Why do some locations resolve old IPs while others resolve new IPs?↓
Different ISPs and recursive resolvers cache DNS responses independently based on when their local users first requested the domain. A resolver in Tokyo might still have 3 hours remaining on its cache TTL, while a resolver in Frankfurt has already fetched your new record.