[dns-wg] ns.ripe.net missing NS records

> -----Original Message-----
> From: Christian Storch [mailto:storch at infra.net] 
> Sent: Friday, November 03, 2006 3:46 PM
> To: Brett Carr
> Cc: dns-wg at ripe.net
> Subject: Re: [dns-wg] ns.ripe.net missing NS records
> 
> Brett Carr wrote:
> >> -----Original Message-----
> >> From: dns-wg-admin at ripe.net [mailto:dns-wg-admin at ripe.net] 
> On Behalf 
> >> Of Christian Storch
> >> Sent: Friday, November 03, 2006 2:56 PM
> >> To: dns-wg at ripe.net
> >> Subject: [dns-wg] ns.ripe.net missing NS records
> >>
> >> Hi,
> >>
> >> is there any reason for ns.ripe.net missing NS records of 
> /24 reverse 
> >> zones out of /16 reverse zones?
> >> Anyway we've a problem resolving ip addresses out of a 
> couple of /16 
> >> reverse zones when asking ns.ripe.net as one of the 
> secondaries for 
> >> such a zone.
> >>
> >> Any thoughts or hints?
> >>     
> >
> > Christian,
> >
> > ns.ripe.net is generally a secondary and hence it carries the 
> > information provided by the relevant primary, however if 
> you fo feel 
> > there Is a problem with the information that ns.ripe.net is serving 
> > then please let me know the specifics and I'd be happy to 
> look into it for you.
> >
> > Brett
> >   
> Brett,
> 
> here are some examples:
> 
> 193.197.192.11
> 195.30.231.17
> 212.227.85.10
> 
> Every /16 has ns.ripe.net as one secondary.
> But only the servers of the corresponding LIR will give you 
> the NS records of the /24.
> E.g. try
> 
>     dig ns 192.197.193.in-addr.arpa @dns1.belwue.de
> 
> and than
> 
>     dig ns 192.197.193.in-addr.arpa @ns.ripe.net
> 
> So its like playing roulette for our resolver.
> 

Christian,
      as far as I can tell (without having access to the relevant servers)
this is possibly a misconfiguration on the primary.

I've taken a look in the zonefile we have for 197.193.in-addr.arpa and there
is no delegation for 192.197.193.in-addr.arpa within that file so
ns.ripe.net does not know where to send you. My guess is that the LIR have
the child zone configured on their server and that is why they are answering
differently.

Brett..

--
Brett Carr                              Ripe Network Coordination Centre
Manager -- DNS Services Group           Singel 258 Amsterdam NL
GPG Key fingerprint = F20D B2A7 C91D E370 44CF  F244 B6A1 EF48 E743 F7D8