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

On Mon, Mar 20, 2017 at 3:27 PM, Brett Frankenberger wrote: > If ARIN delegated 32.11.10.in-addr.arpa through 47.11.10.in-addr.arpa > to a RIPE nameserver, there's no good way for RIPE to then delegate, > say, 10.11.34.0/24 (34.11.10.in-addr.arpa) to the nameserver of the >

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

On Sat, Mar 18, 2017 at 09:27:11PM -0700, Doug Barton wrote: > > > As to why DNS-native zone operations are not utilized, the challenge > > is that reverse DNS zones for IPv4 and DNS operations are on octet > > boundaries, but IPv4 address blocks may be aligned on any bit > > boundary. > > Yes,

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

Dear John, Bill and all, On 17/03/17 19:31 , John Curran wrote: > On 17 Mar 2017, at 2:17 PM, William Herrin wrote: >> >> On Fri, Mar 17, 2017 at 2:14 PM, John Curran wrote: >> >>> See previous reply. The data was both correctly formatted and signed, >>> so

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

On 03/18/2017 10:53 PM, John Curran wrote: On 19 Mar 2017, at 12:50 AM, Doug Barton > wrote: ... Meanwhile, my offer to help y'all fix your DNS was a sincere one. Feel free to hit me up off list. Doug - You’d want to make that offer to the

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

On 19 Mar 2017, at 12:50 AM, Doug Barton > wrote: ... Meanwhile, my offer to help y'all fix your DNS was a sincere one. Feel free to hit me up off list. Doug - You’d want to make that offer to the RIPE NCC (as they experienced the issues with

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

On 03/18/2017 09:40 PM, John Curran wrote: On 19 Mar 2017, at 12:27 AM, Doug Barton wrote: ... Despite the associated risk, we are happy to install such checks if RIPE requests them, but are this time are processing them as we agreed to do so – which is whenever we

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

On 19 Mar 2017, at 12:27 AM, Doug Barton wrote: > ... >> Despite the associated risk, we are happy to install such checks if >> RIPE requests them, but are this time are processing them as we >> agreed to do so – which is whenever we receive correctly formatted >> and

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

Thanks for the response, John. Some thoughts below. On 03/18/2017 08:58 PM, John Curran wrote: On 18 Mar 2017, at 9:58 PM, Doug Barton > wrote: My eyebrows reacted to this the same way Bill's did. It sounds like this is at least a

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

On 18 Mar 2017, at 9:58 PM, Doug Barton wrote: > > My eyebrows reacted to this the same way Bill's did. It sounds like this is > at least a semi-automated system. Such things should have sanity checks on > the receiving side when told to remove large gobs of data, even if

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

On 03/17/2017 10:42 AM, Mark Kosters wrote: On 3/17/17, 12:26 PM, "NANOG on behalf of William Herrin" wrote: On Fri, Mar 17, 2017 at 7:52 AM, Romeo Zwart wrote: RIPE NCC have issued a statement about the issue here:

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

On Fri, Mar 17, 2017 at 2:31 PM, John Curran wrote: > Glad to help (and apologies for the information coming out in pieces – > we’ve opted to go with updates as we learn more rather than some for > comprehensive but less timely report.) > Also very much appreciated. Regards,

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

On 17 Mar 2017, at 2:17 PM, William Herrin wrote: > > On Fri, Mar 17, 2017 at 2:14 PM, John Curran wrote: > >> See previous reply. The data was both correctly formatted and signed, >> so the agreed integrity checks passed. >> > > Ah, okay. So it wasn't bad

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

On Fri, Mar 17, 2017 at 2:14 PM, John Curran wrote: > See previous reply. The data was both correctly formatted and signed, > so the agreed integrity checks passed. > Ah, okay. So it wasn't bad counts as originally reported but no data with counts that confirmed no data.

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

On 17 Mar 2017, at 2:08 PM, William Herrin wrote: > > On Fri, Mar 17, 2017 at 1:42 PM, Mark Kosters wrote: >> On 3/17/17, 12:26 PM, "NANOG on behalf of William Herrin" < > nanog-boun...@nanog.org on behalf of b...@herrin.us> wrote: >>>Hmm. That sounds like an

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

On 17 Mar 2017, at 12:26 PM, William Herrin > wrote: On Fri, Mar 17, 2017 at 7:52 AM, Romeo Zwart > wrote: > RIPE NCC have issued a statement about the issue here: > >

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

On 3/17/17, 12:26 PM, "NANOG on behalf of William Herrin" wrote: On Fri, Mar 17, 2017 at 7:52 AM, Romeo Zwart wrote: > RIPE NCC have issued a statement about the issue here: > >

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

On Fri, Mar 17, 2017 at 1:42 PM, Mark Kosters wrote: > On 3/17/17, 12:26 PM, "NANOG on behalf of William Herrin" < nanog-boun...@nanog.org on behalf of b...@herrin.us> wrote: >> Hmm. That sounds like an ARIN-side bug too. ARIN's code responded to >> corrupted data by

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

> On Mar 17, 2017, at 10:28 AM, valdis.kletni...@vt.edu wrote: > > On Fri, 17 Mar 2017 17:42:11 +0100, Bjørn Mork said: >> 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

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

On Fri, 17 Mar 2017 17:42:11 +0100, Bjørn Mork said: > 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. If you don't have a chaos monkey, the Internet will

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

On Fri, Mar 17, 2017 at 05:42:11PM +0100, Bjørn Mork wrote: > William Herrin writes: > > On Fri, Mar 17, 2017 at 7:52 AM, Romeo Zwart wrote: > >> RIPE NCC have issued a statement about the issue here: > >> > >>

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

William Herrin writes: > On Fri, Mar 17, 2017 at 7:52 AM, Romeo Zwart 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.

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

On Fri, Mar 17, 2017 at 7:52 AM, Romeo Zwart 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.

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

Dear all, 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. Kind regards, Romeo Zwart RIPE NCC On 17/03/17 12:31 , John Curran wrote: > Eygene - > > We are aware there’s

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

Folks - RIPE NCC has backed out the change at issue, and we are again processing zonelet files received from them. They’ve posted more details here - FYI, /John John Curran President and CEO ARIN On 17 Mar 2017, at 12:31

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

John, Alex, Romeo, Fri, Mar 17, 2017 at 12:31:06PM +0100, John Curran wrote: > We are aware there’s an issue and working on it presently with RIPE. > Expect additional updates shortly. Fri, Mar 17, 2017 at 12:50:48PM +0100, Alex Band wrote: > You can find a detailed announcement from the

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

You can find a detailed announcement from the RIPE NCC here: https://www.ripe.net/ripe/mail/archives/dns-wg/2017-March/003394.html -Alex Band > On 17 Mar 2017, at 12:31, John Curran wrote: > > Eygene -

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

Eygene - We are aware there’s an issue and working on it presently with RIPE. Expect additional updates shortly. /John John Curran President and CEO ARIN > On 17 Mar 2017, at 11:04 AM, Eygene Ryabinkin wrote: > > Job, good day. > > Fri, Mar 17, 2017 at

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

Job, good day. Fri, Mar 17, 2017 at 09:55:56AM +, Job Snijders wrote: > 171 also seems affected. Not the whole one, it seems: {{{ $ dig +trace -t soa 1.171.in-addr.arpa ; <<>> DiG 9.10.4-P6 <<>> +trace -t soa 1.171.in-addr.arpa ;; global options: +cmd . 202634 IN