Re: Strange resolve problem
- From: Ian Northeast <ian@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 03 Apr 2007 02:07:53 +0100
On Mon, 02 Apr 2007 16:32:45 -0700, phwashington wrote:
It was the nsswitch.conf file. I've never had this happen before when I
was setting up a system.
It had
hosts: files nis dns
set it to
hosts: files dns nis
or
hosts: dns files nis
and it works just fine.
Unless you have some specific reason to do so I suggest that you do not
use NIS at all for name resolution. You didn't mention in your OP that
you were doing so, otherwise I would have commented on it. I have never
seen any distro insert it by default so I assume you have added it. Why?
It is conventional to use "files dns" for the hosts resolution order, with
good reason. Most answers will come from DNS, the service designed for the
purpose, but you can override it on a per machine basis by adding
/etc/hosts entries. Additionally, putting a machine's local addresses into
its own /etc/hosts enables it to resolve itself if the DNS server or
network is down.
If you use NIS for host resolution then, unless you take special steps
when generating the map, you are propagating the NIS master's hosts file
to all the clients. Which is normally not what you want. In your case it
appears that an erroneous hosts file, with its owner's name attached to
127.0.0.1, got propagated thus.
NIS is best used for users, groups, netgroups and (arguably) services.
Whatever Sun say:)
Regards, Ian
.
- References:
- Strange resolve problem
- From: phwashington
- Re: Strange resolve problem
- From: Ian Northeast
- Re: Strange resolve problem
- From: phwashington
- Strange resolve problem
- Prev by Date: Re: Disabling floppy drive? (since broken)
- Next by Date: Licensing (was: ANN: Microsoft goes Open Source)
- Previous by thread: Re: Strange resolve problem
- Next by thread: Re: A Suggestion For Higher-Quality Open-Source Software
- Index(es):
Relevant Pages
|
