↓Skip to main content
0
  1. Wiki/

Email Encyclopedia: What is a CNAME Record

Table of Contents

Alibaba Mail More Products and Services

A CNAME record (Canonical Name Record) is a type of resource record in the Domain Name System (DNS) used to point a domain or subdomain to another “canonical” domain. Through CNAME records, multiple domains can point to the same primary domain, thus implementing domain alias functionality.

In the internet environment, CNAME records are widely used in website hosting, Content Delivery Networks (CDN), email services, and many other fields, helping users simplify domain management and improve system flexibility and maintainability.

Basic Concepts #

DNS and Domain Resolution #

To understand CNAME records, you first need to understand the basic principles of DNS (Domain Name System). DNS is a distributed database system responsible for converting human-readable domain names (such as example.com) into corresponding IP addresses (such as 192.0.2.1) so that computers can communicate in networks.

In DNS, each domain name may contain multiple types of resource records, such as:

  • A record: Maps a domain name to an IPv4 address;
  • AAAA record: Maps a domain name to an IPv6 address;
  • MX record: Specifies the mail server that receives emails for the domain;
  • TXT record: Stores text information, commonly used for domain ownership verification or SPF records;
  • CNAME record: Uses one domain name as an alias for another domain name.

Function of CNAME Records #

The core function of a CNAME record is to create domain aliases. For example, if a user wants www.example.com and example.com to point to the same server, they can add a CNAME record for www.example.com in their DNS settings, pointing to example.com. This way, when users visit www.example.com, DNS will automatically resolve it to the IP address corresponding to example.com.

Use Cases #

CNAME records have very wide applications. Here are some common use cases:

Subdomain Aliases #

One of the most common uses is to create aliases for subdomains. For example:

www IN CNAME example.com.

This indicates that www.example.com is an alias for example.com. If the IP address of example.com changes in the future, you only need to update its A record, and all CNAME records pointing to it will automatically take effect.

CDN Acceleration #

Many websites use CDN (Content Delivery Network) to improve access speed. In this case, CNAME records are usually configured for static resource subdomains (such as cdn.example.com), pointing to domain names provided by CDN service providers:

cdn IN CNAME cdn.provider.net.

This way, user requests are routed to the nearest CDN node, improving loading speed and reducing the load on the source server.

Third-party Service Integration #

Some third-party services (such as Google Workspace, Shopify, etc.) require users to set up CNAME records in their DNS to complete domain binding. For example, when using Google Mail service, you might need to add the following record:

mail IN CNAME googlemail.com.

This allows Google to handle mail traffic for that subdomain.

Technical Details #

Format of CNAME Records #

In DNS zone files, the standard format for CNAME records is as follows:

<hostname> <TTL> IN CNAME <target domain>.

Where:

  • <hostname>: The domain or subdomain that needs an alias;
  • <TTL>: Time To Live, the lifetime of the record (in seconds), indicating how long the record is valid in cache;
  • IN: Indicates Internet class (usually the default value);
  • CNAME: Record type;
  • <target domain>: The canonical domain name, i.e., the primary domain being pointed to.

Example:

www 86400 IN CNAME example.com.

This indicates that www.example.com is an alias for example.com, with a TTL of 86400 seconds (24 hours).

Considerations #

  1. Cannot Coexist with Other Records
    According to RFC 1912, if a domain name has a CNAME record, it cannot simultaneously have other types of records (such as A, MX, TXT, etc.). This means you cannot set both a CNAME record and other resource records for the same domain name.

  2. Not Suitable for Root Domains (@)
    It is generally not recommended to set CNAME records for root domains (such as example.com itself), as this would prevent MX records and others from working properly. The recommended practice is to use A or AAAA records to point directly to IP addresses.

  3. Chained CNAME Records
    Although it is technically allowed for a CNAME to point to another CNAME (forming a CNAME chain), doing so may cause resolution delays and increase the possibility of errors. Therefore, excessively long CNAME chains should be avoided.

Practical Guide #

How to Add a CNAME Record #

Most domain registrars or DNS service providers (such as Cloudflare, GoDaddy, Alibaba Cloud DNS, Tencent Cloud DNSPod, etc.) provide graphical interfaces for managing DNS records. Here are the general steps:

  1. Log in to your domain management console;
  2. Find the “DNS Management” or “Domain Resolution” page;
  3. Add a new record:
    • Select “CNAME” as the type;
    • Enter the subdomain you want to set up (such as www) in the hostname field;
    • Enter the canonical domain you want to point to (such as example.com) in the target field;
  4. Save the changes and wait for DNS propagation (usually takes effect within a few minutes).

Verifying if a CNAME Record Has Taken Effect #

You can use the following command to verify if a CNAME record is correctly set up:

dig www.example.com CNAME

Or use online tools such as DNS Checker for global multi-location testing.

Difference Between CNAME Records and Alias Records #

In recent years, some DNS service providers have introduced new types of records called ALIAS records or ANAME records, aimed at addressing some limitations of CNAME records (such as not being usable for root domains). These records are essentially enhanced versions of CNAME, allowing root domains to point to another domain under certain conditions while preserving the existence of other records.

However, ALIAS/ANAME records are not part of the standard DNS protocol but are extension features specific to certain DNS services.

Security and Best Practices #

Although CNAME records provide great flexibility, in practical use, you should also note the following points:

  • Avoid unnecessary CNAME chains: Each CNAME hop increases resolution time and potential points of failure;
  • Regularly check record validity: Ensure that target domains are still available and have not been tampered with;
  • Prevent CNAME hijacking: Ensure the security of DNS accounts, enable two-factor authentication and other measures;
  • Set cache time reasonably in conjunction with TTL: For frequently changing records, set a lower TTL; for stable records, the TTL can be appropriately increased to reduce query pressure.

Summary #

CNAME records are an important type of resource record in the DNS system, used to implement domain alias functionality. They play a key role in modern internet architecture, especially in multi-subdomain management, CDN integration, and third-party service connections.

By properly configuring CNAME records, you can significantly improve the efficiency and flexibility of domain management. However, during use, you also need to be aware of their limitations and potential risks, following best practices to ensure system stability and security.

With the development of the internet, DNS technology is also constantly evolving, and more compatible and feature-rich record types may emerge in the future. But in the current environment, CNAME records remain one of the indispensable basic tools.