.org Registry Offline - Not
einer writes "According to the The Register, the registry containing all of the .org tld information has fallen off the planet. The article is light on details, and doesn't list any potential consequences. " It looks like it's the server that maintains the records for who owns what .org domain - and a big "I Told You So" for Verisign. And of course, now it seems to be working just fine. Good work, PIR.
I make it a point to never visit any .org sites at all. Vile things, they are. I haven't visited a single .org website in over 2 years.
Slashdotter are stupid and biased.
Because you never know where to find a good orgy....
I just did a whois query on my org domain. It works fine.
now I can't lookup slashdot.org anymore.
...in a few hours, slashdot.org will redirect to microsoft.com or riaa.com...
And I thought the blender.org era was a good thing... Things like this support the corporate credibility in the IT ages. *sigh*
Verisign licensed SCO's Unix Source code on Monday...
Just be thankful all .cx domains are still available.
:P
I don't know if I could make it through the day without a trip to a certain site.
Responsible servers changed, all is well. Nothing to see here. Move along.
.ORG WHOIS information is provided to assist persons in
jrw@gerontius:~$ whois slashdot.org
NOTICE: Access to
determining the contents of a domain name registration record in the PIR
registry database. The data in this record is provided by Public Interest Registry
for informational purposes only, and PIR does not guarantee its
accuracy. This service is intended only for query-based access. You agree
that you will use this data only for lawful purposes and that, under no
circumstances will you use this data to: (a) allow, enable, or otherwise
support the transmission by e-mail, telephone, or facsimile of mass
unsolicited, commercial advertising or solicitations to entities other than
the data recipient's own existing customers; or (b) enable high volume,
automated, electronic processes that send queries or data to the systems of
Registry Operator or any ICANN-Accredited Registrar, except as reasonably
necessary to register domain names or modify existing registrations. All
rights reserved. PIR reserves the right to modify these terms at any
time. By submitting this query, you agree to abide by this policy.
Domain ID:D2289308-LROR
Domain Name:SLASHDOT.ORG
Created On:05-Oct-1997 04:00:00 UTC
Last Updated On:15-Jan-2003 01:48:23 UTC
Expiration Date:04-Oct-2005 04:00:00 UTC
Sponsoring Registrar:R11-LROR
Status:OK
Registrant ID:11-C
Registrant Name:SEE SPONSORING REGISTRAR
Registrant Street1:Whois Server:whois.opensrs.net
Registrant Street2:Referral URL:www.opensrs.org
Registrant City:N/A
Registrant Postal Code:N/A
Registrant Country:CA
Registrant Email:not@available.org
Admin ID:11-C
Admin Name:SEE SPONSORING REGISTRAR
Admin Street1:Whois Server:whois.opensrs.net
Admin Street2:Referral URL:www.opensrs.org
Admin City:N/A
Admin Postal Code:N/A
Admin Country:CA
Admin Email:not@available.org
Billing ID:11-C
Billing Name:SEE SPONSORING REGISTRAR
Billing Street1:Whois Server:whois.opensrs.net
Billing Street2:Referral URL:www.opensrs.org
Billing City:N/A
Billing Postal Code:N/A
Billing Country:CA
Billing Email:not@available.org
Tech ID:11-C
Tech Name:SEE SPONSORING REGISTRAR
Tech Street1:Whois Server:whois.opensrs.net
Tech Street2:Referral URL:www.opensrs.org
Tech City:N/A
Tech Postal Code:N/A
Tech Country:CA
Tech Email:not@available.org
Name Server:NS1.VASOFTWARE.COM
Name Server:NS2.VASOFTWARE.COM
Name Server:NS3.VASOFTWARE.COM
I just hope that MS and others don't hit up OSS for this; the .org registry was the first to run a non Oracle\MS SQL\DB2 database (it runs/ran Postgre).
I don't want Postgre to be the underlying problem in this because it could easily destroy their reputation.
But, this was a concern when the whole TLD split-up was initially suggested. I'm no fan of Verisign but, Network Solutions and Verisign ran a tight ship. This type of thing just didn't happen. ICANN made a big mistake with their breakup of the registrars and this is likely to become a frequent problem.
The worst part is, with the way the resgistrars are distributed now, the blame game is going to be rediculous with everyone pointing at the other guy. In the past there was no question as to who was responsible for any issues.
Why do we have to have a system that relies on single points of failure for each of the main TLDs? Each "maintainer" of the TLD is subject to problems - both mechanical (system failures, congestion, etc.) and human (stupidity, politics, luck).
I don't think the founding fathers of the Internet thought it of it being like this.
> now I can't lookup slashdot.org anymore.
/. is doing real work...
Which isn't that big a deal, till you realize that the alternative to
Oh the humanity!
the .org tld information has fallen off the planet.
I knew the earth was flat but nobody believed me.
"the fax machine is nothing but a waffle iron with a phone attached to it." - Grandpa Simpson
[whois.crsnic.net]
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.
No match for "SLASHDOT.ORG".
>>> Last update of whois database: Mon, 19 May 2003 06:05:55 EDT <<<
pr0n - keeping monitor glass spotless since 1981.
bags I get to name to problem;-)
p e= org&command=slashdot
not quite as bad as the day the internet died as all it means in real terms is a few people will try to buy domain names that arn't available.
anyone want to buy slashdot.org?
http://www.domaincity.co.uk/cgi-bin/whois.pl?ty
it seems to be for sale, or maybe not
sparkes
blog and junk
whois slashdot.org
.com and .net domains can now be registered
[whois.crsnic.net]
Whois Server Version 1.3
Domain names in the
with many different competing registrars. Go to http://www.internic.net
for detailed information.
No match for "SLASHDOT.ORG".
>>> Last update of whois database: Mon, 19 May 2003 06:05:55 EDT
66.35.250.150 slashdot.org
198.186.202.135 NS1.VASOFTWARE.COM
198.186.202.136 NS2.VASOFTWARE.COM
66.35.250.12 NS3.VASOFTWARE.COM
Then your life can continue as normal, despite verisign's fuckup.
the AC
Hemos is like...sci-fi fans;he thinks technology is cool, but he hasn't bothered to understand the science it's based on
And of course, now it seems to be working just fine.
The sky is falling! The sky is falling!
Oh, wait...
In walking, just walk. In sitting, just sit. Above all, don't wobble.
-- Yun-Men
Seriously... Are registry services going to see fallout due to having to reverse and refund erroneous .org registrations that their servers processed during the outage? This might also depend upon whether their scripts depend upon the PIR servers, and whether the scripts distinguish between "error" and "domain not registered" conditions.
Anyone who followed the .Org bidding process knew this day was coming. ICANN's summary dismissal of the IMS/ISC bid as being too technical ("Internet is hard", says ICANN) in favor of 2-bit registrars who "white washed" their record by getting a major NGO to sit on the board made it inevitable.
Here's journalistic integrity for you: a story that reports you cannot reach .org sites posted on and read from a .org site. That's like posting: "you are unable to read this message." Way to go guys.
Join Tor today!
All our bases belong to them!!
:
Check by yourself
$ whois slashdot.org
Found referral to whois.opensrs.net.
Registrant:
Microsoft Corporation
One Microsoft Way
Redmond, WA 98052
US
Domain name: SLASHDOT.ORG
(...)
http://www.pir.org/whois/ I ran a few whois queries straight off of pir's site, so the information is still floating around somewhere.....
no, you're confusing the DNS record with who actually owns it, the registrant information. DNS should still work for a good while...
Related?
I was the source for the story on The Register. You'll see in the detail that it depends on which whois server you use. Crsnic is the one that's misreporting and it's supposed to be provide united results. Looks like PIR isn't talking to Crsnic properly.
Slashdot.org is not accessible any more!
The productivity of my IT company will rise rise riiiise!!
A news site posting a story that it's gone down.
This problem has been around for months... In order to look up WHOIS information on .ORG domains, you have to point your WHOIS client at whois.pir.org. For some reason, whois.internic.net isn't redirecting the appropriate information. I first noticed the problem back in early March.
I don't think the .org registry ever went down. The only Informative message here (IMHO) was from jrwilk01: "Responsible servers changed, all is well. Nothing to see here. Move along." It was marked Redundant and scored 0, just because the moderators only saw the whois record!
Those of you with obsolete whois clients can do something like this:
$ whois slashdot.org@whois.publicinterestregistry.org...
Billing Street1:Whois Server:whois.opensrs.net
...
$ whois slashdot.org@whois.opensrs.net
Or just go to whois.bw.org.
"A door is what a dog is perpetually on the wrong side of" - Ogden Nash
I did a who is and I got this:
Domain ID:D2289308-LROR
Domain Name:SLASHDOT.ORG
Created On:05-Oct-1997 04:00:00 UTC
Last Updated On:15-Jan-2003 01:48:23 UTC
Expiration Date:04-Oct-2005 04:00:00 UTC
Sponsoring Registrar:R11-LROR
Status:OK
Registrant ID:11-C
Registrant Name:SEE SPONSORING REGISTRAR
Registrant Street1:Whois Server:whois.opensrs.net
Registrant Street2:Referral URL:www.opensrs.org
Registrant City:N/A
Registrant Postal Code:N/A
Registrant Country:CA
Registrant Email:not@available.org
It looks like someone is a annymous coward.
-------
Support Indy Music. Buy
I wouldn't go villifying anyone just yet.
-transiit
Looks like Jason Blair got picked up by The Register for this story. First Peter Arnett gets picked up by a UK Tabloid, now this. Those wacky Britts!
-- @rjamestaylor on Ello
My .org domain ran fine all weekend. I do not believe there is any issue of real importance behind all this fooferaw.
.org domain without specifying a valid .org whois server. THE SKY IS FALLING! Guess what, you can't whois a .mil domain without specifying a valid .mil whois server. Nothing to report here, system works as advertised.
.org names seem to resolve fine, and I got a total of ZERO problem reports over the weekend from our 24x7 .org site. Did anyone else have a real DNS problem, or is this all a case of the Register placing too much value on the compiled-in defaults for the whois client?
You can't "whois" a
The important function of a registrar is to feed names into the root nameservers. I don't see any indication of any flaws in that process. All the
Anyone?
No matter how long it was on the front page, this article sullied the reputation of the .org folks, and they deserve an apology and a retraction.
Unless, of course, the Reg doesn't take responsibility for what it publishes. Like a lot of so called "news" sites out there. Heck, even slashdot posts retractions once in a blue moon or two.
--- It is not the things we do which we regret the most, but the things which we don't do.
"By submitting this query, you agree to abide by this policy."
Apparently, we're all dumb as lamp posts and can't bother to read the part of the whois query on our boxes that says this whois server only handles .net and .com
We're going to go back to school, we should be ready to post articles worth reading in a few short years, til then, there's always the BBC, eh?
--- It is not the things we do which we regret the most, but the things which we don't do.
Yeah, that code in MySQL that makes sure users use updated whois clients is really cool. PostgreSQL might get a similar feature soon, but by then MySQL will have an even better feature that prevents The Register from publishing bogus articles about servers being down when they're up. MySQL rocks! Go MySQL!
It's premature to speculate on the cause of the outage
On a more serious note, it's premature to even say there was an outage.
It would appear that, although the original story is still available at the full URL, the Register has taken down all links to it from other areas of the site.
This would be the same site whose journalists often raise an almighty fuss when other publications do exactly the same thing.
I guess they're not double standards when they're your double standards.