mail us  |  mail this page

contact us
training  | 
tech stuff  | 

Canonical Name Record (CNAME)

A CNAME record maps a single alias or nickname to the real or Canonical name which may lie outside the current zone. Canonical simply means the expected or real name.


name  ttl  class   rr     canonical name 
www        IN      CNAME 

The following fragment shows the use of CNAME RRs to map web and ftp services to a single host.

; zone fragment for
$TTL 2d ; zone default = 2 days or 172800 seconds
server1    IN      A
www        IN      CNAME  server1
ftp        IN      CNAME  server1

CNAME RRs incur performance overheads. The most common DNS query is for an A RR, or an AAAA RR if IPv6 - the end system needs an address which is only defined with these RR types. In the above example if a query for the address of is received, two look-up operations are performed on the master or slave server. The first finds which finds a CNAME RR. This is followed by a query for to obtain the IP, that is, the CNAME chain is followed to attempt to resolve the request for an IP address. On low volume DNS servers the additional resources used are not significant but on high volume servers the additional load can become non-trivial. The user must make a choice to balance what many see as the convenience of using CNAME RRs against the possible performances degradation involved.

CNAME RRs cannot have any other RRs with the same name, for example, a TXT - well that was true until DNSSEC came along and in this case RRSIG, NSEC and certain KEY RRs can now occupy the same name.

While use of CNAME RRs with NS and MX records is widely implemented and generates a working configuration it is theoretically not permitted (RFC 1034 section 3.6.2) since it can result in lost names. The fragment below illustrates a widely used but technically invalid configuration.

; zone fragment for
$TTL 2d ; zone default = 2 days or 172800 seconds
           IN      MX  10
mail       IN      CNAME   server1
server1    IN      A

In the above configuration when a query is issued for the A RR of the result will return both the CNAME RR and the A RR. When the A RR is used the name associated with the CNAME can be lost, that is, there is a valid MX record referencing the host and an A RR referencing but nothing joins the two records. The fragment below, by re-ordering the RRs, will achieve the same result and allow a valid mapping of the MX name to the A RR name.

; zone fragment for
$TTL 2d ; zone default = 2 days or 172800 seconds
           IN      MX  10
server1    IN      CNAME   mail
mail       IN      A

For many users the above feels uncomfortable because the real host name is not Bear in mind that the DNS system simply maps a name used externally to an IP address - irrespective of the host's name in its local configuration file or whatever it answers to a hostname command.

You can map CNAME records to another CNAME record but this is considered bad practice since queries will follow the CNAME chain and look for the A record which uses more DNS resources. CNAME loops can also inadvertently result from such a procedure.

You can redefine a single IP to have multiple names using standard A records which is functionally the same as a CNAME for entries within a zone.

; zone fragment for
$TTL 2d ; zone default = 2 days or 172800 seconds
server1    IN      A
www        IN      CNAME  server1

; following is functionally identical
; but incurs no CNAME lookup overhead
server1    IN      A
www        IN      A

In our view the only time that a CNAME is required (there is no alternative) is when you want to alias a host in the current domain to an external domain as shown below:

; zone fragment for
$TTL 2d ; zone default = 2 days or 172800 seconds
; www service internal to domain
www        IN      A
; CNAME used to map ftp service to an external host
ftp        IN      CNAME

Examples & Variations

; zone file fragment for
joe        IN      A   
www        IN      CNAME  joe ;canonical name is
www        IN      CNAME ; exactly the same as above
ftp        IN      CNAME ; bad practice
; better practice to achieve same result as ftp CNAME above
; by re-defining the same physical host with 2 A records
ftp        IN      A

; next line redirects to
bill       IN      CNAME

; this is theoretically invalid - but widely implemented
           IN      MX 10
mail       IN      CNAME

; classic and access
; resolves to an IP
           IN      A
www        IN      CNAME
; could also be defined as 
           IN      A
www        IN      A

If you are concerned about when to use the dot and when not at the end of a line.

Problems, comments, suggestions, corrections (including broken links) or something to add? Please take the time from a busy life to 'mail us' (at top of screen), the webmaster (below) or info-support at zytrax. You will have a warm inner glow for the rest of the day.

Pro DNS and BIND by Ron Aitchison


tech info
guides home
dns articles
1 objectives
big picture
2 concepts
3 reverse map
4 dns types
5 install bind
6 samples
7 named.conf
8 zone records
9 howtos
10 tools
11 trouble
12 bind api's
13 dns security
bits & bytes
15 messages
notes & tips
registration FAQ
dns resources
dns rfc's
change log

Creative Commons License
This work is licensed under a Creative Commons License.

If you are happy it's OK - but your browser is giving a less than optimal experience on our site. You could, at no charge, upgrade to a W3C STANDARDS COMPLIANT browser such as Firefox




share page via facebook tweet this page


email us Send to a friend feature print this page Decrease font size Increase font size Display full width page



Debian Linux


GNU-Free SW Foundation


Open Source Initiative
Creative Commons


Ibiblio - Library
Open Book Project
Open Directory


CSS Technology SPF Record Conformant Domain
Copyright © 1994 - 2015 ZyTrax, Inc.
All rights reserved. Legal and Privacy
site by zytrax
Hosted by
web-master at zytrax
Page modified: October 21 2015.