OpenNIC: Difference between revisions
| Line 8: | Line 8: | ||
== History == |
== History == |
||
OpenNIC was created with the goal of having a democratically-chosen TLD DNS. By the end of July, OpenNIC root servers were operating and several [[top-level domain]]s had been introduced as well as peering of the [[AlterNIC]] namespace. In March 2001 peering began of [[Pacific Root]] and in September a [http://grep.geek/ search engine] was announced which was dedicated to the OpenNIC namespace. |
|||
OpenNIC restructured its architecture to improve scalability and avoid single-point-of-failure issues. Each TLD has its own policies regarding acceptable use. New [[TLD]]s may be created subject to OpenNIC [http://wiki.opennicproject.org/CreatingNewTLDs stated policies]. |
OpenNIC restructured its architecture to improve scalability and avoid single-point-of-failure issues. Each TLD has its own policies regarding acceptable use. New [[TLD]]s may be created subject to OpenNIC [http://wiki.opennicproject.org/CreatingNewTLDs stated policies]. |
||
Revision as of 01:26, 22 October 2013
OpenNIC (www.opennicproject.org)is an alternate network information center/alternative DNS root which lists itself as an alternative to ICANN and its registries.
As of 2006[update] users of the OpenNIC DNS servers are able to resolve all existing ICANN top-level domains as well as their own.
Like all alternative root DNS systems, OpenNIC-hosted domains are unreachable to the vast majority of the Internet. Only specific configuration in one's DNS resolver makes these reachable, and very few Internet service providers have this configuration.
History
OpenNIC was created with the goal of having a democratically-chosen TLD DNS. By the end of July, OpenNIC root servers were operating and several top-level domains had been introduced as well as peering of the AlterNIC namespace. In March 2001 peering began of Pacific Root and in September a search engine was announced which was dedicated to the OpenNIC namespace.
OpenNIC restructured its architecture to improve scalability and avoid single-point-of-failure issues. Each TLD has its own policies regarding acceptable use. New TLDs may be created subject to OpenNIC stated policies.
Top Level Domains
Currently, OpenNIC supports the following TLDs:
- .bbs
- aimed toward (Telnet-style) bulletin board systems and related Web sites.[1]
- .dyn
- dynamic IPs.[2]
- .free
- operated by FreeNIC, the .free tld provides namespace, certificate authority, and other services to encourage the non-commercial use of the internet.[3]
- .fur
- furry fandom-related sites.[4]
- .geek
- chartered for use by geek-oriented sites, including anything of a personal or hobbyist nature. This description is deliberately vague to reflect the huge range of interests that might qualify. [5]
- .opennic.glue
- internal architectural, as in root server administration and peering purposes. The only domain names that exist for this TLD are those that are used for each system on the peer.
- .gopher
- sites using the Gopher protocol.[6]
- .indy
- independent news, media, and entertainment.[7]
- .ing
- fun TLD. Further details to be confirmed.[8]
- .micro
- micronations and their entities. Recent and not widely used yet.[9]
- .neo
- emo subculture with influences of technology, music, and other forms of multimedia.[10]
- .null
- miscellaneous non-commercial individual sites.[11]
- .oss
- open-source software.[12]
- .oz
- Australian-related content, without the residency requirements of .au.[13]
- .parody
- venue for non-commercial parody work. Having a TLD designated to works of parody attempts to remove claims that a website could be mistaken for a business site, and thus reduces the possibility of claims of trademark infringement.[14]
- .pirate
- created as a reaction against internet censorship. (Currently unavailable due to hardware fault)
Peering
OpenNIC also provides resolution of select other alternative DNS roots. Currently OpenNIC peers with New Nations, providing .ko, .ku, .rm, .te, .ti, and .uu.
Public Access Information
To access the OpenNIC Network fully, users need to use (at least one of) its name servers.
For temporary resolution of the above TLDs, i.e. for those who are unable or unwilling to make this kind of change to their system, OpenNIC also provides a proxy server service.[15]
See also
Notes and references
- ^ As described in the .bbs charter OpenNIC .bbs TLD Charter
- ^ As described in the .dyn charter OpenNIC .dyn TLD Charter
- ^ As described in the .free charter OpenNIC .free TLD Charter
- ^ As described on the .fur description page OpenNIC .fur Description
- ^ As described in the .geek charter OpenNIC .geek Charter
- ^ As described in the .gopher charter OpenNIC .gopher Charter
- ^ As described in the .indy Charter OpenNIC .indy Charter
- ^ As described in the .ing Charter OpenNIC .ing Charter
- ^ As described in the .micro Charter OpenNIC .micro Charter
- ^ As described in the .neo Charter OpenNIC .neo Charter
- ^ As described in the .null Charter OpenNIC .null Charter
- ^ As described in the .oss Charter OpenNIC .oss Charter
- ^ As described in the .oz Charter OpenNIC .oz Charter
- ^ As described on the .parody Description page OpenNIC .parody Description
- ^ Shown on the main wiki page ([1]) OpenNIC's Proxy Service, OpenNIC Domain access only