CNAME Lookup

What Is a CNAME Record?

A CNAME (Canonical Name) record is a type of DNS record that creates an alias from one domain name to another. Instead of mapping a domain directly to an IP address (like an A record does), a CNAME record points a domain to another domain name, which then resolves to the final IP address.

For example, you might have www.example.com set up as a CNAME pointing to example.com. When a user visits www.example.com, the DNS resolver first finds the CNAME record, then looks up the A record for example.com to get the actual IP address.

When to Use CNAME Records

CNAME records are essential in several common scenarios:

• Subdomain aliasing — Point www.example.com, blog.example.com, or shop.example.com to your main domain or hosting provider.
• CDN configuration — Point your domain to a CDN endpoint like d1234abcdef.cloudfront.net or example.cdn.cloudflare.net.
• SaaS integrations — Connect custom domains to hosted services like GitHub Pages, Shopify, Heroku, or Vercel using CNAME records.
• Email services — Verify domain ownership for email providers like Google Workspace or Microsoft 365 using CNAME records.
• Load balancing — Point subdomains to load balancer hostnames that can change IP addresses without requiring DNS updates.

CNAME vs. Other DNS Record Types

CNAME vs. A Record

An A record maps a domain directly to an IPv4 address. A CNAME record maps a domain to another domain name (an alias). The key difference: A records are the “final answer” in DNS resolution, while CNAME records add a redirection step. A records are required at the zone apex (root domain); CNAME records can only be used on subdomains.

CNAME vs. ALIAS/ANAME

ALIAS (or ANAME) records are a proprietary extension offered by some DNS providers (Cloudflare, Route 53, DNSimple) that work like CNAME records but can be used at the zone apex. They resolve the target domain to an IP address server-side before returning the response, avoiding the restriction that CNAME records cannot coexist with other record types at the same name.

CNAME vs. MX Record

MX records specify the mail servers responsible for accepting email for a domain. While both MX and CNAME records point to domain names, they serve completely different purposes. You cannot place a CNAME record on a name that also needs MX records — the CNAME would override everything else. This is why CNAME records are only used on subdomains that don't need their own mail handling.

Understanding DNS Record Types

Our CNAME lookup tool queries multiple DNS record types simultaneously. Here's what each type means and when it's relevant:

How CNAME Resolution Works

When your browser needs to connect to www.example.com, the DNS resolution process follows these steps:

1. Your browser asks the recursive resolver (usually your ISP or a public resolver like 8.8.8.8) for the IP address of www.example.com.
2. The resolver queries the authoritative DNS server for example.com and receives a CNAME record: www.example.com → example.com.
3. The resolver now needs to resolve example.com, so it queries again and gets an A record: example.com → 93.184.216.34.
4. The resolver returns the IP address to your browser, which connects to the server.

This is why CNAME records add a small latency overhead — they require at least one additional DNS lookup. In practice, DNS resolvers cache results according to the TTL (Time to Live), so the overhead is usually only felt on the first request.

Common CNAME Record Mistakes

Avoid these frequent DNS configuration errors when working with CNAME records:

• CNAME at the zone apex — You cannot place a CNAME record on your root domain (example.com). CNAME records can only exist on subdomains. Use an A/AAAA record or your provider's ALIAS/ANAME equivalent for the root.
• CNAME with other records — A CNAME record cannot coexist with any other record type (A, MX, TXT) for the same name. This is a strict DNS rule (RFC 1034). If you need MX records on a subdomain, use an A record instead of CNAME.
• CNAME chains — A CNAME pointing to another CNAME creates a chain that increases resolution time. While technically allowed, chains longer than 2-3 hops can cause timeouts or be rejected by some resolvers.
• Circular CNAME references — If a.example.com points to b.example.com and b.example.com points back to a.example.com, DNS resolution will fail. Most resolvers detect and abort circular references.
• Missing trailing dot — In some DNS management interfaces, the CNAME target requires a trailing dot (example.com.) to indicate a fully qualified domain name. Without it, the target may be interpreted as relative to the current zone.

CNAME Records for Popular Services

Many services require CNAME records as part of their custom domain setup. Here are common configurations:

• GitHub Pages: www.yourdomain.com → yourusername.github.io
• Vercel: www.yourdomain.com → cname.vercel-dns.com
• Netlify: www.yourdomain.com → yoursite.netlify.app
• AWS CloudFront: cdn.yourdomain.com → d1234abcdef.cloudfront.net
• Shopify: www.yourdomain.com → shops.myshopify.com
• Google Workspace: Various CNAME records for mail, calendar, and domain verification

Use our CNAME lookup tool above to verify that your CNAME records are properly configured after making changes to your DNS settings.

DNS Propagation and Monitoring

After creating or modifying a CNAME record, the change needs to propagate across the global DNS infrastructure. This can take anywhere from a few minutes to 48 hours, depending on the previous TTL value and caching behavior of intermediate resolvers.

During DNS propagation, some users may see the old records while others see the new ones. This is normal and expected. You can use our CNAME lookup tool to check what Google's DNS resolvers currently return — since Google's resolvers handle a large portion of global DNS traffic, they're a good indicator of propagation progress.

For ongoing monitoring after your DNS is configured, consider setting up endpoint monitoring with API Status Check to ensure your services remain accessible and get instant alerts if DNS issues cause downtime.

Frequently Asked Questions About CNAME Lookup

What is a CNAME record?

A CNAME (Canonical Name) record is a type of DNS record that creates an alias from one domain name to another. For example, www.example.com can be a CNAME pointing to example.com. When a DNS resolver encounters a CNAME record, it follows the alias and resolves the canonical name to get the final IP address.

How do I look up CNAME records for a domain?

Enter the domain name in our CNAME lookup tool and click “Lookup DNS.” The tool queries Google's public DNS resolver to retrieve CNAME records along with A, AAAA, MX, NS, and TXT records. You can also use command-line tools like dig example.com CNAME or nslookup -type=CNAME example.com.

What is the difference between a CNAME and an A record?

An A record maps a domain directly to an IPv4 address, while a CNAME record maps a domain to another domain name (an alias). A records are the final resolution step. CNAME records add an extra lookup because the resolver must then resolve the canonical name. You cannot have a CNAME record at the zone apex (root domain).

Can I use a CNAME record for my root domain?

No, standard DNS prohibits CNAME records at the zone apex. However, some DNS providers offer alternatives: Cloudflare has “CNAME flattening,” AWS Route 53 has “ALIAS records,” and others provide similar “ANAME” functionality that works like a CNAME at the root level.

Why is my CNAME record not working?

Common causes include: DNS propagation delay (up to 48 hours), conflicting records (CNAME cannot coexist with other record types), the target domain not existing, incorrect syntax, or attempting to use CNAME at the zone apex. Use our lookup tool to verify what resolvers currently see.

What is DNS TTL and why does it matter?

TTL (Time to Live) is how long DNS resolvers cache a record before re-querying the authoritative server. Lower TTL means faster propagation but more DNS queries. A moderate TTL of 3600 seconds (1 hour) works well for most CNAME records. Lower the TTL before planned DNS migrations.

How do CNAME records affect website performance?

CNAME records add an extra DNS resolution step, which can increase latency by a few milliseconds on the first request. DNS caching mitigates this for subsequent requests. Avoid long CNAME chains (CNAME → CNAME → CNAME) as each hop adds lookup time.

How do I monitor DNS records for changes?

Use our CNAME lookup tool for manual checks, or set up endpoint monitoring with API Status Check to detect when DNS issues cause service disruptions. Pair DNS monitoring with uptime monitoring for complete visibility into your infrastructure.