Ben Golding wrote: > I've been having a lot of trouble recently with the nameserver on snv_101b > (and earlier). Specifically, during the install/upgrade process, the > /etc/resolv.conf is changed to look like: > > search object-craft.com.au > domain object-craft.com.au > nameserver 192.168.0.3 > > Odd, I normally see the order
domain nameserver search when selecting "dns" for the nameservice, which matched the order from the installer. > According the DNS and Bind book, the "search" and "domain" directives are > mutually exclusive. Bind enforces this by making the one that appears last > override the other. > > As a result, the search domain is set to "object-craft.com.au" and "com.au". > For domains with less dots in them, ndots probably forestalls this happening, > ie, frobozz.com doesn't set the search path to "frobozz.com" and "com". > > That works fine usually except when I try to reference "localhost". Some > bozo has registered "localhost.com.au" so that is discovered before the > resolver falls back to the localhost entry in /etc/hosts. > > What are the host and ipnodes entries in your /etc/nsswitch.conf? files dns should fix that issue. -- Ian.
