Multi-Region NS DNS Propagation Checker
Test NS DNS propagation across multiple worldwide DNS servers in North America, Europe, Asia, and Oceania.
| 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 |
|---|
How Multi-Region Checking Helps You
A DNS record does not reach the whole world at the same moment. After you change a record, some parts of the internet see the new value while others still answer with the old one. Checking from a single location tells you what your connection sees - not what a visitor in another country sees.
This page asks the same question from eight separate locations around the world and shows you each answer side by side. If every region returns the same value, your record is consistent everywhere. If they disagree, you can see exactly which part of the world is still behind.
It is the quickest way to answer the questions that single-location tools cannot: has my change gone live everywhere yet?, why does the site work for me but not for my customer abroad?, and is my domain returning different addresses in different countries?
What This Check Covers
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 independently, so one slow or unreachable region never hides the results from the others.
How the Response Time Is Measured
For each region we ask your domain's own authoritative name servers directly and time that single exchange. Authoritative servers never reply from a cache, so the figure you see is a genuine fresh lookup measured from that part of the world - not a cached answer that would flatter the result. The time excludes everything except the lookup itself.
Fastest Region
The Fastest Region figure in the summary panel is simply the lowest response time returned by any region in the current check. It tells you the best case a visitor anywhere in the world could expect when resolving your domain.
Records You Can Check
Multi-region checking is available for A, NS, MX, CNAME and PTR records - the record types where a difference between regions actually matters for reachability, mail delivery and delegation.
Reading the Results
A green tick means that region resolved the record successfully and shows the value it received. A red cross means that region could not resolve it at all - the record may be missing, the name servers may be refusing the query, or the change may not have reached that part of the world yet. Hover any marker for the exact reason.
Why Regions Can Disagree
Differences are not always a fault. Large services deliberately return different addresses in different countries so visitors reach a nearby server. Genuine problems usually look different: one region returning nothing while the rest agree, or an old value lingering in one place long after a change.
World Map View
Below the results a world map marks each region with its outcome, so you can see at a glance whether a problem is isolated to one continent or affects your domain globally.
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.
