What Is a CNAME Record?

What Is a CNAME Record?

A CNAME record (“Canonical Name” record) maps one hostname to another hostname, rather than to an IP address directly. When a resolver looks up a name with a CNAME record, it follows the chain to the target hostname. It then resolves that target’s own record — usually an A record — to get the final IP address.

How a CNAME Record Works

Instead of hardcoding an IP address, a CNAME says “this name is really just an alias for that name — go look there.” This is useful whenever the underlying IP might change without notice. The CNAME never needs updating — only the target’s own A record does. It’s the standard mechanism for pointing www.example.com back at example.com. It’s also used for connecting a subdomain to a third-party platform, such as an email service, a helpdesk tool, or a landing-page builder, without needing to know or track that platform’s IP addresses.

Step-by-Step: Setting Up a CNAME Record

1. Get the target hostname from the destination — the root domain for a www setup, or the specific hostname a third-party service provides.
2. Log in to the DNS management panel.
3. Create the CNAME record, entering the subdomain (e.g. www or shop) as the name.
4. Enter the target hostname as the value — never an IP address, which belongs in an A record instead.
5. Set the TTL.
6. Save and verify once propagation completes, checking that the chain resolves correctly to a final IP.

Timing and Propagation

CNAME records propagate on the same general timeline as other DNS records — typically within a few hours, up to 48 hours in rare cases. A CNAME points to another hostname that resolves separately, so total resolution time technically includes both the CNAME’s own propagation and the target hostname’s current DNS state. In practice this rarely adds noticeable delay.

Field Reference

• Name/Host — the subdomain being configured (www, shop, mail, etc.); a CNAME cannot be set on the bare root domain (@) under standard DNS rules.
• Type — CNAME.
• Value/Target — the hostname being pointed to.
• TTL — cache duration in seconds.

For a full side-by-side of every record type, see DNS record types.

Troubleshooting CNAME Record Issues

• “Record conflicts” error when saving: a name can only hold a CNAME or other record types, never both. Check for an existing A, MX, or TXT record on the same name first.
• CNAME set but subdomain shows an error: confirm the target hostname itself resolves correctly. Also check that the receiving platform has been configured to accept traffic for this specific subdomain — see what is a subdomain.
• Can’t set a CNAME on the root domain: this is a DNS-standard restriction; use an A record on the root, and reserve CNAME for subdomains like www.
• SSL error after setting up a CNAME: the destination service usually needs the subdomain manually added and verified on its end before it will issue a certificate for it.

Relationship to Hosting

CNAME records are central to creating a subdomain. They’re one of the two standard ways, alongside the A record, to point a domain at hosting. They’re especially common when a business layers third-party tools — email marketing, help desks, landing page builders — onto subdomains of their main hosted domain, without those tools needing to manage IP addresses directly.

FAQ

Can I use a CNAME record on my root domain? No — standard DNS rules prohibit a CNAME on the bare root (apex) domain; use an A record there instead, and CNAME for subdomains.

Why use a CNAME instead of just another A record? A CNAME automatically follows the target’s current IP, so it never needs updating if that IP changes. An A record would need manual updates every time.

Does a CNAME record slow down page loading? The extra resolution step is negligible in practice. Modern DNS resolvers handle CNAME chains quickly, and any measurable delay is far smaller than typical page-load variance.

Can I chain multiple CNAME records together? Technically yes, but it’s discouraged — each extra hop adds resolution overhead and complexity; pointing directly at the final target is the standard best practice.