
.org Registry Offline - Not 224
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.
So what. (Score:5, Funny)
Re:So what. (Score:4, Funny)
Re:So what. (Score:1, Funny)
Re:So what. (Score:5, Funny)
Re:So what. (Score:2, Funny)
Re:So what. (Score:2, Funny)
Re:So what. (Score:2)
No. The real story is that they recovered the records by using the Google cache. Its saved my ass once or twice.
.org registry (Score:3, Funny)
Because you never know where to find a good orgy....
whois still working (Score:5, Informative)
Re:whois still working (Score:4, Insightful)
Re:whois still working (Score:5, Informative)
The whois server that Simon Perry used to check if his domain was up was owned by Verisign. Which doesn't cary any
Simon, being incredibly stupid, doesn't understand what "The Registry database contains ONLY
Neither do The Register it seems. More great reporting from that high quality news source....
Re:whois still working (Score:5, Informative)
I mean, really. A full-page article alledging that Bill Gates is so full of himself that he forgot that he has to pay for things like the rest of us proles, and then three-paragraph correction reporting that the above story isn't true. It's rediculous! At least Slashdot (usually) posts the update to the top paragraph and highlights it. But reporting something that you know isn't true and then containing the correct right within the story is such bad journalism as to border on the rediculous.
I suppose they've been taking the BOFH over-seriously there. Outright lieing is OK for Simon, since he's a fictional character and expected to be a bastard. But for a supposed news article - one that doesn't even have anything to do with technology, only a press conference gone awry, it is just do dishonest to try and libel someone simply because you disagree with his policies.
I lost a lot of confidence in the Register with that story. I know they have an overly mocking style and that they tend to attack everyone and everything simply as part of their style. But doing so with a story you know if false is unfair and lowers you to the level of mindless zealot. - (X)
* I suppose I'm being overly harsh; the story was originally posted without the correction and the correction was only added later after they found out that the story was false. But I still think they should have included a note at the top. Hardly seems fair to mention it only at the very bottom, does it?
Re:whois still working (Score:2)
Re:whois still working (Score:2)
I think it really may have been 'broken' (Score:2)
It seems there is disagreement and confusion around what the problem was, but there was one, and something was done to aleviate it not much more than a minute after this article was posted. I think a lot of people where confused as to what was, but I think I might be able to shed a rather dim light on it. Unhelpfully, I can't tell you what the issue w
Re:I think it really may have been 'broken' (Score:2)
That seems a separate problem that would point to Tucows as the "nexus" of the problem.
If you're running a recent whois, it should hit whois.publicinterestregistry.net looking for slashdot.org. That whois server will "fess up" to part of the info, but fundamentally forward you to whois.opensrs.net , which is where the authoritative whois info resides.
The question is, what was the "broken" entry? If it said "NONAUTHORITATIVE," which I'd expect, then that indicates that you got vali
Re:I think it really may have been 'broken' (Score:2)
FWIW the 'broken' entry wasn't NONAUTHORITATIVE, it was something (and I use the term loosely) like:
>whois slashdot.org
usual discalimer was here...
Domain: slashdot.org
???: ????
???: CX=0
???: ????
I can't remember what the CX=0 error was exactly, or what the '???'s were (hindsight being 20/20 I wish I had been paying more attention). I was a distinctly odd error though, and it did happen identically, twice, between valid returns of a
I totally agree that it doesn't seem to have ever
Re:whois still working (Score:2)
It doesn't matter if they were insulting bill gates or mother theresa, when the truth came to light, the correction should have contained a contrite apology to PIR for the slur. There was none, just a bit of backpedalling about how internic is having issues with
Funny thin
Re:whois still working (Score:2)
However getting in touch with The Register to tell them
People must get in touch with lots of news outlets every day with 'news' that turns out on closer inspection not to be news at all.
It's up to the news outlets to sift the wheat from the chaff, which The Register appears
Re:whois still working (Score:2)
Two different protocols. If you had some way of triggering an EPP command (registryregistrar protocol) and show both are up, I'd be a bit more at ease. To be truthful, PIR/Afilias are doing a poor job of running
Re:whois still working (Score:5, Interesting)
I never got paged about it, and I certainly would have had things gone down.
It seems more plausible that the problem stems from an out-of-date version of whois.
Version 4.6.2 (released in March) introduced a "patch" redirecting .ORG requests to whois.publicinterestregistry.net ; I'd suggest you check version numbers. Chances are that you're running something reasonably new.
It's plausible that VGRS might have been forwarding requests over to PIR, and shut that capability off this weekend, thereby causing "some inconvenience" to those using out-of-date whois clients.
Taking a look at the posts that led to the Register article, it appears that they headed down a garden path rather like this:
Alternatively, perhaps CRSNIC, the putative point of failure, is having a problem?
Apologies owed. (Score:2)
oh no! (Score:5, Funny)
Bigger problem than you think! (Score:5, Funny)
Which isn't that big a deal, till you realize that the alternative to
Oh the humanity!
Re:oh no! (Score:2)
Re:oh no! (Score:2, Funny)
Uh oh... (Score:4, Funny)
Show Me The Money! (Score:2, Interesting)
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.
Re:Show Me The Money! (Score:2)
THe backend protocol and the servers for PIR, totally seperate from whois, needs to be online to do registrations, dns changes etc.
It's up to the registrar to tell its
Huh?? (Score:3, Insightful)
Yay for redundant root nameservers! (Score:2)
One thing puzzles me though, isn't ISOC managing .org nowadays? Or are they still going to? At any rate, I think ISOC will do a better job than Verisign will ever do anyday.
Re:Yay for redundant root nameservers! (Score:1)
PIR took over the domain on New Year's Day this year after VeriSign was forced to hand over the not-for-profit registry to encourage competition.
In recent news... (Score:5, Funny)
Re:In recent news... (Score:2)
Fictional news can't beat real headlines:
Microsoft Buys SCO Group's Unix [internetnews.com]
I note that the article text immediately does have the correct information that a non-exclusive license is what was purchased, not all the Unix assets.
However, my favorite quote from the SCO news is "teams of lawyers and engineers are scouring the source code" [com.com]
I think lawyers scouring source code is generally not particularly effective.
(Don't look at me. That "zdnet.com.c
Patriot Act (Score:1, Funny)
Lol. (Score:1, Funny)
whois slashdot.org (Score:5, Informative)
hard code this into your hosts file (Score:3, Informative)
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
Re:hard code this into your hosts file (Score:2)
nameserver 198.186.202.135
in /etc/resolv.conf?? and it wasnt verisign's fuckup anyway.. if you read the article you would have seen it was PIR's fault. in fact; they didnt even notice the servers had fallen... verisign gave up the control on new years day.
Re:hard code this into your hosts file (Score:3, Insightful)
As it happens, you shouldn't be doing this at all. It's unecessary traffic. Your DNS server should always be close. In fact some authoritative name servers don't even do recursive lookups to prevent the sort of (ab)use that you suggested.
But it's moot really. This doesn't affect DNS.
People: If this is an issue at all (I see nothing wrong anywhere [maybe PIR got them back up?] and I don't exa
.cx (Score:5, Funny)
I don't know if I could make it through the day without a trip to a certain site.
Re:.cx (Score:2, Funny)
OMFG=Oh my fucking god,
ROFL=rolling on the floor laughing,
OLBBQ=outside lighting a barbecue?
I must be getting old, all these acronyms are getting too much for me.
Update your whois client. (Score:5, Informative)
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
Pushing the legal envelope? (Score:5, Insightful)
Don't hit OSS (Score:4, Interesting)
Re:Don't hit OSS (Score:3, Informative)
With a new whois installation, PIR's servers are contacted instead (whois.publicinterestregistry.net).
With an old configured version of whois, one might try:
whois -h whois.publicinterestregistry.net domain.org
Re:Don't hit OSS (Score:2)
"If shoe fits, wear it."
Flame if you will. (Score:5, Insightful)
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.
Re:Flame if you will. (Score:1, Informative)
Re:Flame if you will. (Score:2)
Hear Hear. Network Solutions routinely "loses" information. That said, it never "lost" an entire domain, but still, screwing thousands of little guys isn't the best service either. I can't speak for Verisign.
Re:Flame if you will. (Score:2, Insightful)
Gotta love the current screwed up state of whois data for
Is there a better way? (Score:5, Insightful)
I don't think the founding fathers of the Internet thought it of it being like this.
I'll take Boardwalk.... (Score:1)
Mike
whats wrong? (Score:1, Informative)
Re:whats wrong? (Score:2)
www.flat-earth.org (Score:5, Funny)
I knew the earth was flat but nobody believed me.
Here's mine (Score:3, Interesting)
[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 <<<
Re:Here's mine (Score:3, Informative)
whois -h whois.pir.org slashdot.org
[whois.pir.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 n
Re:Here's mine (Score:2)
And on my machine:
$ whois --version
Version 4.6.3.
Am I missing something here? Is your version HORIDLY out of date?
Re:Here's mine (Score:5, Informative)
Annoying ideed, but easily fixed. Just create
That should do the job, at least is works for me...
Bad solution (Score:2)
Try gwhois (apt-get install gwhois). Not only will gwhois query whois.pir.org as well after that the appropiate (referenced) whois server and give you real usable results, gwhois also strives to know about most other TLDs, and will query automatically the right whois-servers and can even query web forms for those broken TLD
The day .org died - or anyone want slashdot.org? (Score:5, Interesting)
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
Re:The day .org died - or anyone want slashdot.org (Score:2)
Mine wont whois! (Score:3, Informative)
[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
Re:Mine wont whois! (Score:2, Funny)
$ whois -h whois.crsnic.net slashdot.org
[foobar]
No match for "SLASHDOT.ORG".
[bazqux]
The Registry database contains ONLY
Chicken Little (Score:5, Funny)
The sky is falling! The sky is falling!
Oh, wait...
No Surprise (Score:5, Insightful)
Isn't That Amusing (Score:5, Funny)
Re:Isn't That Amusing (Score:5, Funny)
reading it, i couldn't help but imagine the discovery of this news at
h: 'oh man, .org is down' .org site. bogus!'
t: 'no way'
h: 'way'
t: 'no way'
h: 'way'
t: 'duuuuude. like, slashdot is totally a
h: 'like for real brah. and i was completely about to make some righteous nachos before this happened!'
t: 'oh wait it's back! tubular!'
h: 'schweet. check me out while i post this totally rad story on our site!'
It's too late!! (Score:5, Funny)
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
(...)
Information Still Somewhere ??? (Score:2, Informative)
Boston data line cut (Score:2, Interesting)
Results depend on the whois server used (Score:4, Informative)
Re:Results depend on the whois server used (Score:5, Informative)
As you state in your linked page, CRSNIC is run by Verisign. The same Verisign that handed .org prior to PIR and agreed to a three month handoff period from the start of the year. That would make the cut off March 31st or April 1st depending on your sense of humour. Which, it should come as no suprise, was the date that CRSNIC also stopped providing WHOIS info for .org domains.
I also notice that the Register story has been removed from the frontpage, although the direct link is still available. I think we can safely file this under "Death of .org predicted. Film at eleven."
Retraction is in order (Score:5, Insightful)
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.
Re:Results depend on the whois server used (Score:2)
Hoorray!!! (Score:3, Funny)
The productivity of my IT company will rise rise riiiise!!
Irony: (Score:4, Funny)
It's been this way for weeks (Score:5, Informative)
Re:It's been this way for weeks (Score:2)
Never down? (Score:4, Informative)
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 [bw.org].
Re:Never down? (Score:2)
It's the evil Debian people ! (Score:3, Funny)
Annymous Cowards (Score:2, Funny)
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 loo
I'm skeptical of the news. (Score:5, Insightful)
I wouldn't go villifying anyone just yet.
-transiit
Ooops... (Score:2, Informative)
Re:Ooops... (Score:2)
Astroturfer.
PostgresSQL Replicator - http://pgreplicator.sourceforge.net/
An asynchronous replica engine that provides some data ownership models and many conflict resolution algorithms. [open source, GNU License]
Rserv - http://techdocs.postgresql.org/installguides.php# r serv
Installation guide for triggers to provide Master/Slave replication.
Usogres - http://usogres.good-day.net/
Real time backup utility.
eRServer - http://www.erserver.com/
Enterprise replication se
First Peter, now Jason (Score:3, Funny)
BOGUS REPORT (Score:5, Insightful)
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?
Re:BOGUS REPORT (Score:2, Informative)
Re:BOGUS REPORT (Score:2)
I had a problem last weekend with CougaarForge [cougaar.org] - for some reason the parent domain got redirected to a placeholder page. After a bunch of phone calls they switched it back, but it was most definitely hosed up for most of the weekend...
Yours,
Tom
Re:Problems resolving cougaar.org (Score:2)
Nonetheless... fortunately, the alp-5.ul.isotic.org DNS server seems to have things under control:
> nslookup -type=ANY cougaar.org 4.22.165.5
Server: alp-5.ul.isotic.org
Address: 4.22.165.5
cougaar.org
origin = alp-5.ul.isotic.org
mail addr = alpine-sysadmin.bbn.com
serial = 2002020441
refresh = 14400 (4H)
retry = 3600 (1H)
expire = 604800 (1W)
minimum ttl = 86400 (1D)
cougaar.org nameserver =
New article the Reg should post. (Score:3, Funny)
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?
Re:New article the Reg should post. (Score:2)
disappearing stories about disappearing tlds (Score:2, Insightful)
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.
Unbalanced reporting. (Score:2)
"Which it is all very sloppy and doesn't exactly encourage confidence in the company that now runs the
when they published their "correction" http://theregister.co.uk/content/6/30764.html they said this about verisign / NSI:
"VeriSign's crsnic Whois servers are having trouble. There was some problem with
Comment removed (Score:4, Informative)
Re:My .org just fell off the planet! (Score:2)
Oh - I'm not going to tell you my TiVo password, I'm afraid. I don't want you to see how sad and derivative my choie in TV programmes is.
Re:Verisign? (Score:2)
Why was this modded down? Its true. Perhaps the oppertunity to flame verisign was too tempting.
Re:PostgreSQL (Score:3, Insightful)
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.