Steven J Vaughan-Nichols wrote an article on ZDNet about a solution ICANN is providing for dealing with domain name collisions. Nichols discusses how he had to help a friend who was having a problem with a .guru name conflicting with the friend’s private network.
From the article:
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, states that “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.”
To address this issue, the framework calls for DNS registry operators to use a technique called “controlled interruption” to alert system administrators that there’s a conflict. What will happen when a collision between a private and public DNS record happens is that the special IPv4 address, 127.0.53.53, will appear in system logs. This will let you quickly see where the problem lies so you can change the site name within your network.
The group is also working on a fix for companies and groups that have already moved on to using IPv6.
Nichols pointed out that this is a temporary patch to the problem. Read the full article here