On Fri, 29 Nov 2002 04:39, John H. Robinson, IV wrote: > Ben Armstrong wrote: > > Bah, that's what CNAME is for. > > that is _NOT_ what a CNAME is for. a CNAME is for when the hostname is > in a domain that is OUTSIDE of your control. > > ie: evil.debian.org -> www.msn.com = CNAME (we don't control the msn.com > domain) > forge.debian.org -> quantz.debian.org = A (we control the debian.org > domain, so we can save the internet by REDUCING THE NUMBER OF > UNNECESSARY DNS LOOKUPS AND REDUCE THE END USERS DELAY WITH DNS LOOKUP > REQUIREMENTS)
How does that save the Internet? DNS entries are cached and don't cause that much traffic. Having CNAME entries pointing to your own A records is OK, just as having symbolic links pointing to your own files on the same file system is OK. -- http://www.coker.com.au/selinux/ My NSA Security Enhanced Linux packages http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark http://www.coker.com.au/postal/ Postal SMTP/POP benchmark http://www.coker.com.au/~russell/ My home page