[Yeti DNS Discuss] Authoritative for ARPA? (was: Strange BIND resolver behaviour (may be not Yeti-specific))

[Stephane Bortzmeyer]

On Thu, Jul 16, 2015 at 07:51:46PM +0000,
 Shane Kerr <shane at biigroup.cn> wrote 
 a message of 40 lines which said:

> I can make a PR for this to BII and WIDE, which execute this now I
> think, if there is consensus.

I agree. arpa should be handled like any other TLD: use the USG/ICANN
delegation:

arpa.			518400 IN NS e.root-servers.net.
arpa.			518400 IN NS b.root-servers.net.
arpa.			518400 IN NS h.root-servers.net.
arpa.			518400 IN NS g.root-servers.net.
arpa.			518400 IN NS c.root-servers.net.
arpa.			518400 IN NS d.root-servers.net.
arpa.			518400 IN NS i.root-servers.net.
arpa.			518400 IN NS a.root-servers.net.
arpa.			518400 IN NS m.root-servers.net.
arpa.			518400 IN NS k.root-servers.net.
arpa.			518400 IN NS l.root-servers.net.
arpa.			518400 IN NS f.root-servers.net.

By the way, the original mistake probably came from the fact that arpa
is the only TLD delegated to root name servers (a bad idea in the
USG/ICANN root).