On 02/13/10 18:42, kalpesh varyani wrote:
Hi Rick,
I am aware that it is a somewhat odd (but not incorrect, am I right ?)
to put a non-recursive name server in the resolv.conf
There are certain very specific circumstances where you might want to do
this, but in general I can't see any reason
Hi Rick,
I am aware that it is a somewhat odd (but not incorrect, am I right ?) to
put a non-recursive name server in the resolv.conf but I am not able to
understand the behavioral difference of ping/dig and nslookup.
But logically shouldn't it be moving to the next name server when the first
one
On Sat, Feb 13, 2010 at 12:07 PM, kalpesh varyani
wrote:
> From a third linux system, I try name resolution using dig or nslookup.
> In this system, I have resolv.conf as:
>
> nameserver A
> nameserver B
Just out of curiosity, why do you have a non recursing name server in
resolv.conf?
--
aRDy
Hi all,
I have named 9.4.3-P3 running on 2 linux systems(A & B).
A has recursion disabled and the B has recursion enabled.
>From a third linux system, I try name resolution using dig or nslookup.
In this system, I have resolv.conf as:
nameserver A
nameserver B
When I try to resolve names, using
4 matches
Mail list logo
