[Outages-discussion] [outages] whois.arin.net refuses connections on v6

Frank Bulk frnkblk at iname.com
Mon Jul 2 10:44:02 EDT 2012


ARIN's CTO shared with me that this was due to the leap second bug.
Originally ARIN staff thought it was due to the maintenance they performed
Saturday morning.

 

Frank

 

From: outages-bounces at outages.org [mailto:outages-bounces at outages.org] On
Behalf Of Owen DeLong
Sent: Sunday, July 01, 2012 10:08 PM
To: Tony McCrory
Cc: outages at outages.org
Subject: Re: [outages] whois.arin.net refuses connections on v6

 

Works for me currently from 2620:0:930::/48 (AS1734)

 

 

Owen

 

On Jun 30, 2012, at 5:14 PM, Tony McCrory wrote:





Starting in the last 24 hours I've not been able to query whois.arin.net
<http://whois.arin.net/>  over v6.  v4 works fine.

 

Anyone else see the same?  

 

Tony

 

$ whois -h whois.arin.net <http://whois.arin.net/>  127.0.0.0

[Querying whois.arin.net <http://whois.arin.net/> ]

[Unable to connect to remote host]

$ host whois.arin.net <http://whois.arin.net/> 

whois.arin.net <http://whois.arin.net/>  has address 199.71.0.48

whois.arin.net <http://whois.arin.net/>  has address 199.71.0.47

whois.arin.net <http://whois.arin.net/>  has address 199.71.0.46

whois.arin.net <http://whois.arin.net/>  has address 199.212.0.48

whois.arin.net <http://whois.arin.net/>  has address 199.212.0.46

whois.arin.net <http://whois.arin.net/>  has address 199.212.0.47

whois.arin.net <http://whois.arin.net/>  has IPv6 address 2001:500:13::47

whois.arin.net <http://whois.arin.net/>  has IPv6 address 2001:500:31::47

whois.arin.net <http://whois.arin.net/>  has IPv6 address 2001:500:13::46

whois.arin.net <http://whois.arin.net/>  has IPv6 address 2001:500:31::48

whois.arin.net <http://whois.arin.net/>  has IPv6 address 2001:500:13::48

whois.arin.net <http://whois.arin.net/>  has IPv6 address 2001:500:31::46

$ whois -h 2001:500:13::47 127.0.0.0

[Querying 2001:500:13::47]

[Unable to connect to remote host]

$ whois -h 2001:500:31::47 127.0.0.0

[Querying 2001:500:31::47]

[Unable to connect to remote host]

$ whois -h 2001:500:31::48 127.0.0.0

[Querying 2001:500:31::48]

[Unable to connect to remote host]

$ whois -h 2001:500:13::48 127.0.0.0

[Querying 2001:500:13::48]

[Unable to connect to remote host]

$ whois -h 2001:500:13::46 127.0.0.0

[Querying 2001:500:13::46]

[Unable to connect to remote host]

$ whois -h 2001:500:31::46 127.0.0.0

[Querying 2001:500:31::46]

[Unable to connect to remote host]

 

v4 works:

$ whois -h 199.212.0.47 127.0.0.0

[Querying 199.212.0.47]

[199.212.0.47]

#

# Query terms are ambiguous.  The query is assumed to be:

#     "n 127.0.0.0"

#

[....]

 

Example traceroute:

traceroute to 2001:500:31::47 (2001:500:31::47), 30 hops max, 80 byte
packets

 1  ...  11.519 ms  17.422 ms  28.084 ms

 2  gige-g2-20.core1.fra1.he.net <http://gige-g2-20.core1.fra1.he.net/>
(2001:470:0:69::1)  45.229 ms  45.216 ms  45.741 ms

 3  10gigabitethernet5-3.core1.lon1.he.net
<http://10gigabitethernet5-3.core1.lon1.he.net/>  (2001:470:0:1d2::1)
58.885 ms  58.871 ms  59.170 ms

 4  10gigabitethernet7-4.core1.nyc4.he.net
<http://10gigabitethernet7-4.core1.nyc4.he.net/>  (2001:470:0:128::1)
134.745 ms  138.270 ms  134.706 ms

 5  10gigabitethernet5-3.core1.lax1.he.net
<http://10gigabitethernet5-3.core1.lax1.he.net/>  (2001:470:0:10e::1)
192.136 ms  192.169 ms  188.694 ms

 6  10gigabitethernet4-2.core3.fmt2.he.net
<http://10gigabitethernet4-2.core3.fmt2.he.net/>  (2001:470:0:18d::1)
198.986 ms  186.827 ms  181.843 ms

 7  10gigabitethernet1-3.core1.fmt2.he.net
<http://10gigabitethernet1-3.core1.fmt2.he.net/>  (2001:470:0:23b::2)
175.135 ms  157.867 ms  157.849 ms

 8  10gigabitethernet1-1.core1.sjc2.he.net
<http://10gigabitethernet1-1.core1.sjc2.he.net/>  (2001:470:0:31::2)
157.421 ms  158.392 ms  157.949 ms

 9  peering.sjc6.arin.net <http://peering.sjc6.arin.net/>
(2001:504:0:1:0:39:3220:1)  153.179 ms  152.843 ms  153.168 ms

10  peering.sjc6.arin.net <http://peering.sjc6.arin.net/>
(2001:504:0:1:0:39:3220:1)  153.119 ms !X  156.999 ms !X  153.701 ms !X

 

_______________________________________________
Outages mailing list
Outages at outages.org
https://puck.nether.net/mailman/listinfo/outages

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/outages-discussion/attachments/20120702/37db97e1/attachment-0001.html>


More information about the Outages-discussion mailing list