Re: 44/8 RDNS is still broken!

[Bryan Fields <Bryan () bryanfields net>]

On 7/22/19 10:09 PM, Owen DeLong wrote:
> That would be ARDC, not ADCR, but here’s the problem… As far as most of us
> are concerned, it was inappropriate for ARIN to hand them control of the
> block in the first place. We were fine with them doing the record keeping
> and providing POC services, but we never expected them to be so bold as to
> simply steal community resources to enrich an organization we never vetted,
> no matter how well intended.
Well here is the rub.  ARDC is not technically competent to manage the blocks
in the first place.  One can see how they bungled the RDNS for 44.0.0.0/9 and
44.128.0.0/10 after the sale causing a world wide 22+ hour outage.  Several
/16 allocations are still down, over 5 days later due to lame delegation.

> $ dig +trace -x 44.25.12.1
> ; <<>> DiG 9.8.3-P1 <<>> +trace -x 44.25.12.1
> ;; global options: +cmd
> .                     3600000 IN      NS      J.ROOT-SERVERS.NET.
> .                     3600000 IN      NS      E.ROOT-SERVERS.NET.
> .                     3600000 IN      NS      G.ROOT-SERVERS.NET.
> .                     3600000 IN      NS      F.ROOT-SERVERS.NET.
> .                     3600000 IN      NS      A.ROOT-SERVERS.NET.
> .                     3600000 IN      NS      K.ROOT-SERVERS.NET.
> .                     3600000 IN      NS      B.ROOT-SERVERS.NET.
> .                     3600000 IN      NS      D.ROOT-SERVERS.NET.
> .                     3600000 IN      NS      M.ROOT-SERVERS.NET.
> .                     3600000 IN      NS      L.ROOT-SERVERS.NET.
> .                     3600000 IN      NS      C.ROOT-SERVERS.NET.
> .                     3600000 IN      NS      I.ROOT-SERVERS.NET.
> .                     3600000 IN      NS      H.ROOT-SERVERS.NET.
> ;; Received 492 bytes from 192.168.8.200#53(192.168.8.200) in 1454 ms
>
> in-addr.arpa.         172800  IN      NS      a.in-addr-servers.arpa.
> in-addr.arpa.         172800  IN      NS      b.in-addr-servers.arpa.
> in-addr.arpa.         172800  IN      NS      c.in-addr-servers.arpa.
> in-addr.arpa.         172800  IN      NS      d.in-addr-servers.arpa.
> in-addr.arpa.         172800  IN      NS      e.in-addr-servers.arpa.
> in-addr.arpa.         172800  IN      NS      f.in-addr-servers.arpa.
> ;; Received 417 bytes from 2001:7fd::1#53(2001:7fd::1) in 1837 ms
>
> 44.in-addr.arpa.      86400   IN      NS      x.arin.net.
> 44.in-addr.arpa.      86400   IN      NS      z.arin.net.
> 44.in-addr.arpa.      86400   IN      NS      r.arin.net.
> ;; Received 112 bytes from 2001:dd8:6::101#53(2001:dd8:6::101) in 839 ms
>
> 25.44.in-addr.arpa.   86400   IN      NS      ampr.org.
> 25.44.in-addr.arpa.   86400   IN      NS      a.coreservers.uk.
> 25.44.in-addr.arpa.   86400   IN      NS      munnari.oz.au.
> 25.44.in-addr.arpa.   86400   IN      NS      ampr-dns.in-berlin.de.
> 25.44.in-addr.arpa.   86400   IN      NS      ns2.threshinc.com.
> ;; Received 186 bytes from 2001:500:13::63#53(2001:500:13::63) in 5508 ms
>
> 25.44.in-addr.arpa.   3600    IN      NS      c.ns.hamwan.net.
> 25.44.in-addr.arpa.   3600    IN      NS      b.ns.hamwan.net.
> 25.44.in-addr.arpa.   3600    IN      NS      a.ns.hamwan.net.
> ;; BAD (HORIZONTAL) REFERRAL
> ;; Received 102 bytes from 2a00:ed40:4001:1::10#53(2a00:ed40:4001:1::10) in 579 ms
>
> 1.12.25.44.in-addr.arpa. 3600 IN      PTR     loopback0.r1.triangle.hamwan.net.
> ;; Received 87 bytes from 44.24.245.2#53(44.24.245.2) in 99 ms

Someone, anyone, want to get this fixed?

The road to hell is paved in good intentions.
Hey mama, look at me, I'm on my way to the promised land, whoo!
-- 
Bryan Fields

727-409-1194 - Voice
http://bryanfields.net