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-18 Thread Barry Margolin
In article mailman.1200.1271623889.21153.bind-us...@lists.isc.org, James Roberts-Thomson james.robertsthomson...@msd.govt.nz 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

RE: Unexpected issues with nslookup command

2010-04-16 Thread Lightner, Jeff
-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 an assumption about subnetting

Re: Unexpected issues with nslookup command

2010-04-16 Thread Mark Andrews
In message ff38bba1bf42ab46a7f46524614fab62024c1...@exvs02.dsw.net, 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

Unexpected issues with nslookup command

2010-04-15 Thread James Roberts-Thomson
Hello, I have tried to research my problem, but haven't found an answer from the collected Google wisdom of the ages, unfortunately. We have a situation where we are getting strange results from the nslookup command (with knock-on effects to name resolution in general). We have two primary

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 doesn't

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 servers.

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 say