Multi-Region CNAME DNS Propagation Checker
Test CNAME 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 |
|---|
CNAME Record Propagation Checker
A CNAME record makes one name an alias of another. You might point www at your main domain or a shop subdomain at a hosted store. Many services, including CDNs, email platforms and SSL providers, also ask you to add a CNAME to route traffic or prove you own the domain.
This checker asks the authoritative name servers for the CNAME on the exact name you enter and shows the target each of the eight regions receives.
Reading CNAME Results
The same target everywhere
The alias is published. If a service still says it cannot see the record, it may be checking before its own cache expires. Wait for the TTL and retry the verification.
No record in every region
The name has no CNAME. It may hold an A record instead, it may not exist, or the CNAME was added to a different name. Services often want a long, specific host such as a selector or a random-looking label. Copy the host exactly as the provider shows it, and remember that some DNS panels add your domain to the end automatically.
The old target in some regions
Your name servers disagree about the zone. One of them has not received the latest version. Check the domain's NS records and ask the DNS provider to resync the lagging server.
CNAME Rules That Cause Failures
No CNAME on the bare domain
The root of a domain must carry SOA and NS records, and a CNAME cannot share a name with any other record. So example.com itself cannot be a CNAME. Many providers offer ALIAS, ANAME or CNAME flattening for this case, and those answer as A records. Check the root with the A record check.
Nothing else on a name that has a CNAME
A name that is an alias cannot also have MX, TXT or A records. Adding a TXT verification record to a name that is already a CNAME is a common reason a provider reports that verification failed.
The target resolves on its own
This check shows where the alias points, not the final IP address. If the target belongs to a CDN, its addresses can differ from region to region. Run the A record check on the target name to see them.
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.
Check Another Record Type
- A record propagation: after moving a website to a new server or IP address.
- 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.
- Multi-region DNS check overview: how the eight-region check works and which record to pick.
