[194128] in North American Network Operators' Group
Re: [NOC] ARIN contact needed: something bad happens with legacy IPv4
daemon@ATHENA.MIT.EDU (=?utf-8?Q?Bj=C3=B8rn_Mork?=)
Fri Mar 17 12:42:33 2017
X-Original-To: nanog@nanog.org
From: =?utf-8?Q?Bj=C3=B8rn_Mork?= <bjorn@mork.no>
To: William Herrin <bill@herrin.us>
Date: Fri, 17 Mar 2017 17:42:11 +0100
In-Reply-To: <CAP-guGV4ZYipZPqknX0b3OsnDpe_DURCEWAVoosbtaT3E0JMvw@mail.gmail.com>
(William Herrin's message of "Fri, 17 Mar 2017 12:26:03 -0400")
Cc: noc@computing.kiae.ru, "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
William Herrin <bill@herrin.us> writes:
> On Fri, Mar 17, 2017 at 7:52 AM, Romeo Zwart <rz+nng@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 go=
od
> data. That's awfully brittle for such a critical service.
Well, it was a nice smoke test of the "RDNS required" anti-feature. All
of a sudden we couldn't even send email to ourselves, having smarthosts
in one of the affected zones. Nice.
Maybe time to re-evaluate the usefulness of that config...
Bj=C3=B8rn
