A Record vs CNAME Record: What Is the Difference?
The DNS system is key for matching domain names with online services. The information that will help in resolving a hostname into a server comes from the DNS records. There are many DNS record types among which are the A and CNAME records. But these two records do not serve the same purpose.
While the A record connects a hostname to an IPv4 address, the CNAME record connects a hostname to another hostname. Though the difference might seem minor, it changes how you set up your domain, subdomain, third-party services, and changes in your infrastructure. It is thus crucial to learn about A Record vs CNAME Record when managing DNS.This task becomes simpler once you know what information they hold, how DNS uses it, where you can use them, and the limitations of each.In this guide, we are going to walk through the differences between them one step at a time.
What Is a DNS Record?
DNS record refers to an organized entry in the Domain Name System which contains details regarding a domain name or a hostname. Several kinds of DNS records are available and each serves its own purpose. A record refers to an IP version 4 address. AAAA refers to IP version 6 addresses. CNAME refers to another hostname. MX records refer to mail servers whereas TXT stores information in text format which is used for verification purposes.
DNS resolver makes use of the right kind of DNS record when handling a particular query to find out how the hostname should be resolved. This information is stored in the DNS servers which are authoritative to the particular domain. This information can then be retrieved by recursive DNS servers. Thus, DNS records are the configuration layer of the DNS system. In the case of comparing A record and CNAME record, the major difference lies in the contents of both records since one gives an address, whereas another one gives another name.
What Is An A Record?
How Does an A Record Work?
An A record will return an IPv4 address in response to a DNS query to the relevant hostname. For instance: app.example.com A 192.0.2.10 A resolver sending out the query for app.example.com will get the IPv4 address 192.0.2.10 back in response. This IPv4 address can be kept by the resolver in its cache based on the Time to Live, or TTL value of the record. TTL denotes how long the DNS response can remain valid in the cache of a recursive resolver before the resolver gets new information.
In case the server changes to a new IPv4 address from 192.0.2.10, then there would be the need for the update of the A record. From this point, the resolvers will keep returning the same IP address as long as the cached data is not expired. Therefore, this is a straightforward process whereby the resolver sends out the request for the hostname and gets the IPv4 address in response.
What Is a CNAME Record?
A CNAME or Canonical Name record is used to map one hostname to another hostname. For instance: www.example.com CNAME hosting.provider.example Contrary to A records, CNAME does not have an IP address. Rather, it indicates another DNS name as the destination and DNS can keep on resolving the destination to find out relevant addresses. The destination hostname might have an A record with IPv4 address, an AAAA record with IPv6 address, or both. CNAME records can prove to be helpful if a service provider provides you a hostname rather than an IP address.
Thus, it brings another step in the process of DNS resolution. The key difference is: A record: hostname → IPv4 address CNAME record: hostname → hostname And, this is the basis of the complete comparison between A Record and CNAME Record.
How Does a CNAME Record Function?
A CNAME instructs DNS that one hostname is the alias of another hostname. Consider: app.example.com CNAME service.provider.example When DNS receives a query for app.example.com, it identifies the CNAME and continues resolution using service.provider.example. The hostname can then resolve through its own DNS records. For example, if the hostname has: service.provider.example A 192.0.2.20 Then DNS will eventually get the IPv4 address 192.0.2.20.
If the provider changes the IP address of the hostname, DNS records can then be changed for the hostname without changing the CNAME itself. But there is a very significant limitation for CNAME records. The CNAME cannot be mixed with other DNS entries with the same owner name. This implies that you cannot have CNAME and A, AAAA, MX or TXT entries for the same hostname. (rfc-editor.org) There are some limitations of CNAME in the DNS zone apex, but we’ll talk about those another time.
Difference Between A Record and CNAME
There is more to the difference between an A record and a CNAME than simply that one contains an IP address and the other a hostname.
1. Destination type
2. Address changes for the destination
3. Compatibility
4. Root-domain behavior
5. IPv4 and IPv6
An A record gives information for IPv4. For IPv6, you need to have a AAAA record. The CNAME record itself does not define either of the address families.
6. Management model
A Record vs CNAME: Comparison Table
| Factor | A Record | CNAME Record |
|---|---|---|
| What it points to | An IPv4 address | Another hostname |
| DNS resolution | Returns the configured IPv4 address | Continues resolution using the target hostname |
| IPv4 support | Directly supported | Obtained through the target's records |
| IPv6 support | Use an AAAA record separately | Target may resolve through an AAAA record |
| Address changes | Record normally needs updating | Target's address can change without changing the alias |
| Same-name DNS data | Can coexist with other compatible records | Generally cannot coexist with ordinary DNS data at the same name |
| Subdomains | Supported | Commonly used |
| Zone apex | Commonly used | Standard CNAME restricted; provider-specific apex solutions may exist |
| Third-party services | Suitable when an IPv4 address is provided | Suitable when a hostname is provided |
| Management approach | Direct IP management | Hostname-based delegation |
When to Use an A Record
Use an A record when the service you are configuring provides an IPv4 address and expects the hostname to resolve directly to that address.
- An A record is a suitable choice when:
- Your hosting provider gives you a fixed IPv4 address.
- You operate a server with a known IPv4 address.
- A service specifically requires an A record.
- You need direct IPv4 resolution.
- The hostname needs to coexist with other compatible DNS records.
- Records are particularly convenient when the destination address remains stable.
If the IPv4 address changes, however, you need to update the DNS record. That requirement becomes more important when infrastructure changes frequently. For IPv6, use an AAAA record alongside the A record when the service and network configuration support both address families.
When to Use a CNAME Record
Use a CNAME when you need a hostname to resolve through another hostname. A CNAME is commonly appropriate when:
- A service provider gives you a hostname instead of an IP address.
- The provider manages the destination infrastructure.
- You are configuring a subdomain for an external service.
- The provider specifically instructs you to create a CNAME.
You want the alias to continue following the target hostname when its IP addresses change. For example, if a provider tells you to point app.example.com to service.provider.example, the expected DNS configuration is a CNAME. Before creating it, though, check whether the hostname already has other DNS records. A CNAME generally cannot coexist with those records with the same name. Also, check whether you’re configuring a subdomain or the zone apex because standard CNAME rules treat those locations differently.
A Record vs CNAME for Root Domains and Subdomains
A major difference appears when you configure the root domain. The root domain is also called the zone apex. For example.com, the zone apex is example.com itself. Under traditional DNS rules, you cannot place an ordinary CNAME at the zone apex because that name must also contain essential DNS records such as SOA and NS. A CNAME’s exclusivity requirement conflicts with those records. (rfc-editor.org) As a result, A and AAAA records are commonly used for root-domain address mapping.
Subdomains offer more flexibility. A hostname such as www.example.com can generally use a CNAME because it is not the zone apex. This is why third-party services often instruct users to create CNAME records for specific subdomains.
However, DNS providers can implement additional functionality. CNAME flattening allows some providers to support CNAME-style configurations at the zone apex by resolving the target and returning address information instead of exposing the CNAME directly. (developers.cloudflare.com) Other providers may offer ALIAS or ANAME-style records. Therefore, don’t treat root-domain CNAME support as universal. Check the DNS provider’s documentation before configuring an apex hostname.
A Record vs CNAME: Advantages and Limitations
A Record Advantages
A records offer a direct and widely supported way to map a hostname to an IPv4 address. Key advantages include:
- Direct IPv4 mapping
- Simple configuration
- Broad compatibility
- Common support for root domains
- Ability to coexist with other compatible DNS records
- Direct control over the configured IPv4 destination
They work especially well when the IPv4 address is stable and known.
A Record Limitations
The main limitation is that an A record stores the IPv4 address directly. If that address changes, the DNS record normally needs to be updated. An A record also does not provide IPv6 addressing. You need an AAAA record for IPv6. Therefore, services supporting both IPv4 and IPv6 may require separate A and AAAA records. A record can also require more manual maintenance when a third-party provider frequently changes the IP addresses behind its service.
CNAME Advantages
CNAME records provide hostname-based routing within DNS. Their main advantages include:
- Pointing a hostname to another hostname
- Convenient subdomain configuration
- Less need to track changing target IP addresses
- Useful integration with external services
- Ability to follow the target hostname’s current address records
This can simplify DNS management when another provider controls the underlying infrastructure.
CNAME Limitations
CNAME records have stricter DNS rules. A CNAME cannot directly point to an IP address. Its target must be a hostname. (rfc-editor.org) A CNAME also generally cannot coexist with other ordinary DNS data at the same hostname. That restriction can create problems if the hostname needs an A, AAAA, MX, TXT, or other record. (rfc-editor.org) Finally, traditional DNS does not permit an ordinary CNAME at the zone apex. Some providers work around this through CNAME flattening or other provider-specific mechanisms.
A Record and CNAME Configuration Examples
A Record Example
A basic A record can be configured as:
- Type: A
- Name: app
- Value: 192.0.2.10
- TTL: 3600
For a domain such as example.com, the app hostname becomes: app.example.com The DNS server returns 192.0.2.10 when the relevant A record is queried. If the IPv4 address changes, the value of the A record needs to be updated. An IPv6 configuration would use a separate AAAA record:
- Type: AAAA
- Name: app
- Value: 2001:db8::10
- TTL: 3600
The two records can provide IPv4 and IPv6 addressing for the same hostname. CNAME Example A basic CNAME can be configured as:
- Name: app
- Value: service.provider.example
- TTL: 3600
This makes:
- app.example.com
- an alias for:
- service.provider.example
DNS then resolves the target hostname according to its own records. If the target’s IPv4 or IPv6 addresses change, the CNAME can remain unchanged as long as the target hostname remains correct. The hostname containing the CNAME should not simultaneously contain conflicting ordinary DNS records.
Common A Record and CNAME Configuration Mistakes
Several DNS configuration errors occur because A and CNAME records look similar in DNS management interfaces. The first mistake is putting an IP address into a CNAME record. A CNAME must contain a hostname. Use an A record for an IPv4 address and an AAAA record for an IPv6 address. Another common mistake is creating a CNAME alongside an A or AAAA record at the same hostname. A CNAME generally cannot coexist with other ordinary DNS data at that name. (rfc-editor.org).
The same issue can occur with MX and TXT records. If a hostname needs those records, placing a CNAME at that exact name can create a conflict. Root-domain configuration is another frequent source of confusion. A typical CNAME record cannot be used at the zone apex level. If your DNS provider supports CNAME flattening or any other kind of apex solution, use the instructions provided by your DNS provider. Do not rely on a normal CNAME. Also, it is crucial to avoid mixing up DNS records and HTTP redirects. A CNAME will not redirect the browser from one URL to another URL. CNAME will modify the DNS resolution process. DNS changes might not be applied immediately to all locations because recursive DNS resolvers can store previously received answers based on the values of TTL. Do not replace an A record required by your DNS provider with CNAME just because both types of records ultimately point to the same service.
How to Decide Between A Record and CNAME
First, determine what the service has given you. If it is an IPv4 address, then choose an A record. If it is a hostname, then choose a CNAME. The second step is to identify the hostname to configure. As for a subdomain, a CNAME could be the way to go if the destination is a hostname. With the zone apex, determine whether the provider allows CNAME flattening, ALIAS, ANAME, or something else that works with an apex.
Next, verify whether the hostname will require any additional DNS records. In case the same hostname requires any MX, TXT, A, AAAA, or other standard DNS records, a CNAME might not be a good option due to its exclusivity. Finally, comply with the provider’s DNS instructions. There may be particular requirements from the provider to use an A record, AAAA record, CNAME, TXT record, or some combination of multiple records.
So, there are four factors that should be considered when deciding which record type to use: Destination that you have Where you want to create the record Whether any other DNS records are necessary at the same name DNS or service provider requirements Once all the above is clear, choosing between A record and CNAME record gets much easier.
Conclusion
The distinction between A Record vs CNAME Record comes down to what each record points to. A record assigns an IPv4 address to a hostname. CNAME assigns a hostname to another hostname for further resolution by DNS. Such differences have implications for IP addresses, compatibility of records, subdomains setup, third-party integrations, support of IPv6 and root-domain setup. Choose an A record if you need direct IPv4 address assignment. Choose CNAME if you want to use the hostname resolution of one hostname through another.
On the other hand, make sure to be especially careful about the zone apex. Standard DNS practices prohibit ordinary CNAME records here, but nowadays DNS service providers may offer apex support through CNAME flattening or similar technologies. The safest way is to find out the destination, check the hostname location within the DNS zone, consider additional records needed at this hostname, and consult service provider instructions on how to configure it. Taking into account all the above mentioned considerations, your choice of an A or CNAME record will become very obvious.
