[194171] in North American Network Operators' Group
Re: [NOC] ARIN contact needed: something bad happens with legacy IPv4
daemon@ATHENA.MIT.EDU (William Herrin)
Mon Mar 20 16:57:10 2017
X-Original-To: nanog@nanog.org
X-Really-To: <nanog@nanog.org>
In-Reply-To: <20170320192752.GA14835@panix.com>
From: William Herrin <bill@herrin.us>
Date: Mon, 20 Mar 2017 16:56:39 -0400
To: Brett Frankenberger <rbf+nanog@panix.com>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
On Mon, Mar 20, 2017 at 3:27 PM, Brett Frankenberger <rbf+nanog@panix.com>
wrote:
> If ARIN delegated 32.11.10.in-addr.arpa through 47.11.10.in-addr.arpa
> to a RIPE nameserver, there's no good way for RIPE to then delegate,
> say, 10.11.34.0/24 (34.11.10.in-addr.arpa) to the nameserver of the
> entity to which RIPE has allocated 10.11.34.0. (Sure, it can be done,
> using the same techniques as are used for allocations of
> longer-than-/24, but recipients of /24 and larger reasonably expect to
> have the X.X.X.in-addr.arpa delegated to their nameservers.)
>
Hi Brett,
The last I tried it, the servers which the glue claims are authoritative
for a zone could assert that they themselves are not authoritative and
offer new glue for completely different servers asserted to be
authoritative. I had to fake a parent zone in Bind. This was before DNSSEC.
Regards,
Bill Herrin
--
William Herrin ................ herrin@dirtside.com bill@herrin.us
Dirtside Systems ......... Web: <http://www.dirtside.com/>
