CNAMES are a double lookup.
Not as significant as in days gone by... but still it is a double lookup.
--
greg@gregfolkert.net PGP key 1024D/B524687C 2003-08-05 Fingerprint: E1D3 E3D7 5850 957E FED0 2B3A ED66 6971 B524 687C |
|
So when would you prefer a cname?
There's got to be a reason for them, right?
--
Drew |
|
They're basically an alias.
It's been a while since I've done much in a zone file, but if you had several dozen names pointing to the same IP address, you could use CNAMEs for most of them and keep the IP address on one. This is good if the IP address is updated in the zone file much.
It's also good if you need to point a name to one in another domain. Wade Just Add Story http://justaddstory.wordpress.com/
|
|
The way *I* typically use them...
A Record is the proper full name of the host (i.e. uno.gregfolkert.net)
[greg@lanai WG3 ~]$ dig uno.gregfolkert.net CNAME is any other name I give it: www.gregfolkert.net, mail.gregfolkert.net or just gregfolkert.net [greg@lanai WG3 ~]$ dig www.gregfolkert.net CNAME for my nearly static IP Address at home, owned by comcast: archer.gregfolkert.net is a CNAME for c-98-209-73-13.hsd1.mi.comcast.net. [greg@lanai WG3 ~]$ dig archer.gregfolkert.net If you notice there are two lookups. --
greg@gregfolkert.net PGP key 1024D/B524687C 2003-08-05 Fingerprint: E1D3 E3D7 5850 957E FED0 2B3A ED66 6971 B524 687C |