DNS Propagation Checker - Check Global DNS Propagation Live
Verify whether DNS record updates have propagated worldwide across global nameservers.
| Domain | Type | Primary NS | Responsible Person | Serial | Refresh | Retry | Expire | Minimum | TTL |
|---|
| Name Server | IP Address | TTL |
|---|
| Domain | Type | TTL | Record Value |
|---|
| Trace Result |
|---|
| Domain | Type | Record | Status |
|---|
| Domain | Type | Record | Status |
|---|
DNS Propagation Checker from Eight World Regions
After you change a DNS record you need to know two things: is your DNS provider publishing the new value yet, and is it publishing it the same way everywhere? This checker answers both. It asks your domain's authoritative name servers the same question from eight locations and lists each answer side by side.
Pick a record type, enter a domain (or an IP address for a PTR check) and each region fills in as soon as it replies.
Check Another Record Type
- A record propagation: after moving a website to a new server or IP address.
- CNAME record propagation: after pointing www, a subdomain or a service verification name at another host.
- MX record propagation: after switching email to a new provider.
- NS record propagation: after changing name servers at your registrar or moving DNS hosting.
- PTR record propagation: after your server provider sets reverse DNS for a mail server IP.
Published Is Not the Same as Cached
The answers come straight from the authoritative servers, so this check shows what is published, not what a particular ISP has cached. When all eight regions agree, the change is live at the source. A visitor whose resolver cached the old value will get the new one once that cached copy's TTL runs out, so the longest wait is the TTL the record had before the change.
When regions disagree, the cause sits at the source. Either one of your name servers has not picked up the update, or the service is designed to answer differently by location, as CDNs and geo-routed load balancers do.
How This Check Works
Eight Regions Across Six Continents
Every check is run from South Asia (Mumbai), Southeast Asia (Singapore), East Asia (Tokyo), the Middle East (Dubai), Europe (London), North America (N. Virginia), South America (São Paulo) and Oceania (Sydney). Each location reports on its own, so one slow or unreachable region never hides the results from the others.
Response Time and Fastest Region
Each region asks the authoritative name servers directly and times only that one exchange. Authoritative servers do not answer from a cache, so every figure is a fresh lookup from that part of the world. The Fastest Region in the summary panel is the lowest of those times in the current check.
Ticks, Crosses and the Map
A green tick means the region received an answer and shows it. A red cross means it got none; hover the marker to see why, such as NXDOMAIN, a timeout or no record of that type. The world map below the results marks each region with its outcome, so you can tell whether a problem is limited to one continent.
Global Propagation Troubleshooting & Common Fixes
After migrating to a new server or hosting provider, some global locations resolve the new IP while others return the old address. When authoritative nameservers answer with conflicting data, it usually means secondary (slave) nameservers have not received zone updates due to delayed AXFR/IXFR zone transfers, firewall restrictions, or an unchanged SOA serial number.
When six or seven regions return green checkmarks with valid responses, but one region (such as São Paulo, Sydney, or Dubai) displays a red cross or connection timeout, this indicates regional packet loss, firewall geo-blocking, or routing blackholes between that region's network and your authoritative nameservers.
Seeing different IP addresses across North America, Europe, and Asia is frequently expected behaviour rather than an error. Modern Content Delivery Networks (Cloudflare, Fastly, Akamai) and cloud load balancers use latency-based routing, Geo-DNS, or Anycast BGP to deliver traffic to the nearest geographic edge node.
