| <br /><div style="color: #FFF; background-color: #466f81; padding: 5px 10px; border: 1px solid #0d8323;"><big>Latest Feature</big></div><div style="padding: 10px;"> | | <br /><div style="color: #FFF; background-color: #466f81; padding: 5px 10px; border: 1px solid #0d8323;"><big>Latest Feature</big></div><div style="padding: 10px;"> |
− | [[.com]] is one of the first [[TLD]]s to be used on the Internet's [[Domain Name System]]; it was originally intended for commercial purposes, though there are no current restrictions limiting it to commercial entities. It was introduced in 1985 by [[IANA]], which is responsible for the overall coordination and management of the DNS; the organization was led by [[Jon Postel]] at the time. On January 28, 1986, the entities overseeing the DNS met and restructured its makeup to correspond to 8 TLDs, including .com, the others are: [[.gov]] (government), [[.edu]] (American higher education), [[.mil]] (American military), [[.org]] (organization), [[.int]] (international, specifically NATO relations), [[.net]] (sites related to the Internet itself), and [[.bitnet]] (computers on the BITNET network). | + | A [[Name Collision]] describes the circumstance in which a term attempting to reach a private [[Domain Name]] results in resolving to a public Domain Name unintentionally. Private domain names are used in Intranets and in many corporations and organizations throughout the world. A domain name on a private network that matches a name in the public Internet can create security risks, confusion, and systems failure. Although the Name Collision issue is not new, a renewed interest in the issue came about in 2013 as [[ICANN]]'s [[New gTLD Program]] was preparing to delegate hundreds of new domain names to the [[Root Zone]]. The topic was debated fiercely within the ICANN community when a report by Interisle Consulting was prepared for and released by ICANN.<br /><br /> |