[194114] in North American Network Operators' Group
Re: ARIN contact needed: something bad happens with legacy IPv4
daemon@ATHENA.MIT.EDU (Alberto Delgado)
Fri Mar 17 10:23:58 2017
X-Original-To: nanog@nanog.org
Date: Fri, 17 Mar 2017 12:26:39 +0100
From: Alberto Delgado <albertod@cyberneticos.com>
To: nanog@nanog.org
In-Reply-To: <c22c18b8ceebe590b97ff892178f6b25@cyberneticos.com>
Errors-To: nanog-bounces@nanog.org
I just receive an answer from RIPE and now its working again:
Dear Alberto,
Our apologies for this. There was a bug in our DNS provisioning system,
and it temporarily caused some delegations (where the parent zone is
operated by ARIN) to be removed. The bug has been fixed, and the correct
data is now being published on the RIPE NCC FTP server. We expect ARIN's
DNS provisioning system to pick it up shortly, and the delegations will
be restored.
Regards,
Anand Buddhdev
RIPE NCC
El 2017-03-17 11:49, Alberto Delgado escribió:
> Me too.
>
> We have a 164.138.208.0/22 and we have issues with dns reverse too
>
> We sent an email to ripe support, but no answer yet
>
>
> El 2017-03-17 10:53, Stephane Bortzmeyer escribió:
>> On Fri, Mar 17, 2017 at 12:03:58PM +0300,
>> Eygene Ryabinkin <rea+nanog@grid.kiae.ru> wrote
>> a message of 71 lines which said:
>>
>>> Seems like the other /16 from 144.in-addr.arpa are affected too
>>> (at least).
>>
>> Also in 164.in-addr.arpa, it seems?
