North American Network Operators Group
Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: Correct inclusion of rwhois info in WHOIS server output?

  • From: Suresh Ramasubramanian
  • Date: Sun Sep 11 02:05:41 2005
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=cG8W6xXtlQMdftoMgKCFxqwzGJHUReDe6YHPeeZ+fGPjeiSYMlwVyLDyve/xFpiErnpyhk6FvT16NvUo1k96nO2tHQsaWEZz74WEFAwkSGYW1iWoSPMmdf8P7imQioW98KVCgr1iwbIksKEZTOxe4j0d02vjL59tpjmhFxP4HKU=
Marco d'Itri's whois client does quite a lot of what you want,
including automatically following an rwhois referral when it finds one

Of course not much can be done when the rwhois server to which you're
redirected just doesn't respond

[email protected] 11:33:29 <~> $ telnet  rwhois.level3.net 4321
Trying 209.244.1.179...

srs

On 09/09/05, Albert Meyer <[email protected]> wrote:
> 
> Thanks to everyone who replied on and off-list. I'm concluding that there is a
> problem with WHOIS server output, caused mostly by a lack of standards, but
> people with more influence than me are already working on fixing that. In the
> meantime I'll see if I talk to the gnu maintainer about making jwhois more
> rwhois-friendly.
> 


-- 
Suresh Ramasubramanian ([email protected])