How a CNAME works
A CNAME record — short for canonical name — points one hostname, usually a subdomain, at another hostname rather than at a numeric address. The resolver reads it, sees that it has been sent on to a different name, and repeats the lookup on that name until it finally reaches an A record holding a real address.
That indirection is the entire point. When another company hosts something for you — a shop, a support portal, a landing page builder, an email platform’s tracking links — the machine serving it will move as they grow or change providers. If your zone held a fixed address you would have to keep up with every one of those moves. Pointing at their hostname instead means they update their own record and yours carries on working untouched.
Why CNAMEs matter
Almost every service that asks you to connect your own domain is asking for a CNAME. Domain verification, custom tracking domains, hosted checkout pages, status pages and knowledge bases all use the same mechanism; only the wording of the instructions differs. The feature you are paying for works or fails on whether that one record was entered exactly as supplied, on exactly the right host name.
There is a marketing reason to care as well. Sending campaigns through a sending domain on your own name, rather than the platform’s shared one, is set up with CNAMEs the platform issues. It puts your brand in the link a recipient sees when they hover, and ties sending reputation to your domain instead of a pool shared with strangers.
Common mistakes with CNAMEs
Trying to put one on the bare domain is the most frequent. The standard does not allow a CNAME to sit alongside other records on the same name, and the bare domain always carries other records, its mail routing among them. Some panels reject the attempt; others accept it and take mail down with the change. Providers offer workarounds under names like ALIAS, ANAME or CNAME flattening, and those are what you should use.
The second is pasting a full hostname into a field that already appends your domain, creating a record with your domain in it twice. It looks correct in the form and never resolves. The third is chaining, where a CNAME points at another CNAME which points at a third: every hop adds a lookup and another place for the whole thing to break silently.
Getting CNAMEs right
Copy the value the platform gives you character for character, then work out how your panel treats the host field, because some expect only the subdomain and some expect the whole name. Save it and look the record up from outside your own network before you press verify, since a failed verification often drops the platform into a retry cycle you then have to sit through.
Clear out records for services you have stopped paying for. A subdomain still aliased to a platform you cancelled can be claimed by whoever registers that name there next, which is how businesses end up serving other people’s content on their own domain. Make a zone review part of cancelling any tool, alongside revoking its logins.
