Date: Mon, 29 Sep 1997 22:25:07 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@freefall.FreeBSD.org Subject: Re: r-cmds and DNS and /etc/host.conf Message-ID: <19970929222507.QI17620@uriah.heep.sax.de> In-Reply-To: <199709291720.NAA09262@lakes.dignus.com>; from Thomas David Rivers on Sep 29, 1997 13:20:03 -0400 References: <199709291720.NAA09262@lakes.dignus.com>
next in thread | previous in thread | raw e-mail | index | archive | help
As Thomas David Rivers wrote: > Anyway - at one time, that was my fix... but now it's not. > My host file has: > > > 127.0.0.1 localhost.dignus.com. localhost.dignus.com localhost > 10.0.0.1 ponds ponds.dignus.com ponds.dignus.com. > 10.0.0.3 lakes lakes.dignus.com lakes.dignus.com. Didn't you say there's another domain involved (by resolv.conf, IIRC)? David, why don't you simply start a caching-only nameserver, redirect your resolv.conf(s) to it, and look at its debug output? This will lead you *way quicker* to the solution about what names are being looked up than any of our guesswork here in the mailinglist. A caching-only nameserver is a matter of one minute: cd /etc/namedb sh make-localhost named -d 2 -b /etc/namedb/named.boot FreeBSD ships with a reasonable default named.boot for a caching-only server (which also has a bunch of comments for what to do to add a secondary). -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19970929222507.QI17620>