whois.internic.net / whois.crsnic.net IPv6 timeouts
sfrost at snowman.net
Wed Jul 10 19:52:35 UTC 2013
* Robert L Mathews (lists at tigertech.com) wrote:
> These work for me on multiple IPv6 carriers, using both the Mac OS X and
> Debian squeeze whois clients:
> Perhaps your WHOIS client is choking on the first type of response
> without the "="? WHOIS should work fine via telnet to eliminate possible
> WHOIS client issues; you can just:
It's Ubuntu 13.04's 5.0.20ubuntu1 client, so it really shouldn't be much
different from the Debian whois you're using.
Also, whois -h 188.8.131.52 networksolutions.com works just fine (and
includes the blurb).
> $ telnet 2001:503:5ae2:1060::74 43
> ... and type "=networksolutions.com" to get the raw response.
Doing this results in it just hanging, similar to with the whois client:
sfrost at tamriel:/home/sfrost> telnet 2001:503:5ae2:1060::74 43
Connected to 2001:503:5ae2:1060::74.
Escape character is '^]'.
Whois Server Version 2.0
Domain names in the .com and .net domains can now be registered
with many different competing registrars. Go to http://www.internic.net
for detailed information.
[... hanging here, still ...]
> > Anyone from NetSol care?
> Network Solutions hasn't been involved with the running of
> whois.internic.net and whois.crsnic.net for many years. They're
> currently run by VeriSign Global Registry Services.
Ah, yea, good point. :)
> > there's a Debian bug #683187 which mentions similar issues from
> > nearly a year ago..).
> Right, but other people couldn't duplicate it. I suspect VeriSign uses
> rate-limiting; is it possible that your source IP address is just being
It usually tells you that, actually, and so I doubt that's the case.
Also, attempting from other IPv6 addresses results in the same hang
(even with the telnet approach).
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 198 bytes
Desc: Digital signature
More information about the NANOG