Date: Sun, 4 Jul 2004 22:33:46 -0700 (PDT) From: Bill Schoolcraft <bill@wiliweld.com> To: David Fuchs <david@davidfuchs.ca> Cc: Kevin Stevens <freebsd@pursued-with.net> Subject: Re: [Fwd: /etc/hosts and /etc/host.conf confusion] Message-ID: <20040704222946.A68094@bsd.billschoolcraft.com> In-Reply-To: <40E856B9.30601@davidfuchs.ca> References: <40E62A8C.1040908@davidfuchs.ca> <B5AD052E-CCAB-11D8-8439-000A959CEE6A@pursued-with.net> <40E856B9.30601@davidfuchs.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
At Sun, 4 Jul 2004 it looks like David Fuchs composed: > Excellent, ping does resolve a new entry in /etc/hosts properly. So as > you said, `host' is doing it's own thing. The manpage for host gives me > some leads which I'll follow through on. Hmm, in the Unix boxes I've seen, there is a file called /etc/nsswitch.conf that will have a line called "hosts:" it will dictate the order by which names are resolved. If you have the following your system will look at the /etc/hosts file first, then NISplus, then DNS. If you were to have "dns" first, it would ignore your /etc/hosts file (first) and hit your dns looking for answers. /etc/nsswitch.conf hosts: files nisplus dns -- Bill Schoolcraft PO Box 210076 -o) San Francisco CA 94121 /\ "UNIX, A Way Of Life." _\_v http://billschoolcraft.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040704222946.A68094>