Slashdot Mirror
ICANN Loses Control of Its Own Domain Names
NotNormallyNormal writes "CBC picked up an AP story about ICANN recently losing control over two of their domain names on Thursday, June 26. A domain registrar run by the group transferred the domains to someone else. ICANN's press release had this to say: 'As has been widely reported, a number of domain names, including icann.com and iana.com were recently redirected to different DNS servers, allowing a group to provide visitors to those domains with their own website. It would appear the attack was sophisticated, combining both social and technological techniques, but was also limited and focused.' Comcast has had similar troubles lately as well."
Maybe this'll show them what needs to be changed in the system. Also, err, first post? How?
-=This sig has nothing to do with my comment. Move along now=-
Control my own domains never mind anything else. Please put me out of my misery already.
Marina del Rey, CA (July 5, 2008) --
ENUF. :-( ICANN HAS MY DOMAINS PLZ?
About ICANN
The Internet Corporation for Assigned Names and Numbers (ICANN) is a technical coordination body for the Internet. Created in October 1998 by a broad coalition of the Internet's business, technical, academic, and user communities, ICANN is assuming responsibility for a set of technical functions previously performed under U.S. government contract by IANA and other groups.
Beware: In C++, your friends can see your privates!
In a perfect world, this would serve as a wake-up call to ICANN that the current domain name policies are hideously flawed.
Of course, their heads are so far up their collective asses, though, that they'll just say it was an awesome example of domain tasting by a third party, and all part of the glorious monstrosity they have birthed.
Ha Ha
/nelson
Nothing worthwhile ever happens before noon
It's obvious they didn't follow their own rules by providing valid whois contact information.
When I first read this news several days ago, I thought it was referring to the root servers ...
What most don't know is that the TLDs (ie. com, .net, etc) themselves are registered in much the same manner as 2nd level domains are ... see the TLD Whois: http://whois.iana.org/
The major TLDs (.com, .net, etc) are relatively safe, since any changes would likely be difficult to get through - with any changes quickly noticed ... as in within minutes, or even seconds; likely wouldn't even be that effective, since the most popular TLDs zone dns entries are heavily cached.
However, ccTLDs are a different story completely, since ccTLD zone name server changes are more common and thus such change requests would be far less scrutinized.
I've never heard of any TLD being hijacked, but could likely be easily done, since the social engineering involved would be very similar. A frightening prospect.
Ron
ICANT
haha do you get this? this is soooo funny! lets start doing this from now on! ru with me or agin me?
http://www.cbc.ca/technology/story/2008/07/04/icann-pwned.html
Anyone else think the URL is hilarious?
IANA.com(I am not a .com) but.....
Why do registrars even have to exist? And why does ICANN need to pay other companies to run the actual DNS infrastructure? If ICANN ran .com, .org and .net itself, and there were no registrars/resellers, and every time someone paid for a domain all the money went straight to ICANN, surely ICANN would have enough money to run all the DNS infrastructure itself very well. Then we wouldn't have to deal with all the dodgy things that registries and registrars do, like Verisign's "Site Finder", and various slightly evil registrars stealing domains, and various registrars being incredibly insecure and transferring domains to hackers without proper authentication.
it's called plutocracy
welcome to the real world
Some cell phone execs, although I'm sure they have unlimited plans (or simply don't pay phone bills), so they can see the dangers of having to pay for incoming texts with no way to shut them off.
Wouldn't that be a bit like trying to mail bomb a BOFH?
echo -e 'global _start\n _start:\n mov eax, 2\n int 80h\n jmp _start' > a.asm; nasm a.asm -f elf; ld a.o -o a;
here comes the -1, I don't get it / -1, I don't like you
No, I'd say -1 Offtopic is sufficient, no need to invent new reasons to mod you down :-)
They had no problem getting the domains back. They just kept saying to themselves, "I think ICANN! I think ICANN!"
ICANN would rape your mother if it got them an extra nickel.
Captcha: reared
well, Without them There wouldn't be an internet, for one.
After reading their news release, this goes from "whoo 31337 h4x0r5 shr R Sm4r7" to disgruntaled soon to be ex employee getting he and and all his friends 12 year domains for free for as long as the DNS record is changed. It was an inside job by someone who had access to the Registrar's internal network.
Whoever made the change knew the system and how ICANN and IANA work, and also knew that ICANN can not really say 'well if you got your domain during this 'attack' we want you to pay us some more money' although they may try that. Legally, I am pretty sure it wouldn't stand up to a challenge in court.
Its nice to have a topic where my 2 cents actually mean something finally.
-MnM
Domain Despute Goddess before the fall.plain old tech goddess afterwards ;)
-Magdalene --"there are 10 types of people in the world, those who read binary, and those who don't"
I submitted this a week ago and a firehose reader modded it down quickly.
What changed to make this important now if it wasn't important then?
On a related matter, how many people want to mod this -1 quitchurbitchin?
Knowledge is how to play a game, intelligence is how to win, wisdom is knowing what game to play.
Hmm, in the CBC article is says "Visitors to those addresses are normally redirected automatically to the organization's main sites at ICANN.org and IANA.org, neither of which was affected by the attack."
What is to *re*direct here? DNS is there to translate domain names into IP addresses. It does not have any *re*direction mechanisms. Redirection is a feature of the HTTP protocol and would require to compromise the web-server (which they state has not happened.)
I wonder, Is this simply a typo or does the journalist/editor not understand what (s)he is writing about (and has no references to have this proof read)?
I'm rather vary, because I see such factual errors often in widely read media, written and edited by journalists. Sometimes I see even "experts" quoted with wrong statements. How does this reflect on news that I don't know so much about that I can spot the factual errors?
Busy helping non technical users of OpenOffice.org - http://plan-b-for-openoffice.org/
ICANN, therefore IAM!
ICCAN haz domain?
Talk about a bunch of completely incapable morons ... and we're depending on THEM to keep the Internet running?
Sheesh .. I hope it happens every damned day. In fact I hope someone brings the whole damned thing down. Maybe then the Powers That Be (whoever / whatever THAT is) will replace ICANN top to bottom, clean up the entire domain mess, and give us an honest system.
I noted a similar incident a long time ago, as I pointed out once in this message which was nothing more than one organization filing for the domain name of another, (Sprint registering for the name "MCI.NET") but rather humorous in the result.
The lessons of history teach us - if they teach us anything - that nobody learns the lessons that history teaches us.
I think ICANN are probably do anti-SEO because they are running out of places to store all the money.
I submitted the Wired story of this with the headline 'ICANN gets pwned' over a week ago from a journal entry, oh well...!
Move along now, nothing to see here! Go on!