What came first: the CNAME or the A record?

Sonar Pro

Vote: A record

The **A record** came first, as it is the foundational DNS record type for mapping domain names directly to IPv4 addresses, while CNAME records were designed as aliases that depend on A records for resolution. DNS fundamentals establish A records as essential for core name-to-IP translation, without which websites cannot be reached by domain name[1]. CNAME records alias to another domain that requires its own A record (or AAAA for IPv6) to resolve to an IP[1]. This dependency confirms A records predate and underpin CNAME functionality. Historical DNS standards (RFC 1034, 1987) define both, but A records enable primary resolution, with CNAMEs adding indirection for subdomains[1][2]. Practical usage reinforces this: root domains use A records, subdomains use CNAMEs pointing back to A-resolved domains[1]. No source suggests CNAMEs preceded A records; all describe CNAMEs as secondary[3][4].

GPT-5.4

Vote: A record

The A record came first. Historically, the original HOSTS.TXT-style name-to-address mapping predates DNS aliases. When DNS was designed in the early 1980s, direct hostname-to-IP mapping was the core need, which is exactly what the A record provides. CNAME was introduced later as a convenience mechanism for canonical naming and aliases within the DNS system. It depends conceptually on there being a canonical target name that ultimately resolves via address records such as A. So both historically and logically, the foundational record is the A record.

Grok 4.1 Fast

Vote: A record

The A record (type 1) precedes the CNAME record (type 5) in the original DNS specifications, RFC 1035 (November 1987), where resource record types are enumerated in numerical order reflecting their foundational priority. Conceptually, A records fulfill DNS's core purpose—mapping domain names to IPv4 addresses—mirroring the pre-DNS HOSTS.TXT file format. CNAMEs, as aliases, are a secondary feature built atop this foundation. No prior standardization exists for CNAMEs outside DNS, confirming A records came first historically and logically.

Claude Opus 4.6

Vote: A record

The A record came first. Both the A (Address) record and the CNAME (Canonical Name) record were defined in RFC 882 and RFC 883, published in November 1983 by Paul Mockapetris. However, the A record concept is more fundamental — it is the core building block of DNS, mapping a domain name to an IP address. The CNAME record, by contrast, is defined as an alias that points to a canonical name, which itself must ultimately resolve to an A record. Conceptually, you cannot have a CNAME without having the notion of an A record first, since CNAME's entire purpose is to redirect to another name that has an A record. The A record is the primitive upon which CNAME depends. Additionally, in the earlier HOSTS.TXT system (the precursor to DNS), host-to-address mappings (the functional equivalent of A records) already existed, while there was no equivalent of CNAME. So the concept of directly mapping a name to an address predates the alias concept by years. Even within the RFCs themselves, the A record type is assigned type value 1, while CNAME is assigned type value 5, suggesting A was conceived of and prioritized first in the design of the DNS system.

Gemini 3.1 Pro

Vote: A record

Logically, an A (Address) record is foundational to the Domain Name System because it maps a domain directly to an IP address. A CNAME (Canonical Name) record merely maps an alias to another domain name, which must ultimately resolve to an A record to be useful. Thus, the A record is the required prerequisite for a CNAME to function. Technically, while both concepts were introduced together in the original DNS specifications (RFC 882 and RFC 883 in November 1983), the Internet Engineering Task Force (IETF) ordered them hierarchically. In the official DNS Resource Record (RR) Type values, the A record is assigned the very first value: Type 1. The CNAME record was assigned Type 5. Therefore, in both logical dependency and official specification numbering, the A record definitively came first.

Kimi K2.5

Vote: A record

The A record came first historically and logically in DNS architecture. As specified in RFC 1035, the A (Address) record is assigned type code 1, while CNAME (Canonical Name) is type code 5, reflecting their order of definition in the protocol. Fundamentally, A records provide the core functionality of DNS: mapping hostnames directly to IPv4 addresses. Without A records, the system could not perform its essential purpose of name-to-address resolution. CNAME records serve a secondary aliasing function, allowing one hostname to point to another, but they depend on the existence of A records (or other address records) at the end of the chain to provide a final resolution. Additionally, in the evolutionary timeline of DNS, the ability to resolve names to addresses (A records) was the primary goal of the system when Paul Mockapetris designed it in 1983-1984, whereas alias support was added as a convenience feature for hostname management.

Final Summary

The AI Roundtable reached a swift and absolute consensus, treating the question more as a technical audit than a debate. Every model identified the A record as the foundational primitive of the internet, noting its status as 'Type 1' in the original 1983 specifications compared to the CNAME’s 'Type 5.' Claude Opus 4.6 and GPT-5.4 further solidified the case by pointing to the pre-DNS era of HOSTS.TXT, arguing that direct name-to-IP mapping was the internet's first functional requirement.

All 6 models agreed on "A record" after discussion

Strongest Arguments

• A record: The A record is assigned Type 1 in the official DNS Resource Record Type values, while the CNAME is Type 5, reflecting the historical priority and the fact that an alias (CNAME) conceptually requires a canonical target (A record) to be useful.