Thread: .org domain went down.
According to the register (covered by Slashdot), the .org domain went down for a little while. Isn't that the one running on a postgres server? Does anybody know anything about this? Merlin
Merlin Moncure asked:
> According to the register (covered by Slashdot), the .org domain went
> down for a little while. Isn't that the one running on a postgres
> server? Does anybody know anything about this?
Consider the sources of the information....
I Am Not An Official Mouthpiece, but do have something to do with
operations of .org.
The story seems to be based on a pretty outrageous interpretation of
something going on outside, either having to do with:
a) whois clients being misconfigured so that they access the wrong
server for .ORG.
Suppose you visit <http://www.crsnic.net/> and do a whois query on
slashdot.org. You will receive back the response:
No match for domain "SLASHDOT.ORG".
If you run an old version of whois ("old" meaning "not updated since
before March"), you'll get back much the same response, as whois
used to be set up to pull .org data from VGRS.
Perhaps someone was using an old whois, and misread the output to
indicate that .ORG was out of commission.
b) Possibly some other problem with crsnic.net
There seems to be some indication of similar problems with domains
in the .NET zone, which would point problems towards VGRS.
This "theory" is by no means clear, and may never be, if it
represented some temporary condition that they were quickly able to
resolve.
Either theory seems to fit quite well with the "evidence" in support of
the _The Register_ article...
Of course, what they then do is to infer that since [some local network
problem] has taken place, that therefore the *entire* ORG registry has
gone down without anyone having noticed.
This is no more outrageous than it would be for me to say: "I tried
calling my parents in Ottawa, and couldn't get through. I also couldn't
contact my brother in Halifax. Therefore, based on the evidence, it
appears that some fast-acting version of SARS has killed everyone in
Canada between Ottawa and Halifax." That theory sounds silly? So do
most of the ones at The Register and /.
In other not-necessarily-unrelated news, apparently a backhoe or other
construction took out a lot of Internet connections in the Boston area,
temporarily, which could certainly lead to troubled connectivity for
domain name servers. Supposing crsnic.net or some similar services were
pulling information through an affected connection, it wouldn't be too
remarkable for them to have had some glitchiness for a while.
--
(concatenate 'string "aa454" "@freenet.carleton.ca")
http://www.ntlug.org/~cbbrowne/spreadsheets.html
"The program is manufactured by Quantel, a Silicon Valley company
located in Clearwater, Florida."
On Monday, May 19, 2003, at 10:48 US/Central, Merlin Moncure wrote: > According to the register (covered by Slashdot), the .org domain went > down for a little while. Isn't that the one running on a postgres > server? Does anybody know anything about this? It's working fine, and I see no evidence that it was anything but working fine. The Register's article was a bunch of allegations with no basis in reality. My guess is that someone saw the "No match for 'SLAMB.ORG'."-style message when they did a whois query and assumed that meant the server was down, when it really meant they were querying Verisign's server, which doesn't know anything about .org. And then posted a unsubstantiated rant. And, naturally, the slashdot people linked to it without verifying. Scott
ALL: Just because Afilias is the back end operator for .org I will respond on this. Scott is absolutely right that TheRegister's story was based on incorrect information. CRSNic simply does not contain information for .org domains anymore(see Whois response from CRSNic.net which says it only contains information on com/net/edu and registrars). There was no problem with the .org registry or its Whois system. TheRegister story was (somewhat) corrected yesterday, as was Simon Perry's blog and other sites. If you all have questions, please let me know. Best, Heather -- Heather D. Carle Communications Manager Afilias Tel: +1.215.706.5700 x114 Fax: +1.215.706.5701 E-mail: hcarle@afilias.info http://www.afilias.info <http://www.afilias.info> -----Original Message----- From: pgsql-advocacy-owner@postgresql.org [mailto:pgsql-advocacy-owner@postgresql.org]On Behalf Of Scott Lamb Sent: Monday, May 19, 2003 9:08 PM To: Merlin Moncure Cc: pgsql-advocacy@postgresql.org Subject: Re: [pgsql-advocacy] .org domain went down. On Monday, May 19, 2003, at 10:48 US/Central, Merlin Moncure wrote: > According to the register (covered by Slashdot), the .org domain went > down for a little while. Isn't that the one running on a postgres > server? Does anybody know anything about this? It's working fine, and I see no evidence that it was anything but working fine. The Register's article was a bunch of allegations with no basis in reality. My guess is that someone saw the "No match for 'SLAMB.ORG'."-style message when they did a whois query and assumed that meant the server was down, when it really meant they were querying Verisign's server, which doesn't know anything about .org. And then posted a unsubstantiated rant. And, naturally, the slashdot people linked to it without verifying. Scott ---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to majordomo@postgresql.org so that your message can get through to the mailing list cleanly