A Record vs CNAME: Which One Should Actually Point Where

Two Records, One Overlapping Job — With Real Rules Underneath

An A record points a name directly at an IPv4 address. A CNAME points a name at another name, which then has to be resolved further to actually get an address. On the surface it can look like a stylistic choice — pick whichever, they both "get you there" — but underneath, DNS enforces hard rules about where each is allowed, and ignoring them causes real, sometimes confusing failures rather than a graceful fallback.

This is the dedicated comparison: not just what each record does, but exactly where the rules force one over the other, what CNAME chaining costs in practice, and a decision framework you can apply to any hostname you're configuring.

The Rule That Decides Most of This: The Apex Restriction

The single most important constraint in this whole comparison is that a domain's apex (root) — example.com with no subdomain in front of it — cannot use a CNAME. The apex must simultaneously hold other required record types, most importantly NS records delegating the zone and an SOA record describing it, and DNS specification forbids a CNAME from coexisting with any other record type at the same name. Since those other records are mandatory at the apex, a CNAME simply isn't an option there. This single rule is why apex domains are so often configured with a plain A record even when the underlying infrastructure (a CDN, a load balancer with a changing IP) would otherwise make a CNAME-style pointer more convenient.

What CNAME Chaining Actually Costs

A CNAME can point at another CNAME, which points at another, and so on, though most providers and best practice strongly discourage chains beyond one or two hops. Each hop in the chain is a genuinely separate DNS lookup the resolver must perform before it finally reaches a name with an actual A (or AAAA) record to terminate on. On a cold, uncached query, this adds real, if usually small, latency — each hop is another round trip through however much of the resolution hierarchy hasn't already been cached. On a warm/cached query, the overhead mostly disappears since the whole chain gets cached together, but a cold lookup with a three-hop chain is measurably slower than a single-hop A record answer.

ALIAS/ANAME: The Workaround for Apex + Dynamic Target

Because so many services want you to "point a CNAME at us" and so many organizations want that flexibility at their apex domain specifically, several DNS providers offer a non-standard record type — commonly called ALIAS or ANAME — that behaves like a CNAME from the configuration side (point it at a hostname, not an IP) but is resolved by the provider's own infrastructure into a plain A record answer before it's ever returned to a querying resolver. This satisfies the apex restriction because, as far as the outside world can tell, the apex is still only publishing an A record — the CNAME-like behavior is an internal implementation detail of that specific DNS provider, not a real CNAME on the wire.

Decision Framework

Interaction With Email and Other Records

A related, often-missed rule: because a CNAME can't coexist with any other record at the same exact name, a hostname configured as a CNAME also can't simultaneously have an MX record. If a subdomain needs to both serve web traffic via CNAME and receive mail directly, that combination isn't possible at the same name — mail routing for that specific hostname would need to be handled differently, often by using a separate, dedicated subdomain for the mail-receiving purpose instead of overlapping the same name.

Performance: Is the CNAME Overhead Actually Meaningful?

In absolute terms, one additional DNS lookup hop typically costs single-digit to low double-digit milliseconds on a cold query — not something a human perceives directly, and irrelevant once the answer is cached for the TTL duration. It becomes worth actively avoiding mainly in two situations: extremely latency-sensitive applications where every millisecond of a cold-path request is being optimized, and deep CNAME chains (three or more hops) where the cumulative cost is no longer trivial. For the overwhelming majority of ordinary websites and services, the practical performance difference between a well-configured CNAME and a direct A record is not something worth losing sleep over.

Common Mistakes

Related Tools

Check whether a hostname currently resolves via A record or CNAME with DNS Lookup, which shows every record type at once. For a fast, focused A-record-only check, use A Record Lookup. To confirm a DNS change involving either record type has propagated, use DNS Propagation Checker.