CNAME Records: Giving Your Domain Multiple Names

What Is a CNAME Record

You type into a browser. The page loads. But behind the scenes, your website might actually live on some platform's servers — Shopify, Squarespace, or a cloud host. The address you typed is not the "real" address. It's an alias.

That alias exists because of a CNAME record. CNAME stands for "Canonical Name" — but the friendlier way to think about it is "alias record." It tells the internet: "When someone asks for this name, send them to that name instead."

In DNS terms, a CNAME record maps one domain name (like ) to another domain name (like ). It's not pointing to an IP address. It's pointing to another name, and that name handles the rest.

Real-World Analogy

Think about a person who goes by a nickname. Everyone at the office calls them "Alex," but their legal name is "Alexander Chen." When someone asks for Alex, the company directory says "see Alexander Chen." The CNAME record is that note in the directory. It doesn't give you Alex's desk location directly — it tells you to look up Alexander instead.

How CNAME Records Work

Layer 1 — Plain English

Imagine you're delivering a package. You have the address "123 Main Street, Suite 4B." When the delivery driver arrives at 123 Main Street, the building directory says Suite 4B is actually up on the fourth floor, labeled "Riverfront Consulting." The driver follows the redirect, finds Riverfront Consulting, and drops off the package.

That's what a CNAME record does. When a browser or email server asks for , the DNS system doesn't hand back an IP address right away. It says, "Oh, that name? It's really . Go ask about that name instead." The request then continues with the real name, which eventually resolves to an IP address where your site lives.

The key thing: a CNAME doesn't end the conversation. It passes the request to another name. The second name is the one that actually knows the final address.

Layer 2 — Technical Detail

Technical Details

▸ — the alias (the name people type)

▸ — the canonical name (the "real" name it points to)

▸A CNAME record contains only a domain name as its value, never an IP address

▸DNS resolvers follow CNAMEs recursively until they find an A or AAAA record (the records that actually hold IP addresses)

▸A CNAME cannot coexist with other record types at the same name — if is a CNAME, cannot also have an MX record or TXT record

▸The root of your domain () should never be a CNAME — the root already needs SOA and NS records, and a CNAME would conflict with those

Why It Matters for Your Business

When CNAME records are set up correctly, things just work. Customers type your web address, and they land on your site — whether that site is hosted by you, by Shopify, by a landing page tool, or by a marketing platform. Your team doesn't think about DNS. Customers don't think about DNS. Everyone wins.

When they're wrong, the failure is invisible and total. Your address stops loading. A subdomain for your help center goes dark. A marketing landing page that your team spent weeks building returns a blank error. No one gets a helpful error message. The site simply doesn't resolve.

This matters for anyone running campaigns. Marketing teams create subdomains for microsites, event pages, and partner portals. If those subdomains rely on CNAME records and the record breaks, the campaign dies silently. Sales loses leads, and no one knows why.

Common Issues and Warning Signs

A broken CNAME usually shows up as a site or service that suddenly stops working. The problem is that CNAME failures look exactly like "the internet is down" to most people. There's no obvious alert. Your browser just spins and eventually shows a resolution error.

Another common issue: someone sets up a CNAME at the root domain by accident, or adds other records alongside a CNAME. Either of these violates DNS rules and can cause unpredictable failures — sometimes it works, sometimes it doesn't, depending on what the visitor's DNS resolver decides to do.

Common Issues

Your `www` address suddenly won't load, even though the non-www version works fine — the CNAME record may have been changed or removed

A marketing subdomain (like `event.yourcompany.com`) returns a DNS error — the CNAME pointing to the landing page platform may have a typo or point to a deleted service

You recently switched hosting providers and now certain addresses don't resolve — old CNAME records may still point to the previous platform

A TechSpy scan flags a CNAME at your root domain — the root domain () should use A records, never a CNAME

Intermittent failures on a subdomain — this often means the CNAME target is resolving inconsistently or another record type is conflicting at the same name

How to Fix or Improve CNAME Records

Fixing a CNAME issue usually means checking what it points to and whether that target still exists. Before changing anything, confirm that the service you're pointing to actually expects a CNAME — most platforms tell you exactly which DNS records to create when you set up a custom domain.

Once you've made the change, run another TechSpy scan to confirm the record is correct and resolving properly. It's free and takes under a minute.

1Identify which CNAME is failing. If you ran a TechSpy scan, it will flag the specific record and what's wrong. Otherwise, check which subdomain isn't working (for example, or ).

2Log into your DNS provider. This is the company where you bought your domain (like Namecheap, GoDaddy, or Cloudflare) or where your DNS is managed. You'll need the login credentials.

3Find the CNAME record. Look in the DNS records section for an entry with type "CNAME" at the name that's failing. Check the value (the target domain) — does it exactly match what your hosting platform or service provider told you to use? Even a missing dot or extra character will break it.

4If the target is correct but the service is down, contact the platform you're pointing to. The problem might be on their side — their service might not be answering at that address anymore.

5If the target is wrong, edit the record to match the correct target. DNS changes can take a few minutes to a few hours to spread across the internet, so don't panic if it doesn't fix itself instantly.

6If you don't manage your DNS directly, forward this article to whoever does — your IT person, your web developer, or the agency that set up your domain. Tell them which subdomain is broken and what it should point to.