Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Slashdot Log In

Log In

[ Create a new account ]

ICANN Loses Control of Its Own Domain Names

Posted by Soulskill on Saturday July 05, @04:59AM
from the heal-thyself dept.
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."

Related Stories

[+] IT: Comcast Briefly Loses Control of Its Domain Name 222 comments
Fallen Andy notes that Comcast, one of the largest US ISPs, lost control of its domain name to what appeared to be juvenile social engineers of the old school — i.e. not in it for the money. The intruders got into Comcast's registrar account at Network Solutions and repointed the domain's DNS records. A blog entry at SANS points out how trivially easy this can be. Reader ElvenKnight points out an insightful interview up at Wired with the two young guys who perpetrated the hack.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • by Calydor (739835) on Saturday July 05, @05:04AM (#24064773)
    Maybe this'll show them what needs to be changed in the system. Also, err, first post? How?
  • 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.

  • by ShakaUVM (157947) on Saturday July 05, @05:12AM (#24064795) Homepage Journal

    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.

  • HaHa (Score:5, Funny)

    by soundguy (415780) on Saturday July 05, @05:12AM (#24064797) Homepage

    Ha Ha

    /nelson

      • Re: (Score:2, Insightful)

        by Anonymous Coward

        Memes like the nelson laugh, beowulf cluster, soviet russia, etc are redundant because we get them all the time.

        • Re: (Score:2, Funny)

          by Anonymous Coward

          Mentioning that those memes are redundant is redundant because it gets mentioned all the time ;)

      • Maybe the post was considered redundant because that's the obvious reaction to the story?

  • Sophisticated ? (Score:5, Informative)

    by stephanruby (542433) on Saturday July 05, @05:21AM (#24064811)
    It's obvious [dnsstuff.com] they didn't follow their own rules by providing valid whois contact information [icann.org].
    • Re:Sophisticated ? (Score:5, Insightful)

      by Anonymous Coward on Saturday July 05, @05:42AM (#24064857)

      ICANN, as far as I can tell, does not follow rules. Their one and only purposes seems to be to enrich the members of its board. As a result, we have a stagnant generic TLD system with new proposals, etc being designed to extract cash for them rather than benefit the world. I have no problem with them getting hacked -- throws a spotlight on their arrogance and corruption.

      ICANN'T do anything to help the world because I am too busy getting paid.

    • Re:Sophisticated ? (Score:4, Insightful)

      by kimba (12893) on Saturday July 05, @07:24AM (#24065071)

      Perhaps you can explain what is not valid in the WHOIS information for these domains?

  • 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/ [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

  • URL (Score:5, Funny)

    by thedrx (1139811) on Saturday July 05, @05:46AM (#24064863)
    http://www.cbc.ca/technology/story/2008/07/04/icann-pwned.html

    Anyone else think the URL is hilarious?
    • It is! Very strange.... Now, you need to ask yourself, Did they pick that out themselves or did Wordpress (or whatever) generate it for them? *giggle*
  • by jibjibjib (889679) on Saturday July 05, @07:47AM (#24065143) Journal
    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.
  • No problem! (Score:4, Funny)

    by Veggiesama (1203068) on Saturday July 05, @08:31AM (#24065247)

    They had no problem getting the domains back. They just kept saying to themselves, "I think ICANN! I think ICANN!"

  • 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 durin

  • by Conficio (832978) on Saturday July 05, @09:48AM (#24065543) Homepage

    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?

    • Being directed and being redirected are REALLY subtle differences in the mind of a techno-plebe. And no, in Canada, there is no requirement for journalists to hold CS degrees.

      So, when something's directed to one place, and then directed to another place, it's not strange for a reporter to assume that it was redirected, as opposed to newly directed.

    • Re: (Score:3, Interesting)

      You're being deliberately pedantic. I thought it was perfectly clear exactly what they meant:

      Normally, A records for icann.com, www.icann.com, iana.com, www.iana.com and similar FQDNs point to IP addresses of web servers that are configured to send an HTTP redirect (via the Location header) that tells the browser to request e.g. http://www.icann.org/ [icann.org] if http://www.icann.com/ [icann.com] had been originally requested.

      While more technically specific, this takes a lot more words to say than "Visitors to those addresses a

      • Re: (Score:3, Insightful)

        "simply point to the same web IP address, which is presumably served by the same server. In my book this is hardly a mirror, which would imply it is somewhat fault tolerant."

        Or the IP is, you know, a Virtual IP on server load balancers and they can host the website on one thousand different servers at the same time for all you know?

    • by ColdWetDog (752185) * on Saturday July 05, @11:16AM (#24066253) Homepage

      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?

      Now it's old news and thus suitable for Slashdot. Before it was rough hot-off-the-press stuff.

      We don't do that sort of thing here.