domain names not resolving

[Jeff Lasman]

On Wednesday 21 March 2007 02:14 am, Lucien GENTIS wrote:

> It could be a problem in case of a host which should use this DNS
> server for name resolving
> and have "dns, files" in its nsswitch.conf.
> Wouldn't any call to localhost be resolved to 207.228.252.47 instead
> of 127.0.0.1 ?

Notice the lack of trailing dot on "localhost"; the nameserver will 
return 207.228.252.47 only for calls to "localhost.kirkyonline.com".  
While many zonefiles continue to have a localhost.<domain> construct 
I'm not sure that anything ever uses it, even if anything ever did.

> >> In addition, if ns0 corresponds to 207.228.252.47 ,
> >> I think www and mail must have CNAME records instead of A record
> >> since they correspond to the same IP address.

There are almost no advantages to using CNAME to point to a field in the 
same zone (the only advantage is that you'll only have to change the 
IP# once if/when you ever have to change the IP# in the zonefile), and 
one major disadvantage; every lookup for (for example www) becomes two 
lookups.

Jeff
-- 
Jeff Lasman, Nobaloney Internet Services
P.O. Box 52200, Riverside, CA  92517
Our blists address used on lists is for list email only
voice:  +1 951 643-7540, or see: 
"http://www.nobaloney.net/contactus.html"