Your message dated Fri, 1 Aug 2008 01:42:39 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#493083: $WHOIS_SERVER doesn't always come into effect
has caused the Debian Bug report #493083,
regarding $WHOIS_SERVER doesn't always come into effect
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
493083: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=493083
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: whois
Severity: minor
Version: 4.7.27
I'm working for an European-based LIR and would therefore like all queries
go to RIPE's database unless it is certain that the information I'm looking
for is somewhere else. I tried to set $WHOIS_SERVER to "whois.ripe.net" to
achieve that, but it doesn't always work. For instance:
$ whois "Tore Anderson"
No whois server is known for this kind of object.
$ WHOIS_SERVER=whois.ripe.net whois "Tore Anderson"
No whois server is known for this kind of object.
According to the manual page, if $WHOIS_SERVER is set it should be queried
if «the progrem cannot guess where some kind of objects are located»,
which appears to be the case here. But it doesn't work, and it doesn't
default to sending these unknown queries to whois.arin.net when
$WHOIS_SERVER is unset either, as it says in the manual page. The same
thing happens if I search for a unassigned IP network, for instance
"254.0.0.1".
This works as expected, though:
$ whois -h whois.ripe.net "Tore Anderson"
There are some searches where I've noticed that the $WHOIS_SERVER /
whois.arin.net fallback appears to work as documented, for instance
"PGPKEY-E68858D1" which goes to whois.arin.net if $WHOIS_SERVER is unset,
or to $WHOIS_SERVER (if set).
Best regards,
--
Tore Anderson
--- End Message ---
--- Begin Message ---
On Jul 31, Tore Anderson <[EMAIL PROTECTED]> wrote:
> $ whois "Tore Anderson"
> According to the manual page, if $WHOIS_SERVER is set it should be queried
> if «the progrem cannot guess where some kind of objects are located»,
> which appears to be the case here. But it doesn't work, and it doesn't
> default to sending these unknown queries to whois.arin.net when
> $WHOIS_SERVER is unset either, as it says in the manual page. The same
> thing happens if I search for a unassigned IP network, for instance
> "254.0.0.1".
Read that more carefully, and you will undertand why it's working as
designed: "Tore Anderson" is an unknown kind of object, not an object
which is known but whose location is not in the database.
254.0.0.1 is a *reserved* IP address, not an unassigned one which will
be allocated later. Big difference.
It could be argued that full text searches like this one should be
assimilated to nic handle searches, but they are hard enough to reliably
detect that I do not believe it's worth the effort (considering that
this kind of searches are highly deprecated since they may have
non-unique results and cannot use indexes).
> There are some searches where I've noticed that the $WHOIS_SERVER /
> whois.arin.net fallback appears to work as documented, for instance
> "PGPKEY-E68858D1" which goes to whois.arin.net if $WHOIS_SERVER is unset,
> or to $WHOIS_SERVER (if set).
Actually this one *is* a bug, PGPKEY-* objects are being mistaken for
NIC handles. I fixed this in the next release.
--
ciao,
Marco
signature.asc
Description: Digital signature
--- End Message ---
