nanog mailing list archives

ARIN contact needed: something bad happens with legacy IPv4 block's reverse delegations


From: Eygene Ryabinkin <rea+nanog () grid kiae ru>
Date: Fri, 17 Mar 2017 12:03:58 +0300

We (at Kurchatov Insitute) still use 144.206.0.0/16, the legacy
block, and seeing the breakage rooted at ARIN since this night,
{{{
$ dig +trace -t soa 206.144.in-addr.arpa

; <<>> DiG 9.10.4-P6 <<>> +trace -t soa 206.144.in-addr.arpa
;; global options: +cmd
.                       206351  IN      NS      a.root-servers.net.
.                       206351  IN      NS      c.root-servers.net.
.                       206351  IN      NS      d.root-servers.net.
.                       206351  IN      NS      e.root-servers.net.
.                       206351  IN      NS      l.root-servers.net.
.                       206351  IN      NS      f.root-servers.net.
.                       206351  IN      NS      g.root-servers.net.
.                       206351  IN      NS      h.root-servers.net.
.                       206351  IN      NS      j.root-servers.net.
.                       206351  IN      NS      m.root-servers.net.
.                       206351  IN      NS      k.root-servers.net.
.                       206351  IN      NS      i.root-servers.net.
.                       206351  IN      NS      b.root-servers.net.
.                       514733  IN      RRSIG   NS 8 0 518400 20170329170000 20170316160000 61045 . 
OjsjoA6WCcThV3BqhAyMaXI3bU1m228Gl8nvaR074qBtem/RjaFJh1Oe r7LPI6W15jgbRGuCY7/GUNgDex4ZM43yvx2iY+2GpSk9b2/pKGbDaDIp 
X1Hd8418206eow1P/SgPqtT+2LzjM+lz/HKUvCyPoN4uX5/7GDExn8ir 2Q/vw81Za2nJ4Ji6oeGAmE8g6V3RJfTI0El/CP9Vl2/r0jWDZZ+wtYRA 
uwqvQYj+7VZc5+UJDJ3/Gne1LBnzXKnZRwnfJtZenhfZ7X20D9PiXvfJ M2s1ryqZvg8K5RqYt/r8pIiq1Udd1KWQBgdN7Q629+jNSngZQtH19R9H 
fM7h1w==
;; Received 1097 bytes from 127.0.0.1#53(127.0.0.1) in 0 ms

in-addr.arpa.           172800  IN      NS      e.in-addr-servers.arpa.
in-addr.arpa.           172800  IN      NS      f.in-addr-servers.arpa.
in-addr.arpa.           172800  IN      NS      d.in-addr-servers.arpa.
in-addr.arpa.           172800  IN      NS      c.in-addr-servers.arpa.
in-addr.arpa.           172800  IN      NS      b.in-addr-servers.arpa.
in-addr.arpa.           172800  IN      NS      a.in-addr-servers.arpa.
in-addr.arpa.           86400   IN      DS      53696 8 2 13E5501C56B20394DA921B51412D48B7089C5EB6957A7C58553C4D4D 
424F04DF
in-addr.arpa.           86400   IN      DS      63982 8 2 AAF4FB5D213EF25AE44679032EBE3514C487D7ABD99D7F5FEC3383D0 
30733C73
in-addr.arpa.           86400   IN      DS      47054 8 2 5CAFCCEC201D1933B4C9F6A9C8F51E51F3B39979058AC21B8DF1B1F2 
81CBC6F2
in-addr.arpa.           86400   IN      RRSIG   DS 8 2 86400 20170330000000 20170316230000 33786 arpa. 
gqNN6MmLVxFtSG0oxdyoYVSXZlp6vY9yxpnJW89TYCHfTkv+ZmklM76O IHdTznEhLHXbyr4BaxjFCshsC3WacdH/YZYa/SZynJ9Q1N6/bogrIUTn 
qs61Y/YD4Sk5lI7YvUxVnPrF3lk1pY8dpoTkprTLZngoeQEsm552inqG ypU=
;; Received 733 bytes from 198.41.0.4#53(a.root-servers.net) in 64 ms

144.in-addr.arpa.       86400   IN      NS      r.arin.net.
144.in-addr.arpa.       86400   IN      NS      u.arin.net.
144.in-addr.arpa.       86400   IN      NS      x.arin.net.
144.in-addr.arpa.       86400   IN      NS      y.arin.net.
144.in-addr.arpa.       86400   IN      NS      z.arin.net.
144.in-addr.arpa.       86400   IN      NS      arin.authdns.ripe.net.
144.in-addr.arpa.       86400   IN      DS      62856 5 1 484154736CF9D4DC4F1C2B807BDC06E5B1645AFF
144.in-addr.arpa.       86400   IN      RRSIG   DS 8 3 86400 20170328085556 20170307105911 4341 in-addr.arpa. 
X3nPKgjQbRef6BxK3msEXi/IcfpG1rylY2xeWwfNO6fJB5x/QT38ZCA5 XMs6CBeXb59tpQFbgjwZX+prqSpjGFtZ+phFuzsaGmuPOF0FFypMHj7F 
swykEFvaPY5z4d8mo9FKFJetF2gZfzYthwJWW0x2oo2H2BG0lEedVUCb 1aGs/HE=
;; Received 380 bytes from 193.0.9.1#53(f.in-addr-servers.arpa) in 48 ms

144.in-addr.arpa.       0       IN      SOA     z.arin.net. dns-ops.arin.net. 2017022432 1800 900 691200 10800
144.in-addr.arpa.       0       IN      RRSIG   SOA 5 3 86400 20170331083220 20170317073220 33345 144.in-addr.arpa. 
k2sZXuQQR3MyyRiB9Wd7fw45yZTbNokjQtFFNY+aCEa/85AnSyuomLlZ jZs4A0bO376/Z1v+bTHoeFqsyHr/xuWHX74r0QC/TCeP0amc+w8RqCvw 
Yox1TfoJxwhblGNRCgyLw52WszMYyr49EfWPfpHAKFU+G94gdilf3C6x GOM=
144.in-addr.arpa.       10800   IN      NSEC    0.144.in-addr.arpa. NS SOA RRSIG NSEC DNSKEY
144.in-addr.arpa.       10800   IN      RRSIG   NSEC 5 3 10800 20170331083220 20170317073220 33345 144.in-addr.arpa. 
opvG8SC7+UjHSTtBBtekWNkhLFMIxFxOdejJ7sM7t8lyGNzM6sOABeSI ADXfo8q3p4YFBHgBU5fRCAhBdiQ/AiZC0dLMnHb4WdKEv5bDsBbq5Pt6 
vabJaIv7Gizw7kBy1JZ/ZrC4Jmp4EX0HiYA+Ak+aQggD7gdI/6tFDNpl N7M=
205.144.in-addr.arpa.   10800   IN      NSEC    207.144.in-addr.arpa. NS RRSIG NSEC
205.144.in-addr.arpa.   10800   IN      RRSIG   NSEC 5 4 10800 20170331083220 20170317073220 33345 144.in-addr.arpa. 
F1e5mA7C3Mx10YSaNtshzfzfER8pudDOQkUoe+jeDhHeDZeR8FM1FoqW dqrNh5X6JVNlTdWGio6evnSkxnaoJFYyeYJtc+tJ8dTd5APJxJCSOfhH 
VfRNy7VHs2PdElRo1rRwMw+5Zncc0u8uPdmFDv2ZG8Vv3zj5C6l7rMla 3SA=
;; Received 718 bytes from 199.212.0.63#53(z.arin.net) in 128 ms
}}}

Seems like the other /16 from 144.in-addr.arpa are affected too
(at least).

ARIN tickets are engaged, but I am seeking some live person:
having the whole reverse zone being unavailable isn't the stuff
that is to be handled in 5x8 or alike.

If anybody knows what happened, can point me to my errors
in assertions or give an e-mail/phone of 24x7-like person
or service at ARIN -- will be tremendous.

Thanks!
-- 
Eygene Ryabinkin, National Research Centre "Kurchatov Institute"

Always code as if the guy who ends up maintaining your code will be
a violent psychopath who knows where you live.


Current thread: