Date: Fri, 28 Jun 1996 22:40:04 -0600 (MDT) From: Nate Williams <nate@mt.sri.com> To: hackers@freebsd.org Subject: BIND/named experts? Message-ID: <199606290440.WAA01748@rocky.mt.sri.com>
next in thread | raw e-mail | index | archive | help
My new class --C is now in place, and things appear to be working pretty good. Things are being propogated correctly, and my MX sites have now got all of the necessary information so mail will end up getting to me sooner or later. However, 'named' doesn't work very well on my router box. It seems to want to append '.sri.com' to *EVERY* query I make unless I end them with a dot, which makes named on my router useless (except everyone getting the information from my box seems to be doing OK with it.) Does anyone have any idea how I can track this down? Here is one example of what appears to be happening from the logfile. datagram from [206.127.76.100].34204, fd 5, len 43; now Fri Jun 28 22:34:48 1996 req: nlookup(blacksmith.com.mt.sri.com) id 35841 type=1 class=1 req: found 'blacksmith.com.mt.sri.com' as 'mt.sri.com' (cname=0) ns_req: answer -> [206.127.76.100].34204 fd=5 id=396 size=97 Local datagram from [206.127.76.100].34204, fd 5, len 40; now Fri Jun 28 22:34:48 1996 req: nlookup(blacksmith.com.sri.com) id 36097 type=1 class=1 req: found 'blacksmith.com.sri.com' as 'com.sri.com' (cname=0) forw: forw -> [192.12.33.94].53 ds=8 nsid=2755 id=397 322ms retry 4sec datagram from [192.12.33.94].53, fd 7, len 92; now Fri Jun 28 22:34:48 1996 ncache: dname blacksmith.com.sri.com, type 1, class 1 send_msg -> [206.127.76.100].34204 (UDP 5) id=397 datagram from [206.127.76.100].34204, fd 5, len 32; now Fri Jun 28 22:34:48 1996 req: nlookup(blacksmith.com) id 36353 type=1 class=1 req: found 'blacksmith.com' as 'blacksmith.com' (cname=0) ns_req: answer -> [206.127.76.100].34204 fd=5 id=398 size=132 Local For most other hosts this will eventually work, but the problem lies when the nameserver makes queries that it must respond to, which causes it to recursively call itself. The *weirdest* thing is that it works fine for awhile, and then it'll start locking up which means that *nothing* works. I just rebooted it and things seem to be working fine, but I suspect it'll be locked up in the morning. Thanks for any advice you can give, Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199606290440.WAA01748>