Domain name registry
This article needs additional citations for verification. (December 2010) (Learn how and when to remove this template message)
A domain name registry is a database of all domain names and the associated registrant information in the top level domains of the Domain Name System (DNS) of the Internet that enables third party entities to request administrative control of a domain name. Most registries operate on the top-level and second-level of the DNS.
A registry operator, sometimes called a network information center (NIC), maintains all administrative data of the domain and generates a zone file which contains the addresses of the nameservers for each domain. Each registry is an organization that manages the registration of domain names within the domains for which it is responsible, controls the policies of domain name allocation, and technically operates its domain. It may also fulfill the function of a domain name registrar, or may delegate that function to other entities.
Domain names are managed under a hierarchy headed by the Internet Assigned Numbers Authority (IANA), which manages the top of the DNS tree by administrating the data in the root nameservers. IANA also operates the int registry for intergovernmental organizations, the arpa zone for protocol administration purposes, and other critical zones such as root-servers.net. IANA delegates all other domain name authority to other domain name registries and a full list is available on their web site. Country code top-level domains (ccTLD) are delegated by IANA to national registries such as DENIC in Germany and Nominet in the United Kingdom.
Some name registries are government departments (e.g., the registry for India gov.in). Some are co-operatives of Internet service providers (such as DENIC) or not-for profit companies (such as Nominet UK). Others operate as commercial organizations, such as the US registry (nic.us).
Some registries sell the names directly, and others rely on separate entities to sell them. For example, names in the .com top-level domains are in some sense sold "wholesale" at a regulated price by VeriSign, and individual domain name registrars sell names "retail" to businesses and consumers.
Historically, domain name registries operated on a first-come-first-served system of allocation but may reject the allocation of specific domains on the basis of political, religious, historical, legal or cultural reasons.
For example, in the United States, between 1996 and 1998, InterNIC automatically rejected domain name applications based on a list of perceived obscenities.
Registries may also control matters of interest to their local communities; for example, the German, Japanese and Polish registries have introduced internationalized domain names to allow use of local non-ASCII characters.
Domains which are registered with ICANN registrars, generally have to use the Uniform Domain-Name Dispute-Resolution Policy (UDRP), however, Germany's DENIC requires people to use the German civil courts, and Nominet UK deals with intellectual property and other disputes through its own dispute resolution service.
Domain name registries may also impose a system of third-level domains on users. DENIC, the registry for Germany (.de), does not impose third level domains. AFNIC, the registry for France (.fr), has some third level domains, but not all registrants have to use them.
Many ccTLDs have moved from compulsory third or fourth-level domain to the availability of registrations of second level domains. Among them are .us (April 2002), .mx (May 2009), .co (March 2010)., and .uk (June 2014).
- Domain name registrar
- Drop registrar
- Private sub-domain registry
- List of Internet top-level domains
- NIC handle
- "ICann.org Glossary". Retrieved 2009-04-21.
- "IANA — Root Zone Database". Retrieved 2019-12-04.
- "NIC México anuncia las etapas de la reapertura de dominios directamente bajo.MX" (in Spanish). NIC México. 2009-02-10. Archived from the original on 2009-02-12. Retrieved 2010-05-19. External link in
- ".CO Launch & Registration Rules" (PDF). Archived from the original (PDF) on 2013-06-27. Retrieved 2012-02-24.