Top-level domain edit
extracted from Wikipedia, the Free Encyclopedia
(using Wikipedia Reflection Script)
|
Top-level domain edit
|
|
A top-level domain (TLD), sometimes referred to as a top-level domain name (TLDN), is the last part of an Internet domain name; that is, the letters that follow the final dot of any domain name. For example, in the domain name www.example.com, the top-level domain is com (or COM, as domain names are not case-sensitive). Management of most top-level domains is delegated to responsible parties or organizations by the Internet Corporation for Assigned Names and Numbers (ICANN), which operates the Internet Assigned Numbers Authority (IANA) and is in charge of maintaining the DNS root zone.
IANA currently distinguishes the following groups of top-level domains:1
In addition, a group of internationalized domain name (IDN) top-level domains has been installed for testing purposes.
The authoritative list of currently existing TLDs in the root zone can be found at the IANA website at http://www.iana.org/domains/root/db/ and a Wikipedia list exists.
Contents |
A .nato was added in the late 1980s by the NIC for the use of NATO, who felt that none of the then existing TLDs adequately reflected their status as an international organization. Soon after this addition, however, the NIC created the .int TLD for the use of international organizations, and persuaded NATO to use nato.int instead. However, the nato TLD, although no longer used, was not deleted until July 1996.
Other historical TLDs are .cs for Czechoslovakia (now .cz for Czech Republic and .sk for Slovak Republic), and .zr for Zaire (now .cd for Democratic Republic of the Congo). In contrast to these, the TLD .su has remained active despite the demise of the Soviet Union that it represents. .ru is most commonly used for Russian domains.
RFC 2606 reserves the following four top-level domain names for various purposes, with the intention that these should not be used in production networks within the global domain name system:
In 2007 eleven other internationalized ".test" TLDs were created:23
Today .arpa is used exclusively for Internet-infrastructure purposes such as in-addr.arpa for IPv4 and ip6.arpa for IPv6 reverse DNS lookup, uri.arpa and urn.arpa for the Dynamic Delegation Discovery System, and e164.arpa for Telephone Number Mapping based on NAPTR records. For historical reasons, .arpa is sometimes considered to be a generic TLD.
About the time that ICANN discussed and finally introduced4 .aero, .biz, .coop, .info, .museum, .name, and .pro TLDs, site owners and USENET users argued that a similar TLD should be made available for adult and pornographic websites to settle the dispute of obscene content on the internet and the responsibility of service providers under the questionable Communications Decency Act of 1996. Several options were proposed including .xxx, .sex and .adult, but so far ICANN has chosen not to create any.5
An older proposal6 consisted of seven new gTLDs .arts, .firm, .info, .nom, .rec, .shop, and .web. Later .biz, .info, .museum, and .name covered most of these old proposals.
On 26 June 2008, ICANN approved the relaxation of the rules for the introduction of new TLDs. The new rules will allow any public or private entity from anywhere in the world to register any string of letters as a gTLD. Observers believed that the new rule could result in hundreds of new gTLDs registered this year.7
On 30 July 2008, the U.S. Department of Commerce reiterated the statement that it has no plans to transition management of the authoritative root zone file to ICANN.8
In the past the Internet was just one of many wide-area computer networks. Computers not connected to the Internet, but connected to another network such as BITNET, CSNET or UUCP, could generally exchange e-mail with the Internet via e-mail gateways. For relaying purposes on the gateways, messages associated with these networks were label with suffixes such as .bitnet, .oz, .csnet, and .uucp, but these domains did not exist in the public domain name system.
Most of these networks have long since ceased to exist, and although UUCP still gets significant use in parts of the world where Internet infrastructure has not yet become well-established, it subsequently transitioned to using Internet domain names, so pseudo-domains now largely survive as historical relics. One notable exception is the 2007 emergence of SWIFTNet Mail, which uses the .swift pseudo-domain.9
.local deserves special mention as it is required by the Zeroconf protocol. It is also used by many organizations internally, which will become a problem for those users as Zeroconf becomes more popular. Both .site and .internal have been suggested for private usage, but no consensus has emergedcitation needed.
ICANN's slow progress in creating new gTLDs, and the high registration costs associated with TLDs, contributed to the creation of alternate root servers with their own sets of TLDs. At times, browser plugins have been developed to allow access to some set of "alternative" domain names even when the normal DNS roots are otherwise used.
The anonymity network Tor has a pseudo-domain .onion, which can only be reached with a Tor client because it uses the Tor-protocol (onion routing) to reach the hidden service in order to protect the anonymity of the domain.
|
|||||||||||||||||||||||||||||||||||||||||||||||||