Date: Sun, 20 Oct 1996 19:55:44 -0700 (PDT) From: Tom Samplonius <tom@sdf.com> To: Keith Mitchell <kmitch@unix.guru.org> Cc: hackers@freebsd.org Subject: Re: nslookup on Ultrix and Bind 4.9.4 Message-ID: <Pine.NEB.3.94.961020195421.12128D-100000@misery.sdf.com> In-Reply-To: <199610202113.RAA10451@unix.guru.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 20 Oct 1996, Keith Mitchell wrote: > I am runnign current on my FreeBSD system (10/18). I am using the machine > as a primary name server for the local network. Ever since bind was updated > to 4.9.4?? one of the other computers on the network could not use it as > a nameserver. The other computer is a DECstation 5k running Ultrix 4.4. > > nslookup comes back with messages like: > > *** Can't find server name for address 10.10.10.12: Query refused > *** Default servers are not available > > > And in the named debug file, I get: > > datagram from [198.82.200.88].1539, fd 5, len 27; now Sun Oct 20 17:10:33 1996 > ns_req: answer -> [198.82.200.88].1539 fd=5 id=1 size=27 Local > > > The funny thing is DNS lookups (gethostbyname, gethostbyaddr) seem to work > fine. nsquery seems to work as well. If I set the name server to be > one of the FreeBSD stable machines everything works fine (old bind). > > Any idea why the new bind would cause the resolver to fail on an old Ultrix > machine?? > > It could be using INVQ to find the server name. This was something that old nslookup's do. INVQ is depreciated. Try the nslookup from 4.9.4P1 on Ultrix. Get the full BIND 4.9.4P1 kit from ftp.vix.com:/pub/bind Tom
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.94.961020195421.12128D-100000>