blackhole-*.iana.org gone ?
Hi, The nameserver on blackhole-[12].iana.org does not seem to reply queries for me. $ dig @blackhole-1.iana.org PTR 1.0.0.10.in-addr.arpa. ; <<>> DiG 8.3 <<>> @blackhole-1.iana.org PTR 1.0.0.10.in-addr.arpa. ; (1 server found) ;; res options: init recurs defnam dnsrch ;; res_nsend: Connection refused I am in AS12859. Is anybody else experiencing this problem ? -- Met vriendelijke groet, BIT BV / Ing P.B. van Pelt PBVP1-RIPE (PGPKEY-4DCA7E5E)
Hi,
I am in AS12859. Is anybody else experiencing this problem ?
at least the Autonomica instance, which I happen to use, works. You may want to look at <http://www.as112.net> -Peter
On Fri, 2004-10-01 at 16:54, Peter Koch wrote:
Hi,
I am in AS12859. Is anybody else experiencing this problem ?
at least the Autonomica instance, which I happen to use, works. You may want to look at <http://www.as112.net>
The one in palo alto works: 15 r3-sfo2.r8.pao1.isc.org (192.5.4.232) [AS3557] 158 ms 158 ms 158 ms 16 blackhole-1.iana.org (192.175.48.6) [AS112/AS8001/AS7586/AS13591/AS9942/AS12885] 158 ms 158 ms 158 ms $ dig +short @blackhole-1.iana.org hostname.bind ch txt hostname.bind. 0 CH TXT "hazel.isc.org" Though the next second when one retries it doesn't, and then it is quite apparently, there is no other at AMS-IX, the AS112 installation at ripe according to a traceroute. Unfortunatly there is no direct contact http://www.ripe.net/as112/ though ops@ripe.net are probably in charge. There is a small dip in the graph which might clarify that this is really that node giving problems. Above effect seen from behind AS8251 and AS12871. $ traceroute -A blackhole-1.iana.org traceroute to blackhole-1.iana.org (192.175.48.6), 64 hops max, 40 byte packets 1 nrp-1.bras-1.ams-tel.cistron.net (195.64.92.1) [AS8251] 10 ms 9 ms 9 ms 2 ve-4.rtr-1.ams-sar.cistron.net (62.216.29.1) [AS8251] 10 ms 10 ms 9 ms 3 blackhole-1.iana.org (192.175.48.6) [AS112/AS8001/AS7586/AS13591/AS9942/AS12885] 10 ms 9 ms 9 ms Greets, Jeroen
On 1 Oct 2004, at 10:44, Pim van Pelt wrote:
The nameserver on blackhole-[12].iana.org does not seem to reply queries for me.
$ dig @blackhole-1.iana.org PTR 1.0.0.10.in-addr.arpa.
; <<>> DiG 8.3 <<>> @blackhole-1.iana.org PTR 1.0.0.10.in-addr.arpa. ; (1 server found) ;; res options: init recurs defnam dnsrch ;; res_nsend: Connection refused
I am in AS12859. Is anybody else experiencing this problem ?
blackhole-1.iana.org and blackhole-2.iana.org are anycast as part of the AS112 project. See <http://www.as112.net>. Chances are good that the experiences of other people on this list may not be directly relevant to your problem. Traceroutes show "show ip bgp" to the affected addresses might help identify the actual server you're using. Joe
Hi, | >The nameserver on blackhole-[12].iana.org does not seem to reply | >queries | >for me. | > | >$ dig @blackhole-1.iana.org PTR 1.0.0.10.in-addr.arpa. | > | >; <<>> DiG 8.3 <<>> @blackhole-1.iana.org PTR 1.0.0.10.in-addr.arpa. | >; (1 server found) | >;; res options: init recurs defnam dnsrch | >;; res_nsend: Connection refused | > | >I am in AS12859. Is anybody else experiencing this problem ? | | blackhole-1.iana.org and blackhole-2.iana.org are anycast as part of | the AS112 project. See <http://www.as112.net>. traceroute to blackhole-1.iana.org (192.175.48.6), 64 hops max, 44 byte packets 1 jun1 (193.109.122.225) 0.242 ms 0.243 ms 0.591 ms 2 jun1.sara.network.bit.nl (213.136.31.3) 2.811 ms 1.528 ms 1.474 ms 3 blackhole-1.iana.org (192.175.48.6) 2.160 ms 1.329 ms 1.449 ms These are the AMS-IX based nodes. The 193.148.15.39 unicast address which accompanies the AS112 instance at the RIPE NCC seems to have vanished from my routing tables and is therefor not reachable. NCC folks ? -- Met vriendelijke groet, BIT BV / Ing P.B. van Pelt PBVP1-RIPE (PGPKEY-4DCA7E5E)
Hi, At 17:15 01/10/2004 +0200, Pim van Pelt wrote:
Hi,
| >The nameserver on blackhole-[12].iana.org does not seem to reply | >queries for me.
[..] We are indeed having problems with the AS112 server at AMS-IX ( as112.ripe.net [195.69.144.39] ). I have just removed it's advertisement of the 192.175.48.0/24 network. Those of you at AMS-IX who have been experiencing problems should now be using another AS112 server. I'll send a follow-up to the list when we have resolved the problem. Cheers, dave
Hi, | We are indeed having problems with the AS112 server at AMS-IX | ( as112.ripe.net [195.69.144.39] ). | | I have just removed it's advertisement of the 192.175.48.0/24 | network. Those of you at AMS-IX who have been experiencing | problems should now be using another AS112 server. Confirmed, I am reaching one of the instances in London now and this one is just fine. Thanks for acting, it saves some of my customers the hassle of setting up their own zones. They have come to rely on the NXDOMAIN answers they are getting :) -- Met vriendelijke groet, BIT BV / Ing P.B. van Pelt PBVP1-RIPE (PGPKEY-4DCA7E5E)
Hi, The RIPE NCC AS112 server, as112.ripe.net [195.69.144.39] is up and running again and is advertising the 192.175.48.0/24 network. Please report any outstanding issues to: RIPE NCC Operations <ops@ripe.net> Apologies for any inconvenience. Cheers, dave
At 19:36 01/10/2004 +0200, Dave Knight wrote:
Hi,
The RIPE NCC AS112 server, as112.ripe.net [195.69.144.39] is up and running again and is advertising the 192.175.48.0/24 network.
As we are continuing to have issues with this machine and have decided to take it offline until they are definitively fixed. We plan to replace the hardware and bring it back online next week. Cheers, dave
participants (5)
-
Dave Knight -
Jeroen Massar -
Joe Abley -
Peter Koch -
Pim van Pelt