Updated on:  
January 21, 2025

What is CNAME record

A CNAME record, short for Canonical Name record, is a type of DNS record that maps one domain name to another. This helps direct web traffic effsiciently by creating an alias for your domain. Instead of pointing directly to an IP address, a CNAME record links one domain to another, making domain management simpler.

colourful collage of abstract shapes and signpost with multiple directions

How does an CNAME record work

A CNAME record works by redirecting domain queries to another domain name. When someone enters a URL in their browser, the DNS system checks the domain’s records. If it finds a CNAME record, it redirects the query to the target domain specified in the record.

For instance, if “shop.mybusiness.com” has a CNAME record pointing to “hostedplatform.com,” the browser fetches the content from “hostedplatform.com” while still displaying “shop.mybusiness.com” in the address bar. This process happens seamlessly, ensuring a smooth experience for visitors.

CNAME records are widely used for subdomains, third-party services, and content delivery networks (CDNs). They save time by eliminating the need to manage IP addresses manually, especially if they change frequently.

Understanding key components

CNAME records consist of simple yet powerful components that make them work efficiently.

  • Alias Name: This is the domain name you want to redirect. It can be a subdomain like “shop.mybusiness.com” or a custom domain name for an external service.
  • Canonical Name (Target): This is the destination domain where the alias name points. For example, “hostedplatform.com” is the target in the CNAME record for “shop.mybusiness.com.”
  • TTL (Time to Live): This value determines how long the DNS server should cache the CNAME record. Lower TTL values make updates faster, while higher values reduce DNS server load.

Examples

CNAME records are commonly used in various scenarios, making them invaluable for website and domain management.

If you use a website builder like Wix or Squarespace, they might ask you to set up a CNAME record. For instance, “www.mybusiness.com” can point to “hosting.wix.com.” This ensures your custom domain works seamlessly with their platform.

Another example is setting up email verification for marketing tools. Services like Mailchimp often require a CNAME record to verify domain ownership. For example, “mail.mybusiness.com” might point to “dkim.mailchimp.com.”

How to check your CNAME records

Checking your CNAME records is straightforward and important for troubleshooting or verifying configurations. Start by logging into your domain registrar or DNS hosting provider. Look for the DNS management section, often called a “DNS Settings.”

In the DNS settings, locate the list of DNS records. Search for any entries labeled as CNAME. They will display the alias name and the canonical name it points to. Some registrars provide tools to edit or test records directly in this interface.

You can also use external tools like MXToolbox to check your CNAME records. These tools let you enter your domain name and display all associated DNS records, including CNAME entries.

Common problems and how to fix them

Several issues can arise with CNAME records, but they are usually easy to fix with the right knowledge.

  • Incorrect Target Domain: If the canonical name in your CNAME record is wrong, traffic will be redirected to the wrong destination or fail entirely. Double-check the target domain provided by your service provider.
  • Conflicts with Other DNS Records: CNAME records cannot coexist with other DNS records for the same name. For example, if “www.mybusiness.com” has an A record, you cannot also create a CNAME for it. Resolve this by removing conflicting records.
  • Propagation Delays: DNS changes, including updates to CNAME records, can take time to propagate across the internet. Plan updates during low-traffic periods to minimize disruption.
  • Expired TTL Settings: If the TTL value is set too low, DNS servers may not cache the record long enough, causing unnecessary lookups. Adjust the TTL for better performance without losing flexibility.