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

[Shane Kerr]

All,

On 2015-07-15 15:13:42+0200 (Wednesday)
Stephane Bortzmeyer <bortzmeyer at nic.fr> wrote:

> On Wed, Jul 15, 2015 at 07:58:42AM +0000,
>  Shane Kerr <shane at biigroup.cn> wrote 
>  a message of 46 lines which said:
> 
> > Currently dahu1.yeti.eu.org, ns2.ipv6.ernet.in, and
> > ns-yeti.bondis.org answer ARPA, other servers do not.
> 
> dahu1.yeti.eu.org is *not* configured to be authoritative for
> .arpa. Whatever it does, it is without my consent or even knowledge.
> 
> > 3. Fix the existing servers to match this.
> 
> How?
> 
> dahu1:~ % sudo grep -i arpa /etc/nsd/*
> dahu1:~ %

Okay, it looks like when we generate the root zone we are also claiming
ownership of the ARPA space:

https://github.com/BII-Lab/Yeti-Project/blob/master/script/BII/dm-setup/gen_root_functions.sh#L16

I'd like to propose that we remove the parts that munge the ARPA stuff
from our various DM, since they seem broken now and I don't think this
is part of the Yeti experiment.

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

Cheers,

--
Shane