Re: Unexpected issues with "nslookup" command

2010-04-18 Thread Barry Margolin
In article , James Roberts-Thomson wrote: > However, I'm not sure why it was working when only one nameserver was > specified if the server wouldn't allow recursion in the first place. The > nameservers are supposed to be authoritative for the domains in question in > the first place, so I'm

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-16 Thread Mark Andrews
In message , "Lightner , Jeff" writes: > 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? >

RE: Unexpected issues with "nslookup" command

2010-04-16 Thread Lightner, Jeff
bind-users@lists.isc.org Subject: RE: Unexpected issues with "nslookup" command 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 a

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 Mark Andrews
In message <9b2fff1719120e4c83de53c2f70cc60755d5899...@secmclust01a.corp.ssi.go vt.nz>, James Roberts-Thomson writes: > Hi Mark, > > Thanks for your response; whilst I accept what your saying, I'm not convinced > it applies in this case. > > As far as I can tell, recursion is enabled on the serv

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

Re: Unexpected issues with "nslookup" command

2010-04-15 Thread Mark Andrews
In message <9b2fff1719120e4c83de53c2f70cc60755d5899...@secmclust01a.corp.ssi.go vt.nz>, James Roberts-Thomson writes: > > Can anyone explain what may be happening here, please? Stub resolvers really should be talking to nameservers that offer recursion. If it is talking to a nameserver that does