RE: Unexpected issues with "nslookup" command

2010-04-18 Thread James Roberts-Thomson
Hi Jeff, >Did I misread your original problem? I thought you said it worked if >you had only one of the nameservers in resolv.conf. You didn't state >but I assume (that word again) that you meant if either of your >nameservers was there by itself it worked? No, you did not misread the problem;

RE: Unexpected issues with "nslookup" command

2010-04-15 Thread James Roberts-Thomson
Hi Mark, >allow-recursion defaults to "{ localnets; localhost; };". >If the client was not on a directly connected network it >will NOT get recursion by default. So it would seem; I had made an assumption about subnetting that apparently was not entirely accurate. Oh well, you know what they sa

RE: Unexpected issues with "nslookup" command

2010-04-15 Thread James Roberts-Thomson
15:34:37.026 client x.x.x.x#35622: recursion available" Thanks, James Roberts-Thomson -Original Message- From: ma...@isc.org [mailto:ma...@isc.org] Sent: Friday, 16 April 2010 2:57 p.m. To: James Roberts-Thomson Cc: bind-users@lists.isc.org Subject: Re: Unexpected iss

Unexpected issues with "nslookup" command

2010-04-15 Thread James Roberts-Thomson
ameserver died, and all name resolution ground to a halt). This happens on any of the clients running ISC Bind nslookup (I've even recompiled the latest v9.7.0 binary, too). Can anyone explain what may be happening here, please? Thanks! James Roberts-Thomson (My apologies for the follo