[NOC] ARIN contact needed: something bad happens with legacy IPv4 block's reverse delegations

Mark Kosters markk at arin.net
Fri Mar 17 17:42:58 UTC 2017

On 3/17/17, 12:26 PM, "NANOG on behalf of William Herrin" <nanog-bounces at nanog.org on behalf of bill at herrin.us> wrote:

    On Fri, Mar 17, 2017 at 7:52 AM, Romeo Zwart <rz+nng at zwart.com> wrote:
    > RIPE NCC have issued a statement about the issue here:
    >  https://www.ripe.net/ripe/mail/archives/dns-wg/2017-March/003394.html
    > Our apologies for the inconvenience caused.
    Hmm. That sounds like an ARIN-side bug too. ARIN's code responded to
    corrupted data by zeroing out the data instead of using the last known good
    data. That's awfully brittle for such a critical service.
    Bill Herrin
Hi Bill,

The analysis was not yet complete when the notice went out from RIPE. After doing a post-mortum, there were no bugs in ARIN’s software in regards to this issue. We followed exactly what RIPE told us to do. When we noticed an issue with RIPE’s updates yesterday, we notified them as well.

Two zones managed by APNIC that received delegations from RIPE were also affected by RIPE’s bug – it was more than just a RIPE/ARIN thing.

The three impacted RIR’s have been working closely together to get RIPE’s DNS entries correctly added into our respective authoritative DNS systems.


More information about the NANOG mailing list