You can find a detailed announcement from the RIPE NCC here:
https://www.ripe.net/ripe/mail/archives/dns-wg/2017-March/003394.html
<https://www.ripe.net/ripe/mail/archives/dns-wg/2017-March/003394.html>
-Alex Band
> On 17 Mar 2017, at 12:31, John Curran <jcur...@istaff.org> wrote:
>
> 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 <rea+na...@grid.kiae.ru> wrote:
>>
>> Job, good day.
>>
>> Fri, Mar 17, 2017 at 09:55:56AM +0000, 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 NS m.root-servers.net.
>> . 202634 IN NS i.root-servers.net.
>> . 202634 IN NS k.root-servers.net.
>> . 202634 IN NS c.root-servers.net.
>> . 202634 IN NS a.root-servers.net.
>> . 202634 IN NS d.root-servers.net.
>> . 202634 IN NS l.root-servers.net.
>> . 202634 IN NS e.root-servers.net.
>> . 202634 IN NS g.root-servers.net.
>> . 202634 IN NS b.root-servers.net.
>> . 202634 IN NS j.root-servers.net.
>> . 202634 IN NS h.root-servers.net.
>> . 202634 IN NS f.root-servers.net.
>> . 511016 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 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.
>> in-addr.arpa. 86400 IN DS 47054 8 2
>> 5CAFCCEC201D1933B4C9F6A9C8F51E51F3B39979058AC21B8DF1B1F2 81CBC6F2
>> 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 RRSIG DS 8 2 86400
>> 20170330000000 20170316230000 33786 arpa.
>> gqNN6MmLVxFtSG0oxdyoYVSXZlp6vY9yxpnJW89TYCHfTkv+ZmklM76O
>> IHdTznEhLHXbyr4BaxjFCshsC3WacdH/YZYa/SZynJ9Q1N6/bogrIUTn
>> qs61Y/YD4Sk5lI7YvUxVnPrF3lk1pY8dpoTkprTLZngoeQEsm552inqG ypU=
>> ;; Received 731 bytes from 193.0.14.129#53(k.root-servers.net) in 41 ms
>>
>> 171.in-addr.arpa. 86400 IN NS ns1.apnic.net.
>> 171.in-addr.arpa. 86400 IN NS ns2.lacnic.net.
>> 171.in-addr.arpa. 86400 IN NS ns3.apnic.net.
>> 171.in-addr.arpa. 86400 IN NS ns4.apnic.net.
>> 171.in-addr.arpa. 86400 IN NS apnic.authdns.ripe.net.
>> 171.in-addr.arpa. 86400 IN NS apnic1.dnsnode.net.
>> 171.in-addr.arpa. 86400 IN NS tinnie.arin.net.
>> 171.in-addr.arpa. 86400 IN DS 49699 5 1
>> 0240801C96480900CC6D93130AF45CFE86EDE940
>> 171.in-addr.arpa. 86400 IN DS 49699 5 2
>> 6E0BA96F05B4D39C1668979731E040213BB6130DE33E86E063B5F7F7 5C465C88
>> 171.in-addr.arpa. 86400 IN RRSIG DS 8 3 86400 20170330042932
>> 20170309125911 4341 in-addr.arpa.
>> RKcPZJdG1MBrwpfa1mIK7ikIU585i1Jv+UkEBHxuM3BxxAbD+ht0W04C
>> ljboyXJfYK8ly/YTDqNUkWKZLwDHlkq/rgNwTG63sPT8iK8qya+2qUVB
>> iTXVsD2HaV1V/KwgJjlWHRNnlwkK0YZ5Q7tevXaq4yyLT2Q2mu5dkhFC evNQOyI=
>> ;; Received 482 bytes from 199.253.183.183#53(b.in-addr-servers.arpa) in 69
>> ms
>>
>> 171.in-addr.arpa. 0 IN SOA ns1.apnic.net.
>> read-txt-record-of-zone-first-dns-admin.apnic.net. 5276 7200 1800 604800
>> 172800
>> 171.in-addr.arpa. 0 IN RRSIG SOA 5 3 172800 20170416100102
>> 20170317090102 7858 171.in-addr.arpa.
>> dH+uuGq9pgMc9TEMkTwrf9NGMj5zFnbZt3kjlNSF0kPzGk3WUr5g84jv
>> 0SN88Y26eP/Op4Vv8JewyVu2IT1POnmiNpDYELkJxrTWnPPc6CJ2wugR
>> TrFLOq6eIsqtrCcWbatQ7XSXXj1UglqVVydlX1ExoIh9MdP+1eBneD1I 4OU=
>> 171.in-addr.arpa. 172800 IN NSEC 10.171.in-addr.arpa. NS SOA TXT
>> RRSIG NSEC DNSKEY
>> 171.in-addr.arpa. 172800 IN RRSIG NSEC 5 3 172800 20170416100102
>> 20170317090102 7858 171.in-addr.arpa.
>> QieHZ0W7jx3QCgLuvqtKtFoLPYkxn5R9nRO1oMbSSXkdF+S4iQQkVlX7
>> DyQvoL69hKA+S9idfernf6DwNTQgeWFfCdjUyOjMCa3Ag/S8ARZs7K4F
>> N9DxB/cBCZm7KTzwAzXFe3cJ/d1Wo45Tx9jf6Drx551oqOw1gmDIL4y6 +k4=
>> ;; Received 530 bytes from 202.12.31.140#53(ns4.apnic.net) in 347 ms
>> }}}
>> since it is APNIC who respond to queries about it. Any more specific
>> reverse records that are cross ARIN and die there from 171.x.y.z?
>> --
>> 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.
>
>
