Skip to content
AdminKit

CNAME record

What is CNAME record?

A CNAME record, defined in RFC 1035, is a DNS entry that makes one domain name an alias for another, telling resolvers to look up the target name instead of returning an address directly. AdminKit's DNS lookup tool resolves CNAME records alongside A, MX, TXT and other record types.

By AdminKit team, Netbase JSC · Updated

A CNAME (Canonical Name) record is a DNS entry that makes one domain name an alias for another, telling resolvers to look up the other name instead of returning an address directly. Defined in RFC 1035 and listed as type 5 in IANA’s DNS Parameters registry, it’s the standard way to point a subdomain at a service you don’t control the IP address for — a custom domain pointed at a CDN, a SaaS vendor’s hosting, or an email-marketing platform’s tracking domain are common examples — since the target’s own address can change without the CNAME needing to be updated. RFC 1035 also means a CNAME record cannot coexist with any other record type on the same name, and most DNS providers don’t allow a domain’s root/apex record to be a CNAME at all, which is why services needing root-domain aliasing use provider-specific ALIAS or ANAME records instead. Microsoft’s Azure DNS alias records overview is one provider’s version: it notes that the DNS protocol prevents CNAME records at the zone apex and uses alias record sets so applications can still be hosted at the apex. That same coexistence rule is also why RFC 2181 bars an MX record’s target from being a CNAME — see when an MX record points to a CNAME for what that specific, invalid combination does to mail delivery. A SaaS platform routing every customer’s subdomain to the same target often does that with a wildcard DNS record pointing at one CNAME, rather than creating a CNAME per customer. Email platforms use CNAMEs too: Shopify custom domain email authentication relies on CNAME records that point to names Shopify controls for DKIM and SPF.

CNAME rules worth remembering:

  • A CNAME can’t coexist with any other record type on the same name (RFC 1035).
  • Most providers block a CNAME at the root/apex — use ALIAS or ANAME there instead.
  • RFC 2181 forbids an MX record from pointing at a CNAME target.

AdminKit groups cNAME record under its DNS cluster — browse the AdminKit glossary index for other related terms.

Frequently asked questions

Can a CNAME record coexist with other records on the same name?

No -- RFC 1035 says a CNAME record cannot coexist with any other record type on the same name, which is why a domain's root/apex is usually blocked from being a CNAME at all (it needs other records like MX and NS).

Why can't a domain's root use a CNAME?

Most DNS providers don't allow a domain's root/apex record to be a CNAME, since RFC 1035's coexistence rule would then block every other record type the root also needs, such as MX and NS. Services needing root-domain aliasing use provider-specific ALIAS or ANAME records instead.

Can an MX record point to a CNAME?

No -- RFC 2181 specifically forbids an MX record's target from being a CNAME, because of the same coexistence rule that keeps a CNAME from sharing a name with any other record type.

Why would a site use a CNAME instead of an A record?

A CNAME points a subdomain at a service you don't control the IP address for -- a custom domain pointed at a CDN, a SaaS vendor's hosting, or an email-marketing platform's tracking domain are common cases -- so the target's own address can change without the CNAME needing to be updated.