Path is not the same, but the last few replies similarly suggest packet-filters (!X in my case vs. !P). I can get to the whois port (TCP/43): $ telnet -6 2001:503:3227:1060::74 whois Trying 2001:503:3227:1060::74... Connected to 2001:503:3227:1060::74. Escape character is '^]'. Can you? Tony On Tue, May 1, 2012 at 8:01 AM, TR Shaw <tshaw@oitc.com> wrote:
Anyone else having problems getting to Verisign's whois server on IPv6?
$ host com.whois-servers.net com.whois-servers.net is an alias for whois.verisign-grs.com. whois.verisign-grs.com has address 199.7.59.74 whois.verisign-grs.com has IPv6 address 2001:503:3227:1060::74
$ traceroute6 2001:503:3227:1060::74 traceroute6 to 2001:503:3227:1060::74 (2001:503:3227:1060::74) from 2001:470:5:4ed:cabc:c8ff:fea1:560c, 64 hops max, 12 byte packets 1 2001:470:5:4ed:226:bbff:fe6d:426e 0.311 ms 0.374 ms 0.260 ms 2 ipv6oitc-1.tunnel.tserv12.mia1.ipv6.he.net 21.128 ms 21.052 ms 17.389 ms 3 gige-g2-3.core1.mia1.he.net 20.055 ms 16.198 ms 22.699 ms 4 10gigabitethernet4-3.core1.atl1.he.net 40.166 ms 33.887 ms 32.547 ms 5 10gigabitethernet6-4.core1.ash1.he.net 49.821 ms 45.999 ms 52.751 ms 6 2001:504:0:2::2641:1 47.197 ms 46.748 ms 47.289 ms 7 xe-1-2-0.r1.bb-fo.chi2.vrsn.net 65.094 ms xe-0-2-0.r2.bb-fo.chi2.vrsn.net 66.441 ms xe-1-2-0.r1.bb-fo.chi2.vrsn.net 66.320 ms 8 2001:503:3227:14ff::2 66.448 ms 2001:503:3227:13ff::2 101.761 ms 86.864 ms 9 2001:503:3227:13ff::2 69.818 ms !P 2001:503:3227:14ff::2 69.311 ms !P 2001:503:3227:13ff::2 68.662 ms !P