DNS A Record vs CNAME

Question

What is the difference between an A record and a CNAME record in DNS, and when would you use each?

Accepted Answer

Both A records and CNAME records are fundamental DNS resource record types essential for mapping human-readable domain names to their corresponding network locations. While both facilitate name resolution, they operate with distinct mechanisms and serve different strategic purposes in DNS configuration. An A (Address) record directly maps a hostname or domain name to an IPv4 address. For example, `example.com` would resolve to a specific IP address like `192.0.2.1`. You primarily use an A record when you know the exact IPv4 address of the server hosting your content and need a direct, explicit mapping. It's the standard record type for your domain's root or "apex" (e.g., `yourdomain.com`), as it allows the domain to function independently without relying on another name. A CNAME (Canonical Name) record, conversely, creates an alias from one domain name to another canonical, or "true," domain name. For instance, `www.example.com` could be a CNAME pointing to `example.com`, or `blog.example.com` could point to a third-party blogging service's hostname like `bloghost.provider.com`. When a CNAME record is queried, the DNS resolver performs an additional lookup for the target canonical name to find its associated A record or other record types. You would typically use an A record for your domain's apex and any subdomains requiring a direct, stable IPv4 mapping. CNAMEs are beneficial for flexibility and convenience, allowing you to point multiple subdomains or services to a single canonical name. This means if the IP address of the canonical name changes, you only update one A record, and all CNAMEs automatically resolve to the new address. A crucial limitation is that a CNAME record cannot be used at the root or apex of a domain (e.g., `yourdomain.com`) because it would conflict with other essential records like SOA and NS. For apex aliasing, some DNS providers offer proprietary "ALIAS" or "ANAME" records that effectively resolve this limitation. Selecting between an A record and a CNAME record hinges on whether you require a direct IP mapping or an alias to another hostname. A clear understanding of these differences, especially the implications for the domain apex, is critical for designing a robust, efficient, and easily maintainable DNS infrastructure.

DNS A Record vs CNAME

Ready to prove your AWS networking knowledge?

How DNS Resolution Works

DNS Propagation Basics

Purpose of a CDN

DNS Resolution Failure

Clients Using Stale DNS Cache

Paginated vs. Bulk API Calls: Performance, Cost, and Reliability Trade‑offs

EKS Cluster Upgrades: A Production Runbook for Platform Teams