Jump to content

Main Page: Difference between revisions

From ICANNWiki
No edit summary
No edit summary
Line 29: Line 29:


<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;">
<div style="float:right;margin-left:0.5em;margin-top:0.5em">[[Image:Dotcom.JPG|200px|link=http://icannwiki.com/index.php/.com]]</div>
<big><b>[[Name Collision]]</b></big>
<big><b>[[.com]]</b></big>
<br />
<br />
[[.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 />
Explore the history of the world's most popular TLD with this article.<br /><br />
<b>([[Name Collision|Read the full article...]])</b>
<b>([[.com|Read the full article...]])</b>
<div style="float:right;"><small><strong>Related: [[Domain Name]] - [[New gTLD Program]] - [[NTAG]]</strong></small></div><div style="clear: left;"></div></div>
<div style="float:right;"><small><strong>Related: [[Verisign]] - [[Registry Agreement]] - [[.net]]</strong></small></div><div style="clear: left;"></div></div>


<p>&nbsp;</p>
<p>&nbsp;</p>

Revision as of 23:32, 27 February 2014

ICANNWiki is a nonprofit organization. Learn more about supporting our mission by downloading the
ICANNWiki Info Sheet

Many thanks to our sponsors for all of their continued support!


Neustar  

ICANN

Google
Amazon  Radix

Dominios LatinoaméricaRegistry.Africa  

Afilias  Public Interest Registry

 Donuts   FairWinds Partners

SSIG  Allegravita  

 Freund & Brackey 

Sponsorship


Article of the Week

Vertical Integration
Vertical Integration (VI, or Cross Ownership) is a business structure in which the various functions of the Registry Operator and the Registrar are handled by a single body. This single body is either owned or is under supervision of the same company that supports the specific gTLD; alternatively, the controlling body can be a partnered company that is given the contract of the gTLD. The Registry Operator is not required to provide equivalent access and non-discriminatory access to non-affiliated registrars to sell names under its gTLD. Related policies are developed by ICANN's Vertical Integration Working Group (VIWG). Vertical Integration was banned by ICANN for much of its history, requiring instead Vertical Separation; but in November 2010, the ICANN Board changed its position on Vertical Separation and moved to implement Vertical Integration to foster greater innovation, competition, and presumably provide the consumer with differentiated and lower-priced options.

(Read the full article...)

Related: Registrar - Registry - VIWG


Latest Feature

Name Collision
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.

(Read the full article...)