Top-Level Domain: Difference between revisions

Line 3:

The '''TLD''' is always the last part of a domain name, such as [[.com]], [[.net]], [[.us]], etc.<ref>[http://www.pcmag.com/encyclopedia_term/0,2542,t=TLD&i=52942,00.asp]</ref>

Each TLD is managed by a single [[:~~Category:Registries|Registry~~]].

Each TLD is managed by a single [[Registry]].

==History==

The need for a hierarchical [[DNS]] arose with the popularity of the Internet in academic spheres in the early 1980s. This eventually necessitated a de-centralized Internet. Communications between [[The Stanford Research Institute NIC]] and other institutions include plans to create a hierarchical [[DNS]], found in [[http://www.rfc-editor.org/rfc/rfc805.txt RFC 805]], a group document from 1982. This document outlines many of the basics of the eventual [[DNS]], including the need for [[TLD]]s to provide a fixed starting point for queries, and the need for [[SLD]]s to be unique. This, in turn, would necessitate the need for a [[registrar]] type of administration, and help the nascent [[IT]] community recognize that the distribution of responsibility for each domain to individual name servers would provide administrative advantages.<ref>[http://www.livinginternet.com/i/iw_dns_history.htm Living Internet]

==Varieties of TLDs==

There are different types of TLDs.

Line 11:

Line 13:

* [[CCTLD]]

These TLDs ~~operated~~ in different manners, and can be categorized in some simple ways:

These TLDs operate in different manners, and can be categorized in some simple ways:

* Operating Mode

Line 20:

Line 22:

**Restricted - Requiring Local Physical Address, Local Tax ID, or other specific criteria be met to qualify in order to provision a name.

**Sponsored - A variation on Restricted, the applicant for a domain in an [[STLD]] must meet the requirements within that TLD (ie. [[.jobs]] would require that Human Resources be involved, [[.travel]] would require certain Travel criteria are met, etc).

~~==References==~~

~~{{reflist}}~~

== Related Articles ==

@@ Line 3: / Line 3: @@
 The '''TLD''' is always the last part of a domain name, such as [[.com]], [[.net]], [[.us]], etc.<ref>[http://www.pcmag.com/encyclopedia_term/0,2542,t=TLD&i=52942,00.asp]</ref>
-Each TLD is managed by a single [[:Category:Registries|Registry]].
+Each TLD is managed by a single [[Registry]].
+==History==
+The need for a hierarchical [[DNS]] arose with the popularity of the Internet in academic spheres in the early 1980s. This eventually necessitated a de-centralized Internet. Communications between [[The Stanford Research Institute NIC]] and other institutions include plans to create a hierarchical [[DNS]], found in  [[http://www.rfc-editor.org/rfc/rfc805.txt RFC 805]], a group document from 1982. This document  outlines many of the basics of the eventual [[DNS]], including the need for [[TLD]]s to provide a fixed starting point for queries, and the need for [[SLD]]s to be unique. This, in turn, would necessitate  the need for a [[registrar]] type of administration, and help the nascent [[IT]] community recognize that the distribution of responsibility for each domain to individual name servers would provide administrative advantages.<ref>[http://www.livinginternet.com/i/iw_dns_history.htm Living Internet]
 ==Varieties of TLDs==
 There are different types of TLDs.
@@ Line 11: / Line 13: @@
 * [[CCTLD]]
-These TLDs operated in different manners, and can be categorized in some simple ways:
+These TLDs operate in different manners, and can be categorized in some simple ways:
 * Operating Mode
@@ Line 20: / Line 22: @@
 **Restricted - Requiring Local Physical Address, Local Tax ID, or other specific criteria be met to qualify in order to provision a name.
 **Sponsored - A variation on Restricted, the applicant for a domain in an [[STLD]] must meet the requirements within that TLD (ie. [[.jobs]] would require that Human Resources be involved, [[.travel]] would require certain Travel criteria are met, etc).
-==References==
-{{reflist}}
 == Related Articles ==