Re: ARIN contact needed: something bad happens with legacy IPv4 block's reverse delegations
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?
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?
participants (1)
-
Alberto Delgado