[dns-operations] dns loop

[Bernhard Schmidt]

On Tue, Jun 06, 2006 at 03:21:09PM -0700, Edward Lewis wrote:

> >but this is a protocol/implementation topic not an ops topic?
> Being that this is 6/6/6, I'll turn this into a slightly operational topic.
>  From a v6/v4 enabled network (the NANOG network), I tried to ping the 
> four servers for 225.in-addr.arpa (looking for 
> 225.225.225.225.in-addr.arpa. IN PTR).
> 
> ns.isi.edu.     NXDOMAIN
> nic.near.net.   Referral to root
> flag.ep.net.    no answer
> strul.stupi.se. no answer

As an additional note, the in-zone NS records only show 

;; ANSWER SECTION:
225.in-addr.arpa.       86400   IN      NS      dot.ep.net.
225.in-addr.arpa.       86400   IN      NS      flag.ep.net.

dot.ep.net	IPv4	190ms
dot.ep.net	IPv6	370ms
flag.ep.net	IPv4	200ms
flag.ep.net	IPv6	unreachable

flag.ep.net still has a 6bone address. It has been common knowledge at
least since RFC3701 that 6bone addresses are invalidated starting
6/6/06. dot.ep.net has a RIR and a 6bone address, which is still bad.

So we have a) a tremendous inconsistency between delegation and in-zone
data (the in-zone data seems to be "more" correct) and b) obviously
broken AAAA records on both nameservers for a /8 reverse.

Regards,
Bernhard