BIND database dump question...

[Mark.Andrews at nominum.com]

> 
> Greetings.
> 
> Would the BIND experts hereabouts please interpret this entry from a
> named database dump (i.e., kill -2 <named PID>):
> 
> $ORIGIN 88.24.in-addr.arpa.
> 255  518316  IN   NS   DNS1.RR.COM. ;Cr=addtnl LAME=516 [192.36.148.17]
>      518316  IN   NS   DNS2.RR.COM. ;Cr=addtnl LAME=516 [192.36.148.17]

	192.36.148.17 told this nameserver that the nameservers for
	255.88.24.in-addr.arpa are DNS1.RR.COM and DNS2.RR.COM.  Both
	nameservers have been queried and found to be lame.  The lame
	ttl has another 516 seconds to go before it expires and the
	server will re-test DNS1.RR.COM and DNS2.RR.COM.

	The underlying problem is that there is a bad delegation.
	The parents zone has DNS1.RR.COM and DNS2.RR.COM which
	say the nameservers are ns3.southeast.rr.com and
	ns4.southeast.rr.com which intern say the nameservers are
	ns1.nc.rr.com and ns2.nc.rr.com.

255.88.24.in-addr.arpa.  6D IN NS  DNS1.RR.COM.
255.88.24.in-addr.arpa.  6D IN NS  DNS2.RR.COM.

	vs

255.88.24.in-addr.arpa.  1D IN NS  ns3.southeast.rr.com.
255.88.24.in-addr.arpa.  1D IN NS  ns4.southeast.rr.com.

	vs

255.88.24.in-addr.arpa.  1H IN NS  ns1.nc.rr.com.
255.88.24.in-addr.arpa.  1H IN NS  ns2.nc.rr.com.


> 
> Supporting documentation:
> ------------------------------------------------------------
> BIND 8.2.3
> ------------------------------------------------------------
> dump is from another nameserver in rr.com
> ------------------------------------------------------------
> ARIN lists dns[12].rr.com as authoritative for 24.88.255
> ------------------------------------------------------------
> dns[12].rr.com delegate authority for reverses to other
> nameservers in the rr.com hierarchy, and those nameservers
> are aware of this and act accordingly (i.e., this is not a
> lame delegation, as I understand lame delegations).

	You can't do this.  This is NOT how the DNS is designed,
	Delegations only go down not sideways.

> ------------------------------------------------------------
> 
> We've received reports of problems with reverse lookups in
> 24.88.255.X, and we've been able to duplicate them, but I can't
> figure out how to address the problem of root nameservers
> (192.36.148.17 is i.root-servers.net, and we saw the same thing
> with e.root-servers.net last night) having LAME information, if
> that is in fact what I'm seeing.
> 
> Can someone help explain the database dump?  I've looked at the
> relevant section in DNS and BIND (3rd edition) but it doesn't
> mention LAME records in the database dump section.  I understand
> that lame servers are those which are not authoritative for those
> domains to which authority has been delegated, but that doesn't
> seem to be the case here.  Is there something wrong at the root
> level?  Who would I speak with about that?

	You speak to ARIN to get the delegation corrected.

> 
> Thanks for any help/clues that you can provide.
> 
> -- 
> Todd Herr                                                   therr at va.rr.com
> The original text in the above message represents the opinions and thoughts
> of the author and does not necessarily represent the views of his employer.
> 
> 
> 
--
Mark Andrews, Nominum Inc.
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews at nominum.com