What Is CNAME Record?

At a glance

Instead of holding an IP address, CNAME continues resolution at a target name. It commonly connects custom domains to SaaS, CDN and hosting platforms.

Why CNAME points to a name rather than an address

A Canonical Name record delegates resolution of an alias to another domain name. For example, www.example.com can point to a CDN or SaaS target, whose A or AAAA records are then resolved. The platform can change infrastructure without repeatedly asking customers to change IP addresses.

A name with a CNAME normally cannot also hold other ordinary DNS data because it declares itself an alias. A zone apex needs NS and SOA, so traditional DNS cannot place an ordinary CNAME there. Providers offer ALIAS, ANAME or flattening features to provide a similar experience.

Following an alias chain

• Resolution follows each CNAME target until it finds an address or an error. Every layer may have its own TTL.
• CDNs, object storage, support systems and hosting services often require a specific CNAME to attach a custom domain to their routing platform.
• Long chains add initial lookup steps. Loops, nonexistent targets or DNSSEC failures can prevent the name resolving successfully.
• The target platform can change subsequent addresses, but customer certificates, domain verification and service bindings still require appropriate maintenance.

Migration and dangling CNAME records

Deleting a third-party project without removing its DNS alias may leave a target resource that someone else can claim. Whether this enables subdomain takeover depends on the platform's verification and claiming rules, but dangling aliases deserve cleanup.

Verify the domain and certificate on the new platform before switching. Remove obsolete aliases after unbinding the old service. Regular inventories of subdomains, target resolution and platform responses reduce long-lived abandoned configuration.

Practical use and interpretation

A CNAME target is directly observable. Its suffix may suggest a CDN, builder or SaaS provider, but custom domains, white-label services and layered routing can obscure the product. Combine certificate, page and response evidence.

No CNAME does not rule out a CDN: A or AAAA can point directly to edges. Failed lookups leave the state unknown. Confirmed direct address records support the narrower statement that this name is not continuing through a CNAME.

Points to consider

The target can identify a platform in the resolution chain, but not necessarily the provider of the entire website infrastructure.

Frequently asked questions

Can CNAME point to an IP address?

No. Its target is another name. Use A for IPv4 and AAAA for IPv6 addresses.

Why is an ordinary apex CNAME usually invalid?

The apex must also hold SOA and NS records, while a CNAME normally cannot coexist with other data. Some providers emulate apex aliases through flattening.

Does a platform CNAME prove the whole site is hosted there?

It establishes that the name's resolution chain passes through that target. Pages, APIs, mail and origins may use different providers.