[as112-ops] PTR for private networks.
Marc Storck
mstorck at voipgate.com
Mon Dec 16 11:31:03 UTC 2013
Hello Sergey,
Hello Roman,
as Jonathan already stated, the AS112 project is anycasted. ICANN does NOT manage these nodes.
However, you may find the operator of a node by running
dig hostname.as112.net in txt
in rare cases the following may help as well:
dig @192.175.48.6 chaos txt hostname.bind
and contact the operator listed for the faulty node.
Regards,
Marc Storck
On Dec 16, 2013, at 12:03 PM, Sergey Putko <psv at webzilla.com>
wrote:
> Hi Jonathan,
>
> I doesn’t know what wrong on blackhole-{1,2}.iana.org or something in AS112. As I see, timeouts from some networks, from separate providers and countries.
> Currently on my dns cache servers I created records like:
> zone "10.in-addr.arpa" IN { type master; file "named.empty"; allow-update { none; }; allow-query { any; }; };
>
> This solved issue for me, but I think something wrong with access to blackhole from internet.
> This is reply from ICANN:
>
>> Reverse DNS services for private address space are provided by a loosely coordinated group of network operators via the AS112 project: https://www.as112.net/
>>
>> Ideally, you or your ISP should be providing authoritative reverse DNS answers for private address space. However, if that is not the case and your queries are forwarded to the Internet, they could be answered by whichever AS112 server is closest to you.
>>
>> You can either track down the operator of the server in question or stand up your own AS112 service.
>
>
>
> On Dec 14, 2013, at 2:17 AM, Jonathan Stewart <jonathan.stewart at gmail.com> wrote:
>
>> Hi Sergey,
>>
>> Are you aware that blackhole-1 and -2.iana.org are anycasted?
>>
>> Perhaps the local nodes you are being routed to are malfunctioning.
>>
>> If so, best way to fix would be to contact the operator of that node.
>>
>> Jonathan
>>
>>
>> On Fri, Dec 6, 2013 at 3:19 AM, Sergey Putko <psv at webzilla.com> wrote:
>> Hello,
>>
>> I see issue from some IPs for requests to blackhole-1.iana.org and blackhole-2.iana.org :
>>
>> I see this issue from 78.140.128.0/18 199.80.52.0/22 and some other locations IPs.
>> DIG trace:
>> Sergeys-MacBook-Air:~ psv$ dig +trace 51.10.10.10.in-addr.arpa
>>
>> ; <<>> DiG 9.8.3-P1 <<>> +trace 51.10.10.10.in-addr.arpa
>> ;; global options: +cmd
>> . 29 IN NS a.root-servers.net.
>> . 29 IN NS l.root-servers.net.
>> . 29 IN NS g.root-servers.net.
>> . 29 IN NS b.root-servers.net.
>> . 29 IN NS d.root-servers.net.
>> . 29 IN NS e.root-servers.net.
>> . 29 IN NS k.root-servers.net.
>> . 29 IN NS m.root-servers.net.
>> . 29 IN NS f.root-servers.net.
>> . 29 IN NS h.root-servers.net.
>> . 29 IN NS c.root-servers.net.
>> . 29 IN NS j.root-servers.net.
>> . 29 IN NS i.root-servers.net.
>> ;; Received 512 bytes from 78.140.128.205#53(78.140.128.205) in 76 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 418 bytes from 199.7.83.42#53(199.7.83.42) in 501 ms
>>
>> 10.in-addr.arpa. 86400 IN NS blackhole-1.iana.org.
>> 10.in-addr.arpa. 86400 IN NS blackhole-2.iana.org.
>> ;; Received 102 bytes from 196.216.169.10#53(196.216.169.10) in 499 ms
>>
>> ;; connection timed out; no servers could be reached
>>
>>
>> Traces:
>> # traceroute blackhole-2.iana.org
>> traceroute to blackhole-2.iana.org (192.175.48.42), 64 hops max, 52 byte packets
>> 1 199.101.135.81 (199.101.135.81) 0.185 ms 0.177 ms 0.174 ms
>> 2 webzilla-ipt-gw.r3.dal.iptransit.com (204.26.60.25) 1.210 ms 0.337 ms 0.308 ms
>> 3 xe-0-0-2.r1.ny.iptransit.com (204.26.60.67) 48.751 ms 41.636 ms 45.107 ms
>> 4 xe-0-3-1.r1.lon.iptransit.com (204.26.60.209) 119.682 ms 115.897 ms 119.413 ms
>> 5 ae3.r2.ams.tc2.nl.iptransit.com (199.59.206.150) 118.436 ms 118.260 ms 124.804 ms
>> 6 ae2.r1.de.iptransit.com (199.59.206.125) 128.275 ms 128.400 ms 129.036 ms
>> 7 204.26.63.110 (204.26.63.110) 159.565 ms 158.455 ms 158.485 ms
>> 8 GW-Coordinator.retn.net (87.245.239.38) 177.180 ms 177.078 ms 177.199 ms
>> 9 * * *
>> 10 * * *
>> 11 * * *
>> 12 * * *
>> 13 * * *
>> 14 * * *
>> 15 * * *
>> ^C
>>
>> # traceroute blackhole-1.iana.org
>> traceroute to blackhole-1.iana.org (192.175.48.6), 64 hops max, 52 byte packets
>> 1 199.101.135.81 (199.101.135.81) 0.150 ms 26.598 ms 53.376 ms
>> 2 webzilla-ipt-gw.r3.dal.iptransit.com (204.26.60.25) 0.309 ms 5.788 ms 0.303 ms
>> 3 xe-0-0-2.r1.ny.iptransit.com (204.26.60.67) 45.115 ms 45.170 ms 42.719 ms
>> 4 xe-0-3-1.r1.lon.iptransit.com (204.26.60.209) 115.872 ms 115.866 ms 115.857 ms
>> 5 ae3.r2.ams.tc2.nl.iptransit.com (199.59.206.150) 118.360 ms 118.425 ms 118.451 ms
>> 6 ae2.r1.de.iptransit.com (199.59.206.125) 128.459 ms 128.475 ms 128.226 ms
>> 7 204.26.63.110 (204.26.63.110) 158.454 ms 158.721 ms 158.337 ms
>> 8 GW-Coordinator.retn.net (87.245.239.38) 177.314 ms 177.308 ms 177.543 ms
>> 9 * * *
>> 10 * * *
>> 11 * * *
>> 12 * * *
>> 13 * *^C
>>
>>
>> # traceroute blackhole-2.iana.org
>> traceroute to blackhole-2.iana.org (192.175.48.42), 64 hops max, 52 byte packets
>> 1 78.140.128.227 (78.140.128.227) 0.234 ms 0.207 ms 0.207 ms
>> 2 ae12.j-evo-d4.webzilla.com (78.140.169.25) 0.202 ms 0.209 ms 0.194 ms
>> 3 ae1.10.r2.ams.tc2.nl.iptransit.com (199.59.206.153) 0.624 ms 0.625 ms 0.621 ms
>> 4 ae2.r1.de.iptransit.com (199.59.206.125) 7.238 ms 7.278 ms 7.297 ms
>> 5 204.26.63.110 (204.26.63.110) 37.336 ms 37.381 ms 37.384 ms
>> 6 GW-Coordinator.retn.net (87.245.239.38) 59.699 ms 59.669 ms 59.653 ms
>> 7 * * *
>> 8 * * *
>> 9 * * *
>> 10 *^C
>>
>> # traceroute blackhole-1.iana.org
>> traceroute to blackhole-1.iana.org (192.175.48.6), 64 hops max, 52 byte packets
>> 1 78.140.128.227 (78.140.128.227) 0.243 ms 0.207 ms 0.254 ms
>> 2 ae12.j-evo-d4.webzilla.com (78.140.169.25) 0.644 ms 0.200 ms 0.249 ms
>> 3 ae1.10.r2.ams.tc2.nl.iptransit.com (199.59.206.153) 0.659 ms 0.618 ms 0.628 ms
>> 4 ae2.r1.de.iptransit.com (199.59.206.125) 7.246 ms 7.299 ms 7.302 ms
>> 5 204.26.63.110 (204.26.63.110) 37.374 ms 37.370 ms 41.973 ms
>> 6 GW-Coordinator.retn.net (87.245.239.38) 59.826 ms 59.757 ms 59.821 ms
>> 7 * * *
>> 8 * * *
>> 9 * * *
>> 10 * * *
>> 11 * * *
>> 12 * *^C
>>
>> Also same issue from not IPTransit network:
>> Sergeys-MacBook-Air:~ psv$ traceroute blackhole-2.iana.org
>> traceroute to blackhole-2.iana.org (192.175.48.42), 64 hops max, 52 byte packets
>> 1 192.168.77.1 (192.168.77.1) 1.957 ms 1.451 ms 6.681 ms
>> 2 customer.maycom.net.ua (91.103.127.1) 3.628 ms 2.673 ms 2.009 ms
>> 3 custumer.maycom.net.ua (91.103.120.145) 3.278 ms 2.811 ms 4.332 ms
>> 4 93.183.213.97 (93.183.213.97) 11.415 ms 20.845 ms 33.451 ms
>> 5 ae20-771.s31.kiev.datagroup.ua (80.91.160.117) 17.208 ms 23.006 ms 20.418 ms
>> 6 dg.eunic.net.ua (77.222.149.94) 29.682 ms 30.045 ms 29.560 ms
>> 7 * * *
>> 8 * * *
>> 9 * * *
>> 10 * * *
>> 11 * * *
>> 12 * * *
>> 13 * * *
>> 14 * * *
>> 15 * * *
>> 16 * * *
>> 17 * * *
>> 18 * * *
>> 19 *^C
>>
>> Sergeys-MacBook-Air:~ psv$ traceroute blackhole-1.iana.org
>> traceroute to blackhole-1.iana.org (192.175.48.6), 64 hops max, 52 byte packets
>> 1 192.168.77.1 (192.168.77.1) 94.100 ms 2.744 ms 1.820 ms
>> 2 customer.maycom.net.ua (91.103.127.1) 1.859 ms 2.131 ms 1.509 ms
>> 3 custumer.maycom.net.ua (91.103.120.145) 3.433 ms 2.870 ms 2.716 ms
>> 4 93.183.213.97 (93.183.213.97) 9.871 ms 10.070 ms 69.783 ms
>> 5 ae20-771.s31.kiev.datagroup.ua (80.91.160.117) 31.996 ms 21.792 ms *
>> 6 dg.eunic.net.ua (77.222.149.94) 82.175 ms 31.107 ms 31.272 ms
>> 7 * * *
>> 8 * * *
>> 9 * *^C
>>
>> But its works from 223.25.232.0/21 103.24.200.0/22 and some other networks
>> DIG trace:
>> # dig +trace 51.10.10.10.in-addr.arpa
>>
>> ; <<>> DiG 9.8.3-P4 <<>> +trace 51.10.10.10.in-addr.arpa
>> ;; global options: +cmd
>> . 284 IN NS j.root-servers.net.
>> . 284 IN NS m.root-servers.net.
>> . 284 IN NS a.root-servers.net.
>> . 284 IN NS b.root-servers.net.
>> . 284 IN NS l.root-servers.net.
>> . 284 IN NS e.root-servers.net.
>> . 284 IN NS k.root-servers.net.
>> . 284 IN NS i.root-servers.net.
>> . 284 IN NS g.root-servers.net.
>> . 284 IN NS d.root-servers.net.
>> . 284 IN NS f.root-servers.net.
>> . 284 IN NS c.root-servers.net.
>> . 284 IN NS h.root-servers.net.
>> ;; Received 228 bytes from 103.24.200.77#53(103.24.200.77) in 1193 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 418 bytes from 199.7.83.42#53(199.7.83.42) in 3492 ms
>>
>> 10.in-addr.arpa. 86400 IN NS blackhole-2.iana.org.
>> 10.in-addr.arpa. 86400 IN NS blackhole-1.iana.org.
>> ;; Received 102 bytes from 193.0.9.1#53(193.0.9.1) in 651 ms
>>
>> 10.in-addr.arpa. 300 IN SOA prisoner.iana.org. hostmaster.root-servers.org. 2002040800 1800 900 604800 604800
>> ;; Received 134 bytes from 192.175.48.6#53(192.175.48.6) in 167 ms
>>
>> Traces:
>> # traceroute blackhole-1.iana.org
>> traceroute to blackhole-1.iana.org (192.175.48.6), 64 hops max, 52 byte packets
>> 1 223-25-237-145.revdns.8toinfinity.com.sg (223.25.237.145) 0.315 ms 0.351 ms 0.269 ms
>> 2 ipt-8to-gw.r1.sg.iptransit.com (199.59.206.225) 0.946 ms 1.081 ms 0.861 ms
>> 3 te4.4.br02.sin02.pccwbtn.net (63.218.213.185) 0.943 ms 0.916 ms 0.905 ms
>> 4 sv-ibx.r1.sjc3.isc.org (206.223.116.2) 182.635 ms 182.637 ms 184.037 ms
>> 5 int-0-1-0-4.r1.pao1.isc.org (149.20.65.18) 220.854 ms 220.779 ms 220.878 ms
>> 6 int-0-0-1-0.r1.sql1.isc.org (149.20.65.10) 222.256 ms 222.783 ms 222.460 ms
>> 7 blackhole-1.iana.org (192.175.48.6) 218.269 ms 218.220 ms 218.306 ms
>>
>> # traceroute blackhole-2.iana.org
>> traceroute to blackhole-2.iana.org (192.175.48.42), 64 hops max, 52 byte packets
>> 1 223-25-237-145.revdns.8toinfinity.com.sg (223.25.237.145) 0.416 ms 0.278 ms 0.260 ms
>> 2 ipt-8to-gw.r1.sg.iptransit.com (199.59.206.225) 0.939 ms 0.857 ms 0.844 ms
>> 3 te4.4.br02.sin02.pccwbtn.net (63.218.213.185) 0.902 ms 0.899 ms 0.883 ms
>> 4 sv-ibx.r1.sjc3.isc.org (206.223.116.2) 183.446 ms 182.178 ms 183.384 ms
>> 5 int-0-1-0-4.r1.pao1.isc.org (149.20.65.18) 221.133 ms 220.901 ms 220.863 ms
>> 6 int-0-0-1-0.r1.sql1.isc.org (149.20.65.10) 222.214 ms 222.838 ms 222.075 ms
>> 7 blackhole-2.iana.org (192.175.48.42) 220.379 ms 220.011 ms 220.130 ms
>>
>> # traceroute blackhole-1.iana.org
>> traceroute to blackhole-1.iana.org (192.175.48.6), 64 hops max, 52 byte packets
>> 1 103.24.200.49 (103.24.200.49) 0.418 ms 0.853 ms 0.222 ms
>> 2 103.248.82.17 (103.248.82.17) 4.884 ms 0.228 ms 0.219 ms
>> 3 10.45.40.2 (10.45.40.2) 0.215 ms 0.225 ms 0.217 ms
>> 4 115.249.168.150 (115.249.168.150) 14.257 ms 14.263 ms 20.812 ms
>> 5 * 115.255.252.57 (115.255.252.57) 16.005 ms 15.979 ms
>> 6 62.216.147.101 (62.216.147.101) 66.045 ms 72.346 ms 65.594 ms
>> 7 so-0-1-0.0.pjr02.ldn001.flagtel.com (85.95.25.137) 199.279 ms 199.314 ms 199.321 ms
>> 8 so-1-0-0.0.cjr02.ldn004.flagtel.com (85.95.25.10) 226.890 ms 229.263 ms 328.613 ms
>> 9 62.216.145.114 (62.216.145.114) 158.879 ms 158.761 ms 158.722 ms
>> 10 i68geb-025-ten0-1-0-1.bb.ip-plus.net (138.187.129.108) 157.779 ms 156.700 ms 159.656 ms
>> 11 i00par-005-ten4-1.bb.ip-plus.net (138.187.130.7) 163.085 ms 163.249 ms 162.932 ms
>> 12 frequence3-gig0.bb.ip-plus.net (193.5.122.62) 160.589 ms 160.439 ms 160.590 ms
>> 13 10Ge2-2-rt2-th2.hivane.net (193.17.192.130) 163.709 ms 160.439 ms 160.435 ms
>> 14 ve286-rt-std.hivane.net (193.200.42.138) 165.267 ms 164.806 ms 164.178 ms
>> 15 blackhole-1.iana.org (192.175.48.6) 166.205 ms 166.055 ms 166.051 ms
>>
>> # traceroute blackhole-2.iana.org
>> traceroute to blackhole-2.iana.org (192.175.48.42), 64 hops max, 52 byte packets
>> 1 103.24.200.49 (103.24.200.49) 0.412 ms 0.221 ms 0.213 ms
>> 2 103.248.82.17 (103.248.82.17) 1.301 ms 0.221 ms 0.206 ms
>> 3 10.45.40.2 (10.45.40.2) 0.209 ms 0.374 ms 0.521 ms
>> 4 115.249.168.150 (115.249.168.150) 14.407 ms 14.260 ms 14.259 ms
>> 5 * 115.255.252.229 (115.255.252.229) 33.074 ms 32.854 ms
>> 6 62.216.147.101 (62.216.147.101) 82.584 ms 87.891 ms 82.485 ms
>> 7 so-0-1-0.0.pjr02.ldn001.flagtel.com (85.95.25.137) 216.148 ms 216.140 ms 216.136 ms
>> 8 so-1-0-0.0.cjr02.ldn004.flagtel.com (85.95.25.10) 247.642 ms 259.198 ms 267.922 ms
>> 9 62.216.145.114 (62.216.145.114) 207.391 ms 208.952 ms 214.996 ms
>> 10 i68geb-025-ten0-1-0-1.bb.ip-plus.net (138.187.129.108) 214.883 ms 211.458 ms 212.079 ms
>> 11 i00par-005-ten4-1.bb.ip-plus.net (138.187.130.7) 224.552 ms 225.370 ms 229.087 ms
>> 12 frequence3-gig0.bb.ip-plus.net (193.5.122.62) 227.982 ms 227.670 ms 231.468 ms
>> 13 10Ge2-2-rt2-th2.hivane.net (193.17.192.130) 230.010 ms 232.043 ms 235.161 ms
>> 14 ve286-rt-std.hivane.net (193.200.42.138) 233.596 ms 231.885 ms 232.347 ms
>> 15 blackhole-2.iana.org (192.175.48.42) 232.505 ms 234.562 ms 235.943 ms
>>
>> traceroute to blackhole-1.iana.org (192.175.48.6), 64 hops max, 72 byte packets
>> 1 hosted.by.leaseweb.com (108.59.11.94) 0.163 ms 0.168 ms 0.129 ms
>> 2 108.59.15.142 (108.59.15.142) 0.575 ms 0.673 ms 0.495 ms
>> 3 te7-1.msc1.wdc.leaseweb.net (217.20.125.48) 0.337 ms 0.342 ms 0.300 ms
>> 4 xe0-0-0.ms1.pax.leaseweb.net (217.20.125.21) 63.655 ms 63.683 ms 63.681 ms
>> 5 217.20.125.202 (217.20.125.202) 63.815 ms 63.776 ms 63.792 ms
>> 6 pajbb001.int-gw.kddi.ne.jp (111.87.3.49) 63.711 ms 63.690 ms 63.696 ms
>> 7 otejbb205.int-gw.kddi.ne.jp (203.181.100.137) 164.832 ms 164.829 ms 164.868 ms
>> 8 obpjbb205.int-gw.kddi.ne.jp (59.128.4.178) 176.908 ms 176.909 ms 192.824 ms
>> 9 hkmjbb001.kddnet.ad.jp (118.155.199.194) 217.178 ms 217.174 ms 217.187 ms
>> 10 cm-hkm001.int-gw.kddi.ne.jp (111.87.5.18) 383.058 ms 382.932 ms 404.302 ms
>> 11 59.128.59.38 (59.128.59.38) 222.634 ms 222.649 ms 229.697 ms
>> 12 HOST-162.EDGE-FO.FRA2.VERISIGN.COM (199.7.61.162) 218.463 ms 218.460 ms 218.445 ms
>> 13 blackhole-1.iana.org (192.175.48.6) 224.677 ms 224.683 ms 225.372 ms
>>
>>
>> I can ping blackhole-1.iana.org and blackhole-2.iana.org from any networks, but for UDP I got timeouts from some places, maybe this is something wrong from your side?
>>
>> How we can solve this issue, maybe you need some additional info ?
>>
>> Thanks.
>>
>> _______________________________________________
>> as112-ops mailing list
>> as112-ops at lists.dns-oarc.net
>> https://lists.dns-oarc.net/mailman/listinfo/as112-ops
>>
>>
>>
>>
>> --
>> Jonathan
>
> _______________________________________________
> as112-ops mailing list
> as112-ops at lists.dns-oarc.net
> https://lists.dns-oarc.net/mailman/listinfo/as112-ops
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.dns-oarc.net/pipermail/as112-ops/attachments/20131216/81d9aaa8/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4422 bytes
Desc: not available
URL: <http://lists.dns-oarc.net/pipermail/as112-ops/attachments/20131216/81d9aaa8/attachment-0001.bin>
More information about the as112-ops
mailing list