This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[db-wg] IPv6 Whois update
- Previous message (by thread): [db-wg] Organisation object proposal
- Next message (by thread): [db-wg] IPv6 Whois update
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Shane Kerr
shane at ripe.net
Thu Jan 23 18:30:29 CET 2003
Colleagues, As you may have seen on the list, there were a few reachability problems with the new IPv6 Whois service. We believe these are configuration related, and have a workaround allowing queries to WHOIS.RIPE.NET to work while we research it further. If you have network issues with this service please e-mail <ripe-dbm at ripe.net>. We also have heard some problems people are having with their Whois clients giving them errors querying the RIPE Whois server. These can occur in the case that: - The Whois client has IPv6 support. - The host computer does not have working IPv6 support. The client will: 1. Get the AAAA record for WHOIS.RIPE.NET. 2. Try to connect to the IPv6 address. 3. Fail because there is no IPv6 stack/address/router/etc. If you are experiencing this problem, you may be able to fix it by enabling IPv6 on your host (so that the IPv6 queries work), disabling IPv6 *completely* on your host (so that no AAAA records are returned), or by using another Whois client. The RIPE Whois client will work in this case, and is available from our FTP site: ftp://ftp.ripe.net/tools/ripe-whois-latest.tar.gz -- Shane Kerr RIPE NCC
- Previous message (by thread): [db-wg] Organisation object proposal
- Next message (by thread): [db-wg] IPv6 Whois update
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]