[ipv6-wg@ripe.net] IPV6 Whois
[apologies for duplicate messages] Dear Colleagues, We are happy to announce the availability of RIPE Whois servers on IPv6 network. It is now possible to query whois.ripe.net and test-whois.ripe.net from an IPv6 host, using an IPv6 enabled whois client. If your system doesn't already have one, you can find the latest RIPE Whois client at: ftp://ftp.ripe.net/ripe/tools/ripe-whois-latest.tar.gz You can read the full anouncement at: http://www.ripe.net/ripencc/pub-services/db/whois-ipv6.html Best regards, -- Can Bican Database Group RIPE NCC
| We are happy to announce the availability of RIPE Whois servers on IPv6 | network. It is now possible to query whois.ripe.net and test-whois.ripe.net | from an IPv6 host, using an IPv6 enabled whois client. If your system doesn't | already have one, you can find the latest RIPE Whois client at: Hi Can, I cannot reach the server from AS12859, nor from AS8954. --- whois.ripe.net ping6 statistics --- 2 packets transmitted, 0 packets received, 100% packet loss A traceroute from me (2001:7b8:3:17:202:b3ff:fe10:d926) to you gives: 1 dapje-gw.ipv6.network.bit.nl 0.383 ms 0.286 ms 0.269 ms 2 jun1.telecity.ipv6.network.bit.nl 1.537 ms 1.552 ms 1.505 ms 3 nikipv6.ripe.net 3.378 ms 3.035 ms 3.111 ms 4 nikipv6.ripe.net 4.432 ms !P 3.248 ms !P 3.288 ms !P And telnetting to port 43 of whois.ripe.net does not do much: $ telnet 2001:610:240:0:193::135 whois Trying 2001:610:240:0:193::135... ^C Please advise. -- ---------- - - - - -+- - - - - ---------- Pim van Pelt Email: pim@ipng.nl http://www.ipng.nl/ IPv6 Deployment -----------------------------------------------
hi, On Thu, Jan 23, 2003 at 03:17:03PM +0100, Pim van Pelt wrote:
I cannot reach the server from AS12859, nor from AS8954.
Reachability from 5539 is intermittant. Sometimes the ping works fine for 1000 packets, and then it's back to "non-working" (pinging from 2001:608:0:1::100). Telnet to port 43 mostly works, but connection establishment takes an amazingly long time. Something like "20 seconds" for my last try. Maybe routing was still converging. Seems to be stable right now. Gert Doering -- NetMaster -- Total number of prefixes smaller than registry allocations: 55857 (55593) SpaceNet AG Mail: netmaster@Space.Net Joseph-Dollinger-Bogen 14 Tel : +49-89-32356-0 80807 Muenchen Fax : +49-89-32356-299
It is a nice idea to make the RIPE Whois service available over IPv6, thanks! One question/suggestion: Could the CLIENTADDRESS referral method be upgraded to support IPv6? We have a Whois server that is referred-to from RIPE's (for *.ch), and that uses CLIENTADDRESS for access control. When I access it through the RIPE server from IPv6, our server sees the IPv4 address "10.0.0.169" instead of the client address. This is probably better than if IPv6 client addresses would suddenly start to be passed to unsuspecting Whois servers... so maybe a new version of CLIENTADDRESS ("CLIENTV4ORV6ADDRESS"?) would be in order. We would be happy to move to this new referral method (and could also make our own Whois server IPv6-capable). As it stands, IPv6-capable clients that query .ch domain names through www.switch.ch are now denied service, because our Whois daemon refuses to serve clients with RFC1918 addresses. -- Simon Leinen simon@babar.switch.ch SWITCH http://www.switch.ch/network/
Oops, there was a typo in my last message:
As it stands, IPv6-capable clients that query .ch domain names through www.switch.ch are now denied service, because our Whois daemon refuses ^^^^^^^^^^^^^ whois.ripe.net
to serve clients with RFC1918 addresses. -- Simon.
participants (4)
-
DB-News -
Gert Doering -
Pim van Pelt -
Simon Leinen