From owner-freebsd-hackers Thu Oct 2 13:41:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA21487 for hackers-outgoing; Thu, 2 Oct 1997 13:41:25 -0700 (PDT) Received: from elvis.vnet.net (elvis.vnet.net [166.82.1.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA21480 for ; Thu, 2 Oct 1997 13:41:16 -0700 (PDT) Received: from ponds.dignus.com (ponds.vnet.net [166.82.177.48]) by elvis.vnet.net (8.8.5/8.8.4) with ESMTP id QAA10402; Thu, 2 Oct 1997 16:41:08 -0400 (EDT) Received: from lakes.dignus.com (lakes [10.0.0.3]) by ponds.dignus.com (8.8.5/8.8.5) with ESMTP id QAA00483; Thu, 2 Oct 1997 16:43:00 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.8.5/8.6.9) id QAA14834; Thu, 2 Oct 1997 16:34:20 -0400 (EDT) Date: Thu, 2 Oct 1997 16:34:20 -0400 (EDT) From: Thomas David Rivers Message-Id: <199710022034.QAA14834@lakes.dignus.com> To: freebsd-hackers@freefall.FreeBSD.org, joerg_wunsch@uriah.heep.sax.de, rivers@dignus.com Subject: Re: r-cmds and DNS and /etc/host.conf Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk J"org wrote: > > 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). Ok - Here's what I have in /etc/resolv.conf: domain vnet.net nameserver 127.0.0.1 And, to ensure things are consistent; I rebooted... Then, after the reboot, I did my rlogin - it worked immediately (notice; no nameserver is running on the machine where rlogind is running...) Then, I started named as suggested above; with the command: named -d 2 -b /etc/namedb/named.boot (I had already run the make-localhost script.) Now, my rlogins hang again... Unfortunately, named doesn't report *anything* at all.. Not a single byte... So, I added "options query-log" to the end of named-boot and redid all of this... named still doesn't report anything. Then, I added -q on the named command line (which shouldn't be needed, since options query-log is in named.boot). named still doesn't report anything. So, I changed the debug level from 2 to 10. named still doesn't report anything. As soon as I kill my local named; my rlogin succeeds... (This is the 2.2.1-RELEASE named; perhaps it's been compiled without the flags to report queries???) I also went through the entire exercise with "domain dignus.com" in /etc/resolv.conf - no change. Anyway - here's some of the text from /var/log/messages... it indicates that named was started (several times) and also that something is trying to go out the gateway interface to my ISP (which is down) via natd. My default route is to the external world... Oct 2 15:52:09 ponds named[497]: starting. named 4.9.4-P1 Tue Mar 25 12:43:20 GMT 1997 jkh@time.cdrom.com:/usr/obj/usr/src/usr.sbin/named Oct 2 15:52:09 ponds named[497]: Ready to answer queries. Oct 2 15:52:09 ponds natd: Failed to write packet back. (Network is down) Oct 2 15:52:17 ponds last message repeated 5 times Oct 2 15:52:18 ponds named[497]: dumping nameserver data Oct 2 15:52:18 ponds named[497]: finished dumping nameserver data Oct 2 15:52:19 ponds natd: Failed to write packet back. (Network is down) Oct 2 15:52:26 ponds last message repeated 6 times Any idea why my named isn't producing any debug info? - Dave Rivers -