On 3/17/17, 12:26 PM, "NANOG on behalf of William Herrin"
<nanog-boun...@nanog.org on behalf of b...@herrin.us> wrote:
On Fri, Mar 17, 2017 at 7:52 AM, Romeo Zwart <rz+...@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.
Regards,
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.
Thanks,
Mark
ARIN CTO
