RE: Differences Between Recursion Desired and Recursion Available

For this reason, "stub" resolvers typically set RD=1, and only "full-service resolvers", such as the one integrated into named (although there are standalone ones, like Knot, Unbound, [1]), generate RD=0 queries. Full-service resolvers are capable of taking the referrals, and using them to

Re: Differences Between Recursion Desired and Recursion Available

In article , Harshith Mulky wrote: > What I am not able to understand is, What would happen when resolver does not > set Recursion Desired bit in the query it sends? If RD is not set, the server should simply not

Re: Differences Between Recursion Desired and Recursion Available

On Fri, Oct 06, 2017 at 08:11:56AM +, Harshith Mulky wrote: > What I am not able to understand is, What would happen when resolver > does not set Recursion Desired bit in the query it sends? > > If Recursion is supported on the server, Would the server do the > Referral Queries and set the RA

Differences Between Recursion Desired and Recursion Available

Hello Experts, I read this from RFC1035 about RD and RA Bits RD Recursion Desired - this bit may be set in a query and is copied into the response if recursion supported by this Name Server. If Recursion is rejected by this Name Server, for example it has been configured as Authoritative