Table of Contents
- What’s a CNAME record?
- CNAME record format
- CNAME and Redirect
- Querying CNAME records
- Manage CNAME records
What’s a CNAME record?
CNAME records can be used to alias one name to another. CNAME stands for Canonical Name.
A common example is when you have both
www.example.com pointing to the same application and hosted by the same server. To avoid maintaining two different records, it’s common to create:
example.compointing to the server IP address
As a result,
example.com points to the server IP address, and
www.example.com points to the same address via
example.com. If the IP address changes, you only need to update it in one place: just edit the A record for
www.example.com automatically inherits the changes.
A CNAME record must always point to another domain name, never directly to an IP address. DNSimple’s record editor will warn you if you try to point a CNAME record to an IP address. The sidebar to the right of editing the CNAME encourages you to visit the support article to learn the difference between A, CNAME, ALIAS, and URL records. It also warns you that CNAMEs must be unique to other records.
The DNS A record is specified by RFC 1035.
- A CNAME record must always point to another domain name and never directly to an IP address.
- A CNAME record cannot co-exist with another record for the same name. It’s not possible to have both a CNAME and TXT record for
- A CNAME can point to another CNAME, although this configuration is generally not recommended for performance reasons. When applicable, the CNAME should point as closely as possible to the target name in order to avoid unnecessary performance overheads.
CNAME record format
The structure of a CNAME record follows the standard top-level format definition defined RFC 1035. The RDATA section is composed of one single element:
|domain-name||A domain name which specifies the canonical or primary name for the record.|
The canonical representation is:
<domain-name> is a fully-qualified domain name such as
In DNSimple, the CNAME record is represented by the following customizable elements:
|Name||The host name for the record, without the domain name. This is generally referred to as “subdomain”. We automatically append the domain name.|
|TTL||The time-to-live in seconds. This is the amount of time the record is allowed to be cached by a resolver.|
|Content||The domain-name the CNAME maps to.|
CNAME and Redirect
The CNAME record is sometimes improperly referred to as redirect, generally in the context of web (HTTP) redirects.
There’s no direct correlation between a CNAME and an HTTP redirect, nor does configuring CNAME automatically result in any HTTP redirect.
To perform an HTTP redirect, the server responding to the HTTP request must be configured to return an appropriate HTTP response. This is not directly achievable using a CNAME.
You can learn more by reading the differences between the A, CNAME, ALIAS and URL records. DNSimple provides a special URL record that can be used to configure an HTTP redirect.
Querying CNAME records
You can use
dig in your terminal to determine the CNAME record associated to a domain name. The result contained in the
ANSWER section has the fully-qualified domain name (FQDN), the remaining time-to-live (TTL), and the domain-name.
$ dig CNAME www.dnsimple.com ; <<>> DiG 9.10.6 <<>> CNAME www.dnsimple.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 5274 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;www.dnsimple.com. IN CNAME ;; ANSWER SECTION: www.dnsimple.com. 3599 IN CNAME dnsimple.com. ;; Query time: 52 msec ;; SERVER: 126.96.36.199#53(188.8.131.52) ;; WHEN: Fri Nov 02 20:33:09 CET 2018 ;; MSG SIZE rcvd: 59
Manage CNAME records
From the DNSimple record editor you can add, remove, and update CNAME records.