You know, if I remember right, the whois-servers.net domain still works- so if you just use:
<ext>.whois-servers.net as your whois server, it should work for (probably) almost all extensions. ie: whois -h ca.whois-servers.net mrhost.ca and along Lynn's lines, you could open a socket connection to "ca.whois-servers.net" and pass the domain, and read the output. Like she said, you can test this by telneting to "ca.whois-servers.net" on port 43 (whois port) and just type in the domain. Yes it relies on this domain to work, but it keeps you from having to build a list of ext => whois server Just my $0.02 Mike Pultz [EMAIL PROTECTED] > Amit Rana wrote: > >> It wasn't so much a suggestion for your whois, as a suggestion > >> that using someone elses tool will ultimately lead to > >> dissapointment. > > > > Have you tried jwhois? > > Oh, for Pete's sake. Lynn was (pretty clearly) trying to point out that > the programming required to build your OWN tool is essentially trivial, > and if you build your own, then the only person you must rely on for it > to be up-to-date is yourself...someone who you might reasonably be > expected to have more control over than, oh, I don't know, ANYBODY ELSE. > > The "Have you tried Brand X?" type of questions completely ignore the > point that Lynn was making. > > Regards, > Eric Longman > Atl-Connect Internet Services > > +-------------------------------------------------------+ > | Atl-Connect Internet Services http://www.atlcon.net | > | 3600 Dallas Hwy Ste 230-288 770 590-0888 | > | Marietta, GA 30064-1685 [EMAIL PROTECTED] | > +-------------------------------------------------------+
