Can't reach RIPE WHOIS via IPv6 ?

Mailman List Mirror (Read Only)
1

(I realize RIPE is not in North America, but we get a lot of traffic
from their IP space.)

When I try to contact whois.ripe.net (2001:67c:2e8:22::c100:687) or
their REST server rest.db.ripe.net (2001:67c:2e8:22::c100:68e), it
times out. Traceroutes from a couple of different places all seem to
loop in Amsterdam, IPv4 is fine.

Am I special, or is it just broken?

R's,
John

2

* johnl@iecc.com (John Levine) [Thu 10 Sep 2015, 19:09 CEST]:

When I try to contact whois.ripe.net (2001:67c:2e8:22::c100:687) or their REST server rest.db.ripe.net (2001:67c:2e8:22::c100:68e), it times out. Traceroutes from a couple of different places all seem to loop in Amsterdam, IPv4 is fine.

Am I special, or is it just broken?

WFM

% telnet whois.ripe.net whois
Trying 2001:67c:2e8:22::c100:687...
Connected to whois.ripe.net.

  -- Niels.

3

Hi,

4

Same for me from 2a01:d0::/32

telnet whois.ripe.net whois
Trying 2001:67c:2e8:22::c100:687...
Connected to whois.ripe.net.
Escape character is '^]'.
% This is the RIPE Database query service.
% The objects are in RPSL format.
%
% The RIPE Database is subject to Terms and Conditions.
% See http://www.ripe.net/db/support/db-terms-conditions.pdf

Seems like local routing issue, not global.

5

When I try to contact whois.ripe.net (2001:67c:2e8:22::c100:687) or
their REST server rest.db.ripe.net (2001:67c:2e8:22::c100:68e), it
times out. Traceroutes from a couple of different places all seem to
loop in Amsterdam, IPv4 is fine.

Am I special, or is it just broken?

I guess I was special. Seems to work OK now.

R's,
John