NSI again removes services
The ever-changing NICNAMES/whois service once again does not show _ANY_ dates -- creation, update, or database update. Of course the obnoxious and non-legaly-binding statement has moved, now to the top of the response. I sure wish NSI got rid of their lawyers and hired some techies. I sure wish the alternate registries could display this kind of date data. Ehud
At 08:16 AM 10/18/99 -0700, Ehud Gavron wrote:
I sure wish the alternate registries could display this kind of date data.
Ummmm, they do: (apologies in advance for those who are offended by my choice of domains to query, its the only one I *KNEW* was a COREnic entry)
whois fuckme.com@whois.corenic.net [whois.corenic.net] berkens michael (template COCO-395) CORE-78 po box 4756 seminole, fl 33775 US
Domain Name: fuckme.com Status: production Admin Contact, Technical Contact, Zone Contact: berkens michael (COCO-395) worldwm@gte.net +813-267-5600 (FAX) +12345678 CORE Registrar: CORE-78 Record last modified: 1999-08-02 21:47:11 by CORE-78 Record created: 1999-07-09 00:30:30 by CORE-78 Domain servers in listed order: dns1.domainbank.net 205.147.226.162 dns2.domainbank.net 205.147.226.163 Database last updated on 1999-10-18 17:44:00
The ever-changing NICNAMES/whois service once again does not show _ANY_ dates -- creation, update, or database update.
yep. makes sense...they hadn't changed anything for a while.
Of course the obnoxious and non-legaly-binding statement has moved, now to the top of the response.
as of a while ago. in fact...it was between Tue Aug 17 15:22:34 GMT 1999 Tue Aug 17 23:14:49 GMT 1999 i've been archiving all the whois responses i've gotten for a while now (since feb 97) and i can point to things like this rather easily. as for the latest change (the re-removal of some date information), that happened between Sun Oct 17 16:26:16 GMT 1999 Mon Oct 18 13:07:46 GMT 1999 but if all you want is activation date (which is preumably the same as registration data) you can do this: % whois dump merit.edu (gratuitous legal warning deleted) (0) htype: D | (1) handle: MERIT-DOM| ... (5) domainame: MERIT.EDU| ... (10) activation_date: 03-Oct-1986| ... (37) updated: 19990204-220001 autore| ...
I sure wish NSI got rid of their lawyers and hired some techies.
:)
I sure wish the alternate registries could display this kind of date data.
hear hear. -- |-----< "CODE WARRIOR" >-----| codewarrior@daemon.org * "ah! i see you have the internet twofsonet@graffiti.com (Andrew Brown) that goes *ping*!" andrew@crossbar.com * "information is power -- share the wealth."
The ever-changing NICNAMES/whois service once again does not show _ANY_ dates -- creation, update, or database update.
Try "whois dump domainname" I never knew about this until someone pointed it out on another list. It's easier to parse, too. $ whois dump services5-dom The Data in Network Solutions' WHOIS database is provided by Network Solutions for information purposes, and to assist persons in obtaining information about or related to a domain name registration record. Network Solutions does not guarantee its accuracy. By submitting a WHOIS query, you agree that you will use this Data only for lawful purposes and that, under no circumstances will you use this Data to: (1) allow, enable, or otherwise support the transmission of mass unsolicited, commercial advertising or solicitations via e-mail (spam); or (2) enable high volume, automated, electronic processes that apply to Network Solutions (or its systems). Network Solutions reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy. (0) htype: D | (1) handle: SERVICES5-DOM| (2) name: Network Services Clearinghouse| (3) hostname: | (4) netname: | (5) domainame: SERVICES.NET| (6) netaddress: | (7) address: c/o I.E.C.C. PO Box 640 Trumansburg, NY 14886 US| (8) admincontact: HOS228-ORG| (9) alternatepoc: | (10) activation_date: 21-Jan-1997| (11) billcontact: HOS228-ORG| (12) comments: | (13) connectype: | (14) coordinator: | (15) cputype: | (16) groups: | (17) hostadmin: | (18) host: | (19) impname: | (20) impnetnumber: | (21) impnumber: | (22) inaddrserver: | (23) usgpolicy: | (24) mailbox: | (25) netnumber: | (26) netblock: | (27) nicknames: | (28) opsys: | (29) parentdom: NET | (30) phone: | (31) protocols: | (32) servercontact: IVAN-HST LIGHT3-HST| (33) tacid: | (34) mctacnumber: | (35) techcontact: HOS228-ORG| (36) tissuedate: | (37) updated: 19970121-111213 dawnf=| (38) user_name: | (39) validcard: | (40) tacreq: | (41) zonecontact: HOS228-ORG| (42) registrar: | (43) asn_name: | (44) asn_number: | (45) asn_block: | -- John R. Levine, IECC, POB 727, Trumansburg NY 14886 +1 607 387 6869 johnl@iecc.com, Village Trustee and Sewer Commissioner, http://iecc.com/johnl, Member, Provisional board, Coalition Against Unsolicited Commercial E-mail
Wow, this looks like the SRI-era VOID database query result. The impname and tacreq, in particular, look like they did back in the days when SRI was still doing tac cards out of the same database as whois. (TAC cards had user names and passwords which gave dial-up access to a pool of terminal access controllers run by DCA) Ken Harrenstein wrote VOID to serve as the whois database for the SRI-NIC and it had some useful bits that never made it in to later implementations. I've always suspected that this was the influence of augment, one of Doug Engelbart's data storage brainstorms (for the TOPS 2065 platform). One of the useful bits was that you could specify query type by sort algorithm as well as by key. So you got wierd search commands like "li fi boo htype=h and netname=sri-net". (That specified a last in, first out boolean query, which was the most common type.) Sorry if the nostalgia break is off topic for you, Ted Hardie John wrote:
(0) htype: D | (1) handle: SERVICES5-DOM| (2) name: Network Services Clearinghouse| (3) hostname: | (4) netname: | (5) domainame: SERVICES.NET| (6) netaddress: | (7) address: c/o I.E.C.C. PO Box 640 Trumansburg, NY 14886 US| (8) admincontact: HOS228-ORG| (9) alternatepoc: | (10) activation_date: 21-Jan-1997| (11) billcontact: HOS228-ORG| (12) comments: | (13) connectype: | (14) coordinator: | (15) cputype: | (16) groups: | (17) hostadmin: | (18) host: | (19) impname: | (20) impnetnumber: | (21) impnumber: | (22) inaddrserver: | (23) usgpolicy: | (24) mailbox: | (25) netnumber: | (26) netblock: | (27) nicknames: | (28) opsys: | (29) parentdom: NET | (30) phone: | (31) protocols: | (32) servercontact: IVAN-HST LIGHT3-HST| (33) tacid: | (34) mctacnumber: | (35) techcontact: HOS228-ORG| (36) tissuedate: | (37) updated: 19970121-111213 dawnf=| (38) user_name: | (39) validcard: | (40) tacreq: | (41) zonecontact: HOS228-ORG| (42) registrar: | (43) asn_name: | (44) asn_number: | (45) asn_block: | -- John R. Levine, IECC, POB 727, Trumansburg NY 14886 +1 607 387 6869 johnl@iecc.com, Village Trustee and Sewer Commissioner, http://iecc.com/johnl, Member, Provisional board, Coalition Against Unsolicited Commercial E-mail
"John R. Levine" wrote:
Try "whois dump domainname"
I've found that not all whois clients pass all the options onto the whois server. Additionally, you may not want to rely on another client from within a script...especially if you're trying to straighten out your SWIPs for that last /14 assigned to you. One option would be to connect to the server's whois TCP port 43 and send your commands. You can use the "DOmain" keyword to search only the domain record type when there's a possibility of the domain being a host as well. Example: telnet whois.internic.net 43 dump do yahoo.com The Data in Network Solutions' WHOIS database is provided by Network Solutions for information purposes, and to assist persons in obtaining information about or related to a domain name registration record. Network Solutions does not guarantee its accuracy. By submitting a WHOIS query, you agree that you will use this Data only for lawful purposes and that, under no circumstances will you use this Data to: (1) allow, enable, or otherwise support the transmission of mass unsolicited, commercial advertising or solicitations via e-mail (spam); or (2) enable high volume, automated, electronic processes that apply to Network Solutions (or its systems). Network Solutions reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy. (0) htype: D | (1) handle: YAHOO-DOM| (2) name: Yahoo| (3) hostname: | (4) netname: | (5) domainame: YAHOO.COM| (6) netaddress: | (7) address: 3400 Central Expressway, Suite 201 Santa Clara, CA 95051| (8) admincontact: JPH17 | (9) alternatepoc: | (10) activation_date: 18-Jan-1995| (11) billcontact: JPH17| (12) comments: | (13) connectype: | (14) coordinator: | (15) cputype: | (16) groups: | (17) hostadmin: | (18) host: | (19) impname: | (20) impnetnumber: | (21) impnumber: | (22) inaddrserver: | (23) usgpolicy: | (24) mailbox: | (25) netnumber: | (26) netblock: | (27) nicknames: | (28) opsys: | (29) parentdom: COM | (30) phone: | (31) protocols: | (32) servercontact: NS50746-HST NS50747-HST NS73110-HST NS27120-HST| (33) tacid: | (34) mctacnumber: | (35) techcontact: JPH17 | (36) Connection closed by foreign host. Louie
On Wed, 20 Oct 1999, Louis Lee wrote:
"John R. Levine" wrote:
Try "whois dump domainname"
I've found that not all whois clients pass all the options onto the whois server. Additionally, you may not want to rely on another client from within a script...especially if you're trying to straighten out your SWIPs for that last /14 assigned to you.
My machines generally come with fwhois, which wants it in the format 'whois $domain@$server'...As you suggest, sending the commands straight to the TCP port takes care of that. FWIF, NSI seem to have reinstated the date information. The impression I got from our account manager was that a lot of people had been bending his ear over that one :) -- Patrick Evans - Sysadmin, caffeine addict and beat poet pre at pre dot org www.pre.org/pre I have opinions. I'm allowed to. You don't. You're not.
[ On Wednesday, October 20, 1999 at 17:30:11 (+0100), Patrick Evans wrote: ]
Subject: Re: NSI again removes services
My machines generally come with fwhois, which wants it in the format 'whois $domain@$server'...As you suggest, sending the commands straight to the TCP port takes care of that.
Isn't that "fwhois <domain>@<server>" ? :-) ----^ I think the inventor of fwhois should have nasty things done to the arguments of every command he ever types again! You can still get the *real* whois client from most any *BSD, or from the InterNIC ftp site. You can also find the much more advanced RIPE version too (of which a slightly modified version is now in NetBSD-current too). ftp://rs.internic.net/netprog/whois.c ftp://ftp.ripe.net/tools/ripe-whois-tools-2.4.tar.gz However wouldn't just quoting the so-called "domain" portion make a multi-word query like that work with fwhois? -- Greg A. Woods +1 416 218-0098 VE3TCP <gwoods@acm.org> <robohack!woods> Planix, Inc. <woods@planix.com>; Secrets of the Weird <woods@weird.com>
On Wed, 20 Oct 1999, Greg A. Woods wrote: | I think the inventor of fwhois should have nasty things done to the | arguments of every command he ever types again! | The fact that several widely used Linux distributions still have this ancient, broken program that I cobbled together from old finger source code nearly 8 years ago should speak for itself ;) | You can still get the *real* whois client from most any *BSD, or from | the InterNIC ftp site. You can also find the much more advanced RIPE | version too (of which a slightly modified version is now in | NetBSD-current too). | | ftp://rs.internic.net/netprog/whois.c | ftp://ftp.ripe.net/tools/ripe-whois-tools-2.4.tar.gz | | However wouldn't just quoting the so-called "domain" portion make a | multi-word query like that work with fwhois? Yes
[ On Wednesday, October 20, 1999 at 14:14:12 (-0700), Chris Cappuccio wrote: ]
Subject: Re: NSI again removes services
The fact that several widely used Linux distributions still have this ancient, broken program that I cobbled together from old finger source code nearly 8 years ago should speak for itself ;)
*Eight* years old! Even the latest version of the real whois isn't quite that old yet! ;-) I had no idea! Congratulations at least for having your code survive for that long. That might also explain why I wasn't able to find a canonical distribution site for the source code. Sometimes I wonder about the tastes of some of those who make up Linux distributions. Other times I wonder whether or not they've just got a hate on for anything from *BSD! :-) (Oh how I pine for the idea of a single distributed rwhois-style database where a simple query would always find the answer no matter who's whois data it was!) -- Greg A. Woods +1 416 218-0098 VE3TCP <gwoods@acm.org> <robohack!woods> Planix, Inc. <woods@planix.com>; Secrets of the Weird <woods@weird.com>
On Wed, 20 Oct 1999, Greg A. Woods wrote: | [ On Wednesday, October 20, 1999 at 14:14:12 (-0700), Chris Cappuccio wrote: ] | > Subject: Re: NSI again removes services | > | > The fact that several widely used Linux distributions still have this | > ancient, broken program that I cobbled together from old finger source code | > nearly 8 years ago should speak for itself ;) | | *Eight* years old! Even the latest version of the real whois isn't | quite that old yet! ;-) I had no idea! Congratulations at least for | having your code survive for that long. That might also explain why I | wasn't able to find a canonical distribution site for the source code. | Well, 7 or 8 years i don't remember 1992 ?? There certainly was a whois.c from the pre-internic days and it didn't compile on Linux, hence the need for fwhois ;) | Sometimes I wonder about the tastes of some of those who make up Linux | distributions. Other times I wonder whether or not they've just got a | hate on for anything from *BSD! :-) | IMHO it's lack of attention to detail | (Oh how I pine for the idea of a single distributed rwhois-style | database where a simple query would always find the answer no matter | who's whois data it was!) | geektools.com ?? There are several unofficial services that do this sort of thing
[ On Wednesday, October 20, 1999 at 17:03:08 (-0700), Chris Cappuccio wrote: ]
Subject: Re: NSI again removes services
geektools.com ??
There are several unofficial services that do this sort of thing
I very much prefer my own hack (which does not yet work with fwhois): ftp://ftp.weird.com/pub/local/awhois.sh :-) (up to version 1.43 now -- constantly changing for a Net that never sleeps!) -- Greg A. Woods +1 416 218-0098 VE3TCP <gwoods@acm.org> <robohack!woods> Planix, Inc. <woods@planix.com>; Secrets of the Weird <woods@weird.com>
I'm unable to get a response from NSI's whois server nor their web site. Are they really dead, or is there just a network black hole between me and them? -- John R. Levine, IECC, POB 727, Trumansburg NY 14886 +1 607 387 6869 johnl@iecc.com, Village Trustee and Sewer Commissioner, http://iecc.com/johnl, Member, Provisional board, Coalition Against Unsolicited Commercial E-mail
I was having some problems earily as well, but traceroutes were fine. I think they just had a hiccup in their system. -- James Smith, CCNA Network/System Administrator DXSTORM.COM http://www.dxstorm.com/ DXSTORM Inc. 2140 Winston Park Drive, Suite 203 Oakville, ON, CA L6H 5V5 Tel: 905-829-3389 Fax: 905-829-5692 1-877-DXSTORM (1-877-397-8676) On 21 Oct 1999, John R. Levine wrote:
I'm unable to get a response from NSI's whois server nor their web site.
Are they really dead, or is there just a network black hole between me and them?
-- John R. Levine, IECC, POB 727, Trumansburg NY 14886 +1 607 387 6869 johnl@iecc.com, Village Trustee and Sewer Commissioner, http://iecc.com/johnl, Member, Provisional board, Coalition Against Unsolicited Commercial E-mail
However wouldn't just quoting the so-called "domain" portion make a multi-word query like that work with fwhois?
Yes, although this isn't obvious given that fwhois is usually provided without documentation. -- Nick Bastin - Valkyrie Internet, Inc. The idea that Bill Gates has appeared like a knight in shining armour to lead all customers out of a mire of technological chaos neatly ignores the fact that it was he who, by peddling second-rate technology, led them into it in the first place. - Douglas Adams
I am currently writing a 3 tier client-server whois package at www.dnso.net/projects. At the moment, only the client works. It is based on the whois.c code from Richard Sexton <richard@vrx.net>. The new code is a virtual re-write and will include a whois application server as well as a whoisd server. The back-end is intended to be SQL92 and the source release will include the schema DDL. It's a pretty big project and I could use some help. Release will be open-source GPL, of course.
-----Original Message----- From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu]On Behalf Of Greg A. Woods Sent: Wednesday, October 20, 1999 1:58 PM To: nanog@merit.edu Subject: Re: NSI again removes services
[ On Wednesday, October 20, 1999 at 17:30:11 (+0100), Patrick Evans wrote: ]
Subject: Re: NSI again removes services
My machines generally come with fwhois, which wants it in the format 'whois $domain@$server'...As you suggest, sending the commands straight to the TCP port takes care of that.
Isn't that "fwhois <domain>@<server>" ? :-) ----^
I think the inventor of fwhois should have nasty things done to the arguments of every command he ever types again!
You can still get the *real* whois client from most any *BSD, or from the InterNIC ftp site. You can also find the much more advanced RIPE version too (of which a slightly modified version is now in NetBSD-current too).
ftp://rs.internic.net/netprog/whois.c ftp://ftp.ripe.net/tools/ripe-whois-tools-2.4.tar.gz
However wouldn't just quoting the so-called "domain" portion make a multi-word query like that work with fwhois?
-- Greg A. Woods
+1 416 218-0098 VE3TCP <gwoods@acm.org> <robohack!woods> Planix, Inc. <woods@planix.com>; Secrets of the Weird <woods@weird.com>
participants (12)
-
Andrew Brown -
Chris Cappuccio -
Derek Balling -
Ehud Gavron -
hardie＠equinix.com -
James Smith -
johnl＠iecc.com -
Louis Lee -
Nick Bastin -
Patrick Evans -
Roeland M.J. Meyer -
woods＠most.weird.com