How to Set Up CNAME Records for Your Domain (and When to Use Them)

DNS records can feel like a foreign language, but most business owners eventually need to add a CNAME record for one reason or another. A third-party email marketing service needs verification, a new custom subdomain needs to point somewhere, or your e-commerce platform needs a branded domain. Here is a clear explanation of what CNAME records do, when to use them, and exactly how to add one in cPanel.

What a CNAME Record Does

CNAME stands for Canonical Name. A CNAME record creates an alias: it tells DNS that one hostname is just another name for a different hostname.

Instead of pointing directly to an IP address (like an A record does), a CNAME points to another domain name. DNS resolves the chain: your CNAME points to the target hostname, and the target hostname resolves to an IP. The end result for your visitor is the same - they reach the right server - but the routing goes through an alias.

A simple example: www.yourdomain.ca can be a CNAME pointing to yourdomain.ca. When someone visits the www version, DNS resolves the alias and ends up at the same destination as the non-www version.

The Most Common CNAME Use Cases

www subdomain: Many domain configurations use a CNAME to make www.yourdomain.ca an alias for yourdomain.ca. This is a clean, standard setup.

Custom subdomains for third-party services: This is the most frequent reason business owners need to add a CNAME. Examples include:

• Mailchimp custom tracking domain: email.yourdomain.ca as a CNAME pointing to Mailchimp's servers, so your campaigns use your domain rather than Mailchimp's
• Shopify custom domain: Pointing your domain to Shopify's servers so your store loads on your branded domain
• Google Workspace setup: Google may ask you to add a CNAME as a domain verification record
• Verification records: Many services (Mailchimp, HubSpot, ActiveCampaign, Microsoft 365) use CNAME records to prove you own the domain before enabling branded features

In all these cases, the service provider gives you a specific CNAME name and target value to enter. You are just following their instructions and inputting those values.

The CNAME-at-Root Limitation

Here is an important technical constraint: you cannot use a CNAME record for a bare root domain (also called the zone apex). You cannot make yourdomain.ca itself a CNAME pointing to something.else.com.

This is because the DNS specification requires that the root domain can have SOA (Start of Authority) and NS (nameserver) records, and CNAME records cannot coexist with other record types on the same name.

This matters when a service asks you to point your root domain - not a subdomain - to their servers. A pure CNAME is not possible.

CNAME flattening solves this. Cloudflare (and a small number of other DNS providers) offer a feature called CNAME flattening, also called ALIAS or ANAME records on other platforms. This is a proprietary extension that resolves the CNAME target to an IP address at the DNS provider level and returns an A record to the visitor. From a technical standpoint, it behaves like an A record but points to a hostname. If you need CNAME-like behaviour at your root domain, moving your DNS to Cloudflare and using their CNAME flattening is the practical solution.

How to Add a CNAME Record in cPanel

1. Log in to cPanel and go to Domains > Zone Editor (sometimes listed as DNS Zone Editor)
2. Find your domain in the list and click Manage
3. Click Add Record and select CNAME from the type dropdown
4. In the Name field, enter the subdomain part - for example, if the service wants you to add verify.yourdomain.ca, enter verify (cPanel will append the domain automatically)
5. In the CNAME (target) field, enter the value provided by your service - for example, verify.mailchimp.com. - including the trailing dot if your provider specifies it
6. Set the TTL (time to live) - 14400 (4 hours) is a reasonable default, or leave it at whatever cPanel pre-fills
7. Click Add Record

DNS changes typically propagate within a few minutes to a few hours, though full global propagation can take up to 48 hours in some cases. Most services will check automatically and notify you once they can see the CNAME is in place.

If you are ever uncertain about a DNS change, dotCanada support can help you verify and add the correct records for your domain.