Re: [dns-wg] [dns-operations] Additional information about the RIPE NCC reverse DNS issue

2017-03-19 Thread Gert Doering
Hi, On Sun, Mar 19, 2017 at 12:36:33PM -0700, Doug Barton wrote: > RIPE folks, the operational answer to this problem would seem to be > having ARIN implement a sanity check such that if more than N% of the > information is changed in a given pass that humans need to get involved > to approve t

Re: [dns-wg] [dns-operations] Additional information about the RIPE NCC reverse DNS issue

2017-03-19 Thread Doug Barton
On 03/19/2017 08:09 AM, Shane Kerr wrote: Doug, At 2017-03-18 18:34:25 -0700 Doug Barton wrote: On 03/18/2017 08:46 AM, Anand Buddhdev wrote: Dear colleagues, This is a follow-up to our message of Friday about issues with some reverse delegations. After doing a thorough analysis, and wit

Re: [dns-wg] [dns-operations] Additional information about the RIPE NCC reverse DNS issue

2017-03-19 Thread Shane Kerr
Doug, At 2017-03-18 18:34:25 -0700 Doug Barton wrote: > On 03/18/2017 08:46 AM, Anand Buddhdev wrote: > > Dear colleagues, > > > > This is a follow-up to our message of Friday about issues with some > > reverse delegations. > > > > After doing a thorough analysis, and with the help of ARIN staff

Re: [dns-wg] f.root-servers.net unreachable for a few days?

2017-03-19 Thread Max Grobecker
Hi Ray, thank you - now it's reachable again via a short path :-) -- traceroute to f.root-servers.net (192.5.5.241), 30 hops max, 60 byte packets 1 87.186.224.133 (87.186.224.133) [AS3320] 18.373 ms 2 87.190.177.174 (87.190.177.174) [AS3320] 19.008 ms 3 217.239.43.