On Tue, 8 Jul 2003, Harry Putnam wrote: > Harry Putnam <reader@xxxxxxxxxxx> writes: > > > I see absolutely no difference at all. > > > > host reader.local.net1 returns: > > Host reader.local.net1 not found: 3(NXDOMAIN) > > > > nslookup returns: > > > > Server: 192.168.0.20 > > Address: 192.168.0.20#53 > > > > ** server can't find reader.local.net1: NXDOMAIN > > I spoke too soon. There is a major difference. Any reslotion > on the internet is completely broken with that in place. > > None of the usual tools can resolve anthing, connections fail etc. > > Setting it back to: > hosts: files dns This is correct. It will first look in /etc/hosts and if it cannot find what it needs there it will consult the name servers listed in /etc/resolv.conf. > And it starts working again. By working I mean nslookup can resolve > alpha names to numbers etc, but only outside my little home network. I missed the beginning of this thread but you could always setup an internal name server if you are trying to resolve internal only names as well as names out on the big bad internet. It is IMO simpler than maintaining /etc/hosts files on multiple computers. HTH, -- ......Tom Registered Linux User #14522 http://counter.li.org tdiehl@xxxxxxxxxxxx My current SpamTrap -------> mtd123@xxxxxxxxxxxx
