Skip to main content

What is a DNS CNAME record?

A "Canonical Name" (CNAME) record points from an alias domain to a "canonical" (true) domain. Unlike an A record, which maps a name to an IP address, a CNAME record maps a name to another domain name.

The Scavenger Hunt Analogy: Imagine a scavenger hunt where each clue points to another clue, and the final clue points to the treasure. A domain with a CNAME record is like a clue that points to another domain (clue) until you finally reach the domain with an A record (the treasure).

How CNAME Records Work​

Suppose blog.example.com has a CNAME record with a value of example.com.

  1. When a DNS server hits the records for blog.example.com, it triggers another lookup to example.com.
  2. It then returns the IP address of example.com via its A record.
  3. In this scenario, example.com is the canonical name (true name) of blog.example.com.

Why use CNAME?​

This is extremely useful for subdomains like shop.example.com or dev.example.com. If your server's IP address changes, you only need to update one A record (the root domain), and all subdomains using CNAMEs will automatically follow that change.

CNAME Record Example​

Domain (Alias)Record TypeValue (Canonical Name)TTL
blog.example.comCNAMEexample.com32600

[Image showing the DNS redirection flow from alias to canonical domain]

A Common Misconception​

A CNAME record does not necessarily resolve to the same page as the root domain. It only points the client to the same IP address. Once the client reaches that IP, the web server looks at the URL (e.g., blog.example.com) and delivers the specific blog content instead of the homepage.

Important Restrictions and Rules​

1. No Duplicate Names​

Per DNS specifications, no other DNS records (MX, TXT, A, etc.) can exist on a name that already has a CNAME record.

  • Exception: CNAME Flattening (where a CNAME acts like an A/AAAA record), often used by proxy services like cloudmysite.

2. MX and NS Record Limitations​

MX and NS records cannot point to a CNAME record. They must point directly to an A record (IPv4) or an AAAA record (IPv6). This ensures that mail delivery and nameserver resolution remain efficient and fail-safe.

3. Inefficiency of "Chaining"​

While you can point a CNAME to another CNAME, it is highly inefficient. It requires multiple lookups, slowing down the user experience.

  • Bad Practice: blog → www → root
  • Best Practice: Point both blog and www directly to the root domain.

CNAME Queries for Non-CNAME Records​

If someone queries for a different record type (like a TXT record) using an alias that has a CNAME, the DNS server will return the CNAME record instead. The requester then has to perform a new query using the "true" domain name to find the TXT record they originally wanted.

Pro-Level DNS Management​

Managing complex CNAME structures is vital for modern SaaS and e-commerce platforms. If you are scaling your business in 2026 and need a Reliable Email Provider or expert domain infrastructure, ensuring your canonical names are optimized is key.

Would you like me to draft the next part of the documentation covering MX Records, which are essential for your business email flow?