Bug 15221 - whois is not very useful
Summary: whois is not very useful
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: whois
Version: 8.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Nalin Dahyabhai
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: FC3BugWeekTracker
TreeView+ depends on / blocked
 
Reported: 2000-08-03 11:45 UTC by Per Steinar Iversen
Modified: 2007-04-18 16:27 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2004-09-27 21:41:09 UTC
Embargoed:


Attachments (Terms of Use)

Description Per Steinar Iversen 2000-08-03 11:45:17 UTC
The whois which has been used for a long time by RedHat is not
very useful any more, it does not understand the referrals now common.
It is also not very useful for domains outside the generic ones.

A very good replacement can be found:

http://www.linux.it/~md/software/http://www.linux.it/~md/software/

Try to find the whois information for hio.no for example with the standard
whois client and then with this one...

Comment 1 Nalin Dahyabhai 2000-08-04 06:12:56 UTC
The whois client does follow referrals, but none are given by the default whois
servers.

Comment 2 Tim Waugh 2000-09-26 11:46:46 UTC
How do other whois clients 'just work' then?  For example, 'whois macworld.se'
on FreeBSD 'just works' (it uses whois.nic-se.se).


Comment 3 Need Real Name 2002-12-07 06:14:26 UTC
See Bug ID 59872 which I filed in February, 2002.  
  
This is still a problem with Red Hat 8.0.  'whois' in its current state is  
pitiful.  
  
Thanks.

Comment 4 Alan Cox 2002-12-15 00:38:35 UTC
The BSD one knows how to parse all the crap. We should update to it


Comment 5 Hugo van der Kooij 2002-12-22 20:56:03 UTC
You can find better whois clients packaged and all on:
http://rpmfind.net/linux/rpm2html/search.php?query=whois&submit=Search+...

Comment 6 Rik van Riel 2004-09-27 21:41:09 UTC
We've been shipping jwhois for quite a while now.  Time to close this
bug. ;)


Note You need to log in before you can comment on or make changes to this bug.