.ORG Registrar ID List (was: Stupid .org registry code change)
Mike, You should deal with a registrar for this information, since that is one of the services they can provide for you. If you are interested in the cross-reference list, please see http://www.pir.org/whois_search/registrar_whois_ids, which can be accessed via the link at http://www.pir.org/whois_search/. In addition, if you choose to use the web-based whois, then you can use the link on the whois output for the registrar - so for example, the domain nanog.org is at http://www.pir.org/cgi-bin/whois.cgi?yes_popup_flag=0&whois_query_field= domain+NANOG.ORG, and using the link for Sponsoring Registrar, in this example "NSI(R63-LROR)" will give information on how to reach the registrar - see http://www.pir.org/cgi-bin/whois.cgi?yes_popup_flag=0&whois_query_field= registrar+id+R63-LROR. I will pass on your offer of career advice ;-) Regards, Bruce Bruce W. Beckwith VP, Operations Public Interest Registry 1775 Wiehle Avenue Suite 102A Reston, VA 20190 v: +1 703.464.7005 x105 bbeckwith@pir.org -----Original Message----- From: Michael Lewinski [mailto:mike@rockynet.com] Sent: Monday, December 22, 2003 6:19 PM To: nanog@nanog.org Subject: Stupid .org registry code change During the recent changes to .org, whois stopped being useful for what I need.
Sponsoring Registrar:R11-LROR
All I really want to know is the Registrar's name/URL to tell my client so they can modify their nameservers. Does anyone have: 1) A URL to the table that will allow me to lookup a name from the above code (or better, a hack to whois that will do said lookup for me)? 2) The e-mail address where I should my suggestion that the person who came up with this brilliant scheme needs to pursue a new career in a non-IT related field? TIA, Mike
Bruce Beckwith wrote:
You should deal with a registrar for this information, since that is one of the services they can provide for you.
Right, but in a case where my client inherited a domain from their predecessor, and has no idea who their registrar is, I seem to be in a catch-22.... This was my purpose in issuing a whois query to begin with- to learn which registrar they need to contact to make DNS authority changes. OTOH, if you are suggesting that I should contact *my* registrar of choice to obtain this information... this seems more than a little ridiculous (to me at least, and I suspect OpenSRS is not going to appreciate getting a new support ticket every time I want to do a whois to figure out what other registrar has a domain that my client doesn't even intend to transfer to them). Why should I {e-mail|call} to get what used to be available with a simple whois query? What have we gained by making this process even more complicated? I have no beef with the use of Registrar IDs, I'm sure there are benefits to using them. But I do think that they are a poor substitute for what used to be human-readable information.
Thanks, but again this seems unnecessarily complicated. Why can't your whois server do this for me as .com/.net are, and .org used to be? I.E. $ whois rockynet.com Whois Server Version 1.3 Domain names in the .com and .net domains can now be registered with many different competing registrars. Go to http://www.internic.net for detailed information. Domain Name: ROCKYNET.COM Registrar: TUCOWS, INC. <- This is all I really need Whois Server: whois.opensrs.net <- but this is helpful too Referral URL: http://www.opensrs.org <- this is icing on the cake :) At the very least, I think it's only reasonable for the pir.org whois server to provide some basic help text on where to get more information, i.e. as Tim Wilde pointed out: For more information do a 'whois -h whois.pir.org "registrar id r11-lror"' If I knew a bit more C, I'd hack my copy of whois to do this for me automagically. For now I guess I'll live with having to do two whois queries to get the information I need (I'm stubborn and would rather not use the web-based whois, since I'm already in the shell for the corresponding digs and named configuration- that's what I liked about whois, it was a nice general purpose tool that could tell me certain things about any domain with one simple query). Mike
On Mon, 22 Dec 2003, Mike Lewinski wrote:
Actually your registrar of choice should be able to easily get this information. However if your registrar is just doing things to keep prices as low as possible then they probably won't appreciate being asked to do this sort of thing (there is a reason to use the more expensive registrars).
Why should I {e-mail|call} to get what used to be available with a simple whois query?
Is there a standard for a whois query? If not you are kind of screwed. You have just been relying on things staying the same and been "lucky" so far that they haven't changed much.
This I agree with. However for my .org domain and a couple of others I work with (that are at different registrars) all have the same outputs if you use "whois -h whois.pir.org domainname.org". Different registrars at the .com/.net level have different outputs so I can't see where this would be a difficult problem. bye, ken emery
On Mon, 22 Dec 2003, Mike Lewinski wrote:
Your wish is my command :) I've had this sublookup feature in the completewhois test code for next version for several months, but did not think it was usefull being released on its own. Most of the new code for creating "summary portion" of domain whois is now ready, so I'll release it week earlier then planned as a christmas/hanukkah holiday gift, happy holidays! Note: Currently supported by new code are .com/.net/.org/.info/.biz/.us/.cc/.la In the future all country tlds and other main tlds will also have similar crsnic-like summary created at the top with nameservers taken from dns zone and rest of the info from internal pre-defined info for that tld or from whois [root@sokol /]# whois -h completewhois.com nanog.org [completewhois.com] Elan Completewhois.Com Whois Server, Version 0.91a2, compiled on Dec 22, 2003 Please see http://www.completewhois.com/help.htm for command-line options Use of this server and any information obtained here is allowed only if you follor our policies at http://www.completewhois.com/policies.htm [DOMAIN whois information on NANOG.ORG ] [Query Origin: Main Whois Query f Domain Name: NANOG.ORG Namespace: ICANN General Use Top Level Domain - http://www.icann.org TLD Info: http://www.iana.org/root-whois/org.htm Registry: Public Interest Registry - http://www.pir.org Registrar: Network Solutions Inc. Registrar - http://www.networksolutions.com Whois Server: whois.publicinterestregistry.net Name Server[with whois ip]: DNS3.MERIT.NET 198.108.130.5 Name Server[with whois ip]: DNS2.MERIT.NET 198.109.36.3 Name Server[with whois ip]: DNS.MERIT.NET 198.108.1.42 Status: : OK Creation Date: 21-Jul-1996 04:00:00 UTC Updated Date: 24-Sep-2003 21:05:21 UTC Expiration Date: 20-Jul-2006 04:00:00 UTC [whois.publicinterestregistry.net] Domain ID: D938727-LROR Domain Name: NANOG.ORG Created On: 21-Jul-1996 04:00:00 UTC Last Updated On: 24-Sep-2003 21:05:21 UTC Expiration Date: 20-Jul-2006 04:00:00 UTC Sponsoring Registrar: R63-LROR Status: OK Registrant ID: 5459322-NSI Registrant Name: Merit Network Inc. Registrant Organization: Merit Network Inc. Registrant Street1: 4251 Plymouth Road Registrant Street2: Bldg. 1, Suite 2000 Registrant City: Ann Arbor Registrant State/Province: MI Registrant Postal Code: 48105-2785 Registrant Country: US Registrant Email: domain-admin@merit.edu Admin ID: 15617431-NSI Admin Name: Merit Network Inc. Admin Organization: Merit Network Inc. Admin Street1: 4251 Plymouth Road Admin City: Ann Arbor Admin State/Province: MI Admin Postal Code: 48105-2785 Admin Country: US Admin Email: domain-admin@MERIT.EDU Tech ID: 5459322-NSI Tech Name: Merit Network Inc. Tech Organization: Merit Network Inc. Tech Street1: 4251 Plymouth Road Tech Street2: Bldg. 1, Suite 2000 Tech City: Ann Arbor Tech State/Province: MI Tech Postal Code: 48105-2785 Tech Country: US Tech Email: domain-admin@merit.edu Name Server: DNS3.MERIT.NET Name Server: DNS2.MERIT.NET Name Server: DNS.MERIT.NET
participants (4)
-
Bruce Beckwith -
ken emery -
Mike Lewinski -
william＠elan.net