Received the following tracking number from verisign.
--
Si Dieu existe, j'espère qu'Il a une excuse valable
- Daniel Pennac--- Begin Message ---Dear Antoine, Thank you for contacting Verisign Support. We are reviewing your inquiry. We will contact you once we have an update. If you have additional questions, please do not hesitate to contact us. Best Regards, Henry Customer Service VeriSign, Inc. www.verisigninc.com 1 703.925.6999 1 703.948.3978 Fax --------------- Original Message --------------- From: Antoine Beaupré [anar...@debian.org] Sent: 3/2/2013 12:27 PM To: sub...@bugs.debian.org Subject: Bug#702095: .net server timeout with IPv6 Package: whois Version: 5.0.20 Severity: normal It seems that the whois server for .net (whois.verisign-grs.com) and other domains, is timing out when reached over IPv6: $ env LANG=C LC_ALL=C whois -h whois.verisign-grs.com koumbit.net 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. Timeout. The host is reachable over IPv6, and indeed the boilerplate is actually a response from the server over the TCP socket. $ ping6 whois.verisign-grs.com PING whois.verisign-grs.com (2001:503:5ae2:1060::74): 48 data bytes 56 bytes from whois.crsnic.net: icmp_seq=0 ttl=52 time=105.670 ms 56 bytes from whois.crsnic.net: icmp_seq=1 ttl=52 time=100.985 ms 56 bytes from whois.crsnic.net: icmp_seq=2 ttl=52 time=100.560 ms 56 bytes from whois.crsnic.net: icmp_seq=3 ttl=52 time=100.925 ms 56 bytes from whois.crsnic.net: icmp_seq=4 ttl=52 time=101.225 ms 56 bytes from whois.crsnic.net: icmp_seq=5 ttl=52 time=100.315 ms ^C--- whois.verisign-grs.com ping statistics --- 6 packets transmitted, 6 packets received, 0% packet loss round-trip min/avg/max/stddev = 100.315/101.613/105.670/1.838 ms I have found a discussion here mentionning the same problem, with a workaround: http://www.tunnelbroker.net/forums/index.php?topic=2400.0 The workaround, to hardcode IPv4 addresses in whois.conf, works here. One simply needs to add the following to /etc/whois.conf: \.com$ 199.7.57.74 \.net$ 199.7.57.74 \.edu$ 199.7.57.74 \.cc$ 199.7.57.74 \.tv$ 199.7.57.74 \.name$ 199.7.57.74 \.jobs$ 199.7.57.74 (https://www.verisigninc.com/en_US/products-and-services/register-domain-names/whois/index.xhtml) ...or pass the server IP on the commandline: anarcat@marcos:~$ whois -h 199.7.57.74 koumbit.net 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. Domain Name: KOUMBIT.NET [...] Now, this is probably a problem more with Verisign, but we could still implement a (temporary?) workaround here. -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to fr_CA.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages whois depends on: ii libc6 2.13-37 ii libidn11 1.25-2 whois recommends no packages. whois suggests no packages. -- no debconf information ref:_00DA0Zmyt._500A0D8nHJ:ref
--- End Message ---
pgpIxmE8p7e6m.pgp
Description: PGP signature
