This from the SuSE Linux mail list may help 
Forwarded message from "Lewis E. Wolfgang" <wolfgang@nosc.mil>
Something is definitely rotten here.
Whois reports:
Server Name: SLASHDOT.ORG.SUCKS.COMPARED.TO.JIMPHILLIPS.ORG
IP Address: 24.240.60.16
Registrar: TUCOWS, INC.
Whois Server: whois.opensrs.net
Referral URL: http://www.opensrs.org
Domain Name: SLASHDOT.ORG
Registrar: NETWORK SOLUTIONS, INC.
Whois Server: whois.networksolutions.com
Referral URL: http://www.networksolutions.com
Name Server: NS1.ANDOVER.NET
Name Server: NS2.ANDOVER.NET
Updated Date: 13-jun-2001
I've never seen whois report two registrars, especially one that says
"SLASHDOT.ORG.SUCKS.COMPARED.TO.JIMPHILLIPS.ORG"
I also noticed that traceroutes to both slashdot and freshmeat went
through 64.14.80.154, then stopped at that point.
I'd guess that some cracker broke something somewhere? Maybe a
DNS crack? Maybe Andover went bankrupt and pulled the plug
on us? Maybe Micro$oft is behind this?
It sort of illustrates the hazards of having all the open-source
eggs on one server farm....
Regards,
Lew Wolfgang
This from the SuSE Linux mail list may help
>>>>> Forwarded message from "Lewis E. Wolfgang" <wolfgang@nosc.mil>
Something is definitely rotten here.
Yes, the smell of a rotten old thread:
http://www.merit.edu/mail.archives/nanog/2000-10/msg00254.html
Whois reports:
Server Name: SLASHDOT.ORG.SUCKS.COMPARED.TO.JIMPHILLIPS.ORG
IP Address: 24.240.60.16
Registrar: TUCOWS, INC.
Whois Server: whois.opensrs.net
Referral URL: http://www.opensrs.org
Domain Name: SLASHDOT.ORG
Registrar: NETWORK SOLUTIONS, INC.
Whois Server: whois.networksolutions.com
Referral URL: http://www.networksolutions.com
Name Server: NS1.ANDOVER.NET
Name Server: NS2.ANDOVER.NET
Updated Date: 13-jun-2001
I've never seen whois report two registrars, especially one that says
"SLASHDOT.ORG.SUCKS.COMPARED.TO.JIMPHILLIPS.ORG"
I also noticed that traceroutes to both slashdot and freshmeat went
through 64.14.80.154, then stopped at that point.
I'd guess that some cracker broke something somewhere? Maybe a
DNS crack? Maybe Andover went bankrupt and pulled the plug
on us? Maybe Micro$oft is behind this?
Oh hush the fuck up and cut the conspiracy crap.
It sort of illustrates the hazards of having all the open-source
eggs on one server farm....
Regards,
Lew Wolfgang
>
> I've been trying all day to get my /. fix, as well as
> Freshmeat!
>
> Did I miss an announcement? Or is there something else going
> on?
>
>
Slashdot fix...good lord.
The number of registrars queried depends upon your whois implementation.
These various 'blah sucks' things in whois are old news.
My guess is that they're having some sort of network infrastructure
difficulty
(router, switch, load-balancer) or a disk farm outage or somesuch.
Occam's Razor.
Dee McKinney wrote:
... except that people always forget that any automated wrapper for whois
can be broken by this behaviour if left incorrectly parsed (that thread
above arose from exactly such a problem) and it's a point largely
forgotten in the "you are dumb" flames.
j