CNAME Record Lookup

A CNAME record points one name at another name instead of an IP address. Look up any domain's CNAME across 21 global servers to confirm the alias target is correct and has propagated everywhere.

Global DNS Propagation

New York, USA Google	---
Chicago, USA Gcore	---
Los Angeles, USA Cloudflare	---
Toronto, Canada CIRA	---
Mexico City, MX OpenDNS	---
London, UK Quad9	---
Frankfurt, Germany DNS.Watch	---
Paris, France FDN	---
Amsterdam, NL OpenNIC	---
Moscow, Russia Yandex	---
Singapore Singtel	---
Tokyo, Japan IIJ	---
Mumbai, India Google India	---
Seoul, Korea KT	---
Dubai, UAE Etisalat	---
Sydney, Australia Telstra	---
Auckland, NZ Cloudflare	---
São Paulo, Brazil NIC.br	---
Buenos Aires, AR Telecom Arg	---
Johannesburg, ZA ISPA	---
Cairo, Egypt Telecom Egypt	---

DNS Map

0 0

What a CNAME record does

A CNAME (Canonical Name) record makes one hostname an alias for another. When a resolver looks up the alias, it follows the CNAME to the target name and then resolves that name's A or AAAA record. This lets you point www.example.com at a platform host and change the destination in one place.

CNAMEs are common for subdomains that point at a hosting platform, CDN, or SaaS product. For the full explanation, read what is a CNAME record.

How to read the results

Each row shows one of the 21 global servers and the target name the CNAME points to, for example myapp.vercel.app. Every server should return the same target once the record has propagated.

If a row shows no value, that name has no CNAME at that server. Remember that a name with a CNAME cannot also have other record types, so a root domain or a name that already carries MX or A records will not accept one. Servers that still return an old target are serving a cached answer until the TTL expires.

Common CNAME values

Typical targets include platform hostnames like cname.vercel-dns.com, yourstore.myshopify.com, or a CDN endpoint such as d1234.cloudfront.net. Email and verification services also ask for CNAMEs that point at their infrastructure.

The root of a domain cannot use a CNAME because the zone already has SOA and NS records at that name. Use an A record at the root, or a provider feature such as ALIAS or flattened CNAME that returns an address instead. See A record vs CNAME for when to use each.

Troubleshooting CNAME records

If a subdomain does not resolve, confirm the CNAME target itself resolves. A CNAME that points at a name with no A record still fails, because the chain has to end at an address. Look up the target directly to check it returns an IP.

Watch for CNAME chains. Pointing an alias at another alias adds a lookup hop and slows resolution, and some platforms reject chained CNAMEs. If you added a CNAME on a name that already had records, the provider may have refused it silently. Remove the conflicting records first, then republish the CNAME.