Re: Unknown RR in .in domain

2012-02-06 Thread Mark Andrews
In message <001301cce503$0716a950$1543fbf0$@nic.in>, Gaurav kansal writes: > Thanks Alan. > I got it. > > But why I am getting two NSEC3 records for .in domain?? Shouldn't I > get one NSEC3 RR only Because that is what is required. We are sending the proof thay that a DS record does

RE: Unknown RR in .in domain

2012-02-06 Thread Chris Thompson
On Feb 6 2012, Gaurav kansal wrote: Thanks Alan. I got it. But why I am getting two NSEC3 records for .in domain?? Shouldn't I get one NSEC3 RR only Because the "in" servers are denying the existence of a signed delegation for "nknsec.in", while (because the zone uses opt-out) al

RE: Unknown RR in .in domain

2012-02-06 Thread Gaurav kansal
AM To: bind-users@lists.isc.org Subject: Re: Unknown RR in .in domain On 2/6/2012 1:35 PM, Gaurav kansal wrote: > Can anyone please tell me why TYPE50 RR is showing in response coming > from .in domain Because your version of DIG does not understand NSEC3 records. http://tools.ie

Re: Unknown RR in .in domain

2012-02-06 Thread Alan Clegg
On 2/6/2012 1:35 PM, Gaurav kansal wrote: > Can anyone please tell me why TYPE50 RR is showing in response > coming from .in domain Because your version of DIG does not understand NSEC3 records. http://tools.ietf.org/html/rfc5155 AlanC -- a...@clegg.com | 1.919.355.8851 signature.as