Slashdot Mirror

← Back to Stories (view on slashdot.org)

ICANN Offers Fix For Domain Name Collisions

Posted by samzenpus on from the jury-rigging dept.

An anonymous reader writes with news about ICANN's fix for conflicting domain names. This kind of problem — when an internal server's DNS name conflicts with one of the new Top Level Domain (TLD) names — is going to start happening more and more often. With over 300 new TLDs available to be used by August 2014 and 1,100 more to come, you can expect to see it a lot. Fortunately, the Internet Corporation for Assigned Names and Numbers (ICANN) has a fix so you don't have to go through all the hoops I did to find the problem: the Name Collision Occurrence Management Framework. According to ICANN, which is also the organization that has blessed us with so many new TLDs to add to such old favorites of .com, .edu, and .org, "The framework is designed to mitigate the impact of name collisions in the DNS, which typically occur when fully qualified domain names conflicts with similar domain names used in private networks. When this occurs, users can be taken to an unintended web page or encounter an error message."

3 of 101 comments (clear)

  1. TL;DR: by supersat · · Score: 5, Informative

    127.0.53.53 will be returned when a collision is detected. AFAICT this means when you query DNS for a non-existant 2nd level domain in one of the new TLDs.

  2. 1993 All over again (RFC-1935) by gavron · · Score: 5, Informative

    Thank you, ICANN, for returning to us a problem resolved in 1993.

    See RFC-1535

    Ehud

  3. Actual ICANN document by Animats · · Score: 5, Informative

    As usual, we have to go through two levels of blogs to get to the actual ICANN document. Which document you may find incomprehensible even if you know how DNS works.