Name Collision: Difference between revisions

Revision as of 20:18, 19 February 2014 view source Jonah (talk \| contribs) Bureaucrats, Administrators 6,681 edits →NGPC Resolution ← Older edit		Revision as of 23:01, 19 February 2014 view source Jonah (talk \| contribs) Bureaucrats, Administrators 6,681 edits mNo edit summary Newer edit →
Line 1:		Line 1:
	A '''Name Collision''' describes the circumstance in which a term ~~is used~~ to ~~try and~~ reach a private [[Domain Name]] ~~that~~ results in resolving to a public Domain Name unintentionally. Private domain names are used in [[Intranet]]s 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 ~~in which private information is obtained or private networks are hacked~~.<ref>[http://www.icann.org/en/help/name-collision Name Collision, ICANN.org] Retrieved 18 Feb 2014</ref>		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 [[Intranet]]s 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.<ref>[http://www.icann.org/en/help/name-collision Name Collision, ICANN.org] Retrieved 18 Feb 2014</ref>

	==New gTLD Program==		==New gTLD Program==