Alternative DNS root: Difference between revisions
imported>Monkbot |
imported>Sprinsla Added a link to https://handshake.org/ |
||
| Line 9: | Line 9: | ||
Zach Bastick proposes that alternative DNS roots have allowed for more democratic control of the Internet: | Zach Bastick proposes that alternative DNS roots have allowed for more democratic control of the Internet: | ||
{{blockquote|The implementation of alternative gTLDs predates any significant debate on name space extension by official actors, and this exemplifies how democratising the DNS alters the pace of developing Internet policy, the nature of decisions that justify that policy development, and political dynamics and user autonomy in the network infrastructure.<ref>{{cite journal|last=Bastick|first=Zach|title=Our Internet and Freedom of Speech 'Hobbled by History': Introducing Plural Control Structures Needed to Redress a Decade of Linear Policy|journal=European Commission: European Journal of EPractice|year=2012|series= Policy lessons from a decade of eGovernment, eHealth & eInclusion|issue=15|pages=97–111|url=http://www.epractice.eu/files/Journal_Volume_15_PART8_0.pdf}}</ref>{{rp|103}}}} | {{blockquote|The implementation of alternative gTLDs predates any significant debate on name space extension by official actors, and this exemplifies how democratising the DNS alters the pace of developing Internet policy, the nature of decisions that justify that policy development, and political dynamics and user autonomy in the network infrastructure.<ref>{{cite journal|last=Bastick|first=Zach|title=Our Internet and Freedom of Speech 'Hobbled by History': Introducing Plural Control Structures Needed to Redress a Decade of Linear Policy|journal=European Commission: European Journal of EPractice|year=2012|series= Policy lessons from a decade of eGovernment, eHealth & eInclusion|issue=15|pages=97–111|url=http://www.epractice.eu/files/Journal_Volume_15_PART8_0.pdf|url-status=dead}}</ref>{{rp|103}}}} | ||
Unless one specifically changes their [[DNS resolver|DNS resolution]] settings, alternative DNS top level domains are generally unreachable, and very few [[Internet service provider]]s provide this configuration by default. | Unless one specifically changes their [[DNS resolver|DNS resolution]] settings, alternative DNS top level domains are generally unreachable, and very few [[Internet service provider]]s provide this configuration by default. | ||
| Line 17: | Line 17: | ||
=== Handshake === | === Handshake === | ||
''Handshake'' is a [[Decentralization|decentralized]] implementation of a [[DNS root zone]] using [[blockchain]] and [[cryptocurrency]] technology to create a [[peer-to-peer]] alternative to the 13 root name servers managed by [[ICANN]].<ref>{{Cite web|title=Decentralized naming and certificate authority An experimental peer-to-peer root naming system|url=https://handshake.org/|access-date=2020-12-11|website=Handshake|language=en}}</ref> | ''[https://handshake.org/ Handshake]'' is a [[Decentralization|decentralized]] implementation of a [[DNS root zone]] using [[blockchain]] and [[cryptocurrency]] technology to create a [[peer-to-peer]] alternative to the 13 root name servers managed by [[ICANN]].<ref>{{Cite web|title=Decentralized naming and certificate authority An experimental peer-to-peer root naming system|url=https://handshake.org/|access-date=2020-12-11|website=Handshake|language=en}}</ref> | ||
Unlike other attempts, Handshake does not aim to replace the existing DNS; rather, it seeks to supplement and enhance it by allowing anyone to bid, register, and manage their own TLDs without an intermediate registrar or delegating authority. Since the [[root zone file]] records are not centrally managed, and instead are stored on a public blockchain, owners of Handshake TLDs can add or change top-level [[resource record]]s to delegate [[authoritative name server]]s and set up [[Domain Name System Security Extensions|DNSSEC]] zone signing directly.<ref>{{Cite web|title=The ambitious plan to reinvent how websites get their names|url=https://www.technologyreview.com/2019/06/04/239039/the-ambitious-plan-to-make-the-internets-phone-book-more-trustworthy/|access-date=2020-12-08|website=MIT Technology Review|language=en}}</ref><ref name=":0">{{Cite web|title=A crypto project to make internet names censorship-proof is now live|url=https://www.technologyreview.com/2020/02/07/844900/handshake-network-dns-live/|access-date=2020-12-08|website=MIT Technology Review|language=en}}</ref> | Unlike other attempts, Handshake does not aim to replace the existing DNS; rather, it seeks to supplement and enhance it by allowing anyone to bid, register, and manage their own TLDs without an intermediate registrar or delegating authority. Since the [[root zone file]] records are not centrally managed, and instead are stored on a public blockchain, owners of Handshake TLDs can add or change top-level [[resource record]]s to delegate [[authoritative name server]]s and set up [[Domain Name System Security Extensions|DNSSEC]] zone signing directly.<ref>{{Cite web|title=The ambitious plan to reinvent how websites get their names|url=https://www.technologyreview.com/2019/06/04/239039/the-ambitious-plan-to-make-the-internets-phone-book-more-trustworthy/|access-date=2020-12-08|website=MIT Technology Review|language=en}}</ref><ref name=":0">{{Cite web|title=A crypto project to make internet names censorship-proof is now live|url=https://www.technologyreview.com/2020/02/07/844900/handshake-network-dns-live/|access-date=2020-12-08|website=MIT Technology Review|language=en}}</ref> | ||
| Line 29: | Line 29: | ||
===OpenNIC=== | ===OpenNIC=== | ||
{{further|OpenNIC}} | {{further|OpenNIC}} | ||
OpenNIC is a user owned and controlled alternative to [[InterNIC]] and ICANN providing a non-national democratic alternative to traditional domain registries. OpenNIC servers are able to resolve all ICANN top-level domains, | OpenNIC is a user-owned and -controlled alternative to [[InterNIC]] and ICANN providing a non-national democratic alternative to traditional domain registries. OpenNIC servers are able to resolve all ICANN top-level domains, OpenNIC-specific top-level domains, and those in other alternative DNS roots with which they have reached [[peering]] agreements.<ref>{{Cite web|url=http://wiki.opennicproject.org/FAQ|title=What is OpenNIC?:OpenNIC Wiki|website=wiki.opennicproject.org|access-date=2017-01-17|archive-url=https://web.archive.org/web/20170118054231/http://wiki.opennicproject.org/FAQ|archive-date=18 January 2017|url-status=dead}}</ref><ref>{{Cite web|url=http://wiki.opennicproject.org/PeerTLDs|title=OpenNIC Peers:OpenNIC Wiki|website=wiki.opennicproject.org|access-date=2017-01-17|archive-url=https://web.archive.org/web/20161227052650/http://wiki.opennicproject.org/PeerTLDs|archive-date=27 December 2016|url-status=dead}}</ref> | ||
===Yeti DNS Project=== | ===Yeti DNS Project=== | ||
Yeti DNS Project is an attempt to build an alternative root server dedicated to [[IPv6]]. Sponsored by a Chinese state agency, the project aims at experimenting with different new DNS-related technology and enabling sovereign countries to explore and control the | Yeti DNS Project is an attempt to build an alternative root server dedicated to [[IPv6]]. Sponsored by a Chinese state agency, the project aims at experimenting with different new DNS-related technology and enabling sovereign countries to explore and control the Internet and enhance their [[network sovereignty]].<ref>{{Cite web|url=https://www.internetgovernance.org/2016/04/07/alternate-dns-roots-and-the-abominable-snowman-of-sovereignty/|title=Alternate DNS roots and the abominable snowman of sovereignty|first1=Brenden|last1=Kuerbis|first2=Milton|last2=Mueller|date=7 April 2016}}</ref><ref>{{Cite web|url=http://en.c114.com.cn/579/a1035022.html|title=Yeti DNS Project:Building Autonomous & Controllable Internet Infrastructures From the Root Server - ICT\cn-c114 ¡ª C114 - China Communication Network|website=en.c114.com.cn}}</ref> | ||
===.chn=== | ===.chn=== | ||
| Line 41: | Line 41: | ||
===Russian National Domain Name System=== | ===Russian National Domain Name System=== | ||
The Russian National Domain Name System ({{langx|ru|НСДИ}}) is an alternative DNS root project started in 2019 by [[Federal Service for Supervision of Communications, Information Technology and Mass Media|Roskomnadzor]] | The Russian National Domain Name System ({{langx|ru|НСДИ}}) is an alternative DNS root project started in 2019 by [[Federal Service for Supervision of Communications, Information Technology and Mass Media|Roskomnadzor]]—a government department for communications, IT and mass media<ref>{{Cite web|url=https://52.rkn.gov.ru/directions/p2363/p30512/|title=Об утверждении Положения о национальной системе доменных имен|website=rkn.gov.ru|access-date=3 March 2021|archive-date=25 February 2021|archive-url=https://web.archive.org/web/20210225214720/https://52.rkn.gov.ru/directions/p2363/p30512/|url-status=dead}}</ref>—that is gradually becoming mandatory for all ISPs in Russia. | ||
As of March 2021, its servers are located on the [[Moscow Internet Exchange]]. | |||
The mission of the project is to provide an alternative DNS root for all users of the Internet within [[Russia]]. The main goal is to continue the functioning of the Russian Internet subnetwork in case of Russia's potential disconnection from the rest of the Internet ([[Sovereign Internet Law]]).{{citation needed|date=November 2025}} | |||
==Defunct implementations== | ==Defunct implementations== | ||
| Line 47: | Line 51: | ||
===Open Root Server Network (ORSN)=== | ===Open Root Server Network (ORSN)=== | ||
{{further|ORSN}} | {{further|ORSN}} | ||
Open Root Server Network (ORSN) was a network of Domain Name System root nameservers for the Internet. ORSN root zone information was normally kept in synchronization with the "official" root nameservers coordinated by ICANN. ORSN Public DNS Servers were operated by the community of ORSN, providing Domain Name System access freely for everyone, without any limitation. ORSN public DNS servers did not log usage. "The ORSN project was canceled on May 2019 and will never come back." {{ | Open Root Server Network (ORSN) was a network of Domain Name System root nameservers for the Internet. ORSN root zone information was normally kept in synchronization with the "official" root nameservers coordinated by ICANN. ORSN Public DNS Servers were operated by the community of ORSN, providing Domain Name System access freely for everyone, without any limitation. ORSN public DNS servers did not log usage. "The ORSN project was canceled on May 2019 and will never come back." | ||
<ref>{{cite web |url=http://www.orsn.org/en/faq/ |title=Open Root Server Network - General Information about this Project |website=ORSN.org |accessdate=2017-07-28 |archive-date=6 October 2017 |archive-url=https://web.archive.org/web/20171006125625/http://www.orsn.org/en/faq/ |url-status=dead}}</ref> | |||
===AlterNIC=== | ===AlterNIC=== | ||
| Line 54: | Line 59: | ||
===eDNS=== | ===eDNS=== | ||
eDNS (Enhanced Domain Name Service) was founded by a coalition of ISPs led by [[Karl Denninger]] of the Chicago-area MCSNet.<ref>{{cite news|url=http://connection.ebscohost.com/c/articles/9707181217/schism-hits-domain-name-system|archive-url=https://web.archive.org/web/20131029190527/http://connection.ebscohost.com/c/articles/9707181217/schism-hits-domain-name-system|url-status=dead|archive-date=2013-10-29|first=Will|last=Rodger|title=Schism hits Domain Name System|work=Inter@ctive Week|date=February 1997|volume=4|number=5|accessdate=2013-01-05}}</ref><ref>{{cite news|url=http://news.cnet.com/Rogue-domains-revolt/2100-1023_3-275957.html|title=Rogue domains revolt|work=[[CNET]]|date=1997-03-04|accessdate=2013-01-06}}</ref> It ceased operation in 1998. It served the following domains: biz (general business use), corp (corporations), fam (for and about family), k12 (for and about children), npo (non-profit organizations), per (personal domains), web (web-based sites, Web pages). | eDNS (Enhanced Domain Name Service) was founded by a coalition of ISPs led by [[Karl Denninger]] of the Chicago-area MCSNet.<ref>{{cite news|url=http://connection.ebscohost.com/c/articles/9707181217/schism-hits-domain-name-system|archive-url=https://web.archive.org/web/20131029190527/http://connection.ebscohost.com/c/articles/9707181217/schism-hits-domain-name-system|url-status=dead|archive-date=2013-10-29|first=Will|last=Rodger|title=Schism hits Domain Name System|work=Inter@ctive Week|date=February 1997|volume=4|number=5|accessdate=2013-01-05}}</ref><ref>{{cite news|url=http://news.cnet.com/Rogue-domains-revolt/2100-1023_3-275957.html|title=Rogue domains revolt|work=[[CNET]]|date=1997-03-04|accessdate=2013-01-06}}</ref> It ceased operation in 1998. It served the following domains: biz (general business use), corp (corporations), fam (for and about family), k12 (for and about children), npo (non-profit organizations), per (personal domains), web (web-based sites, Web pages).{{citation needed|date=November 2025}} | ||
===Open RSC=== | ===Open RSC=== | ||
One of the notable challengers to ICANN's control of the DNS namespace was | One of the notable challengers to ICANN's control of the DNS namespace was [[Open RSC|Open RSC (Open Root Server Confederation)]], a group that grew out of private discussions and developed into a public [[Listserv|Listserv mailing list]]. It grew large enough that the group decided to submit an application to the United States government to run the DNS.<ref>{{cite web|url=http://www.ntia.doc.gov/ntiahome/domainname/proposals/orsc/ORSC_PRO.htm |title=ORSC proposal of 8 October 1998 |publisher=Ntia.doc.gov |accessdate=2009-11-06| archiveurl= https://web.archive.org/web/20091109182608/http://www.ntia.doc.gov/ntiahome/domainname/proposals/orsc/ORSC_PRO.htm| archivedate= 9 November 2009 | url-status= live}}</ref> | ||
The organization posted bylaws and articles of incorporation outlining | The organization posted bylaws and articles of incorporation outlining Open RSC's position following extensive public discussion regarding the manner in which the DNS was operated.<ref>{{cite web|url=http://www.ntia.doc.gov/ntiahome/domainname/proposals/orsc/bylaws.html |title=ORSC bylaws |publisher=Ntia.doc.gov |accessdate=2009-11-06| archiveurl= https://web.archive.org/web/20091021022746/http://www.ntia.doc.gov/ntiahome/domainname/proposals/orsc/bylaws.html| archivedate= 21 October 2009 | url-status= live}}</ref><ref>{{cite web|url=http://www.ntia.doc.gov/ntiahome/domainname/proposals/orsc/ORSC_PRO.htm |title=ORSC articles of incorporation |publisher=Ntia.doc.gov |accessdate=2009-11-06| archiveurl= https://web.archive.org/web/20091109182608/http://www.ntia.doc.gov/ntiahome/domainname/proposals/orsc/ORSC_PRO.htm| archivedate= 9 November 2009 | url-status= live}}</ref>{{elaborate|date=November 2025}} | ||
ICANN chairwoman [[Esther Dyson]] acknowledged adopting features such as membership from | ICANN chairwoman [[Esther Dyson]] acknowledged adopting features such as membership from Open RSC in her response to the [[United States Department of Commerce]].<ref>{{cite web|url=http://www.ntia.doc.gov/ntiahome/press/icann111098.htm |title=NTIA Reviewing ICANN November 6 Submission |publisher=Ntia.doc.gov |accessdate=2009-11-06| archiveurl= https://web.archive.org/web/20091108032422/http://www.ntia.doc.gov/ntiahome/press/ICANN111098.htm| archivedate= 8 November 2009 | url-status= live}}</ref>{{clarify|in her response to what from the U.S. Department of Commerce?|date=November 2025}} | ||
Open RSC publishes a root zone containing additional top level domains not found in the [[ICANN]] root zone.{{examples needed|date=November 2025}} | |||
===RealNames=== | ===RealNames=== | ||
Microsoft offered the [[RealNames]] service on its Internet Explorer browser address bar. RealNames, to users of Internet Explorer, was in effect a [[domain registry]]. RealNames shut down operations in 2002 following a decision by Microsoft to redirect the | Microsoft offered the [[RealNames]] service on its Internet Explorer browser [[address bar]]. RealNames, to users of Internet Explorer, was in effect a [[domain registry]]. RealNames shut down operations in 2002 following a decision by Microsoft to redirect the billion page views per calendar quarter that RealNames was resolving from the browser address bar into its [[MSN search engine]].{{Citation needed|date=March 2018}} | ||
== See also == | == See also == | ||
Latest revision as of 18:48, 13 December 2025
Template:Short description The Internet uses the Domain Name System (DNS) to associate numeric computer IP addresses with human-readable names. The top level of the domain name hierarchy, the DNS root, contains the top-level domains that appear as the suffixes of all Internet domain names. The most widely used (and first) DNS root is administered by the Internet Corporation for Assigned Names and Numbers (ICANN). In addition, several organizations operate alternative DNS roots, often referred to as alt roots. These alternative domain name systems operate their own root name servers and commonly administer their own specific name spaces consisting of custom top-level domains.
The Internet Architecture Board (IAB) has spoken out strongly against alternative roots in Template:IETF RFC.[1]
Overview
The DNS root zone consists of pointers to the authoritative domain name servers for all top-level domains (TLDs). The root zone is hosted on a collection of root servers operated by several organizations around the world that all use a specific, approved list of domains that is managed by ICANN. By contrast, alternative roots typically include pointers to all of the TLD servers for domains delegated by ICANN, as well as name servers for other, custom top-level domains that are not sanctioned by ICANN. Some alternative roots are operated by the organizations that manage these alternative TLDs.
Zach Bastick proposes that alternative DNS roots have allowed for more democratic control of the Internet:
<templatestyles src="Template:Blockquote/styles.css" />
The implementation of alternative gTLDs predates any significant debate on name space extension by official actors, and this exemplifies how democratising the DNS alters the pace of developing Internet policy, the nature of decisions that justify that policy development, and political dynamics and user autonomy in the network infrastructure.[2]Template:Rp
Script error: No such module "Check for unknown parameters".
Unless one specifically changes their DNS resolution settings, alternative DNS top level domains are generally unreachable, and very few Internet service providers provide this configuration by default.
Implementations
Some organizations provide alternative DNS root services, such as additional top-level domains.
Handshake
Handshake is a decentralized implementation of a DNS root zone using blockchain and cryptocurrency technology to create a peer-to-peer alternative to the 13 root name servers managed by ICANN.[3]
Unlike other attempts, Handshake does not aim to replace the existing DNS; rather, it seeks to supplement and enhance it by allowing anyone to bid, register, and manage their own TLDs without an intermediate registrar or delegating authority. Since the root zone file records are not centrally managed, and instead are stored on a public blockchain, owners of Handshake TLDs can add or change top-level resource records to delegate authoritative name servers and set up DNSSEC zone signing directly.[4][5]
Existing TLDs are reserved in the Handshake blockchain such that resolving traditional domain names (i.e. zones under .com, .org, .net, etc.) through a Handshake node or name server are directed back to ICANN's root servers. In addition, the top 100,000 most popular domains are reserved as Handshake TLDs which can be redeemed by the original domain owner.[5]
Namecoin
Script error: No such module "labelled list hatnote". Namecoin is a blockchain and cryptocurrency to support the alternative top-level domain .bit.[6]
OpenNIC
Script error: No such module "labelled list hatnote". OpenNIC is a user-owned and -controlled alternative to InterNIC and ICANN providing a non-national democratic alternative to traditional domain registries. OpenNIC servers are able to resolve all ICANN top-level domains, OpenNIC-specific top-level domains, and those in other alternative DNS roots with which they have reached peering agreements.[7][8]
Yeti DNS Project
Yeti DNS Project is an attempt to build an alternative root server dedicated to IPv6. Sponsored by a Chinese state agency, the project aims at experimenting with different new DNS-related technology and enabling sovereign countries to explore and control the Internet and enhance their network sovereignty.[9][10]
.chn
Script error: No such module "labelled list hatnote". Template:Expand Chinese .chn is a new top-level domain with its own root DNS server for an Internet of Things (IoT) network in China. The company developing this alternative root claims that China has its own intellectual right on this new alternative domain name root and the associated IoT network, and that it will become the second computer network in the world.[11][12] It is claimed to be part of a "IPv9" decimal network/numeric domain name system developed and innovated in China.[13]
Russian National Domain Name System
The Russian National Domain Name System (Template:Langx) is an alternative DNS root project started in 2019 by Roskomnadzor—a government department for communications, IT and mass media[14]—that is gradually becoming mandatory for all ISPs in Russia.
As of March 2021, its servers are located on the Moscow Internet Exchange.
The mission of the project is to provide an alternative DNS root for all users of the Internet within Russia. The main goal is to continue the functioning of the Russian Internet subnetwork in case of Russia's potential disconnection from the rest of the Internet (Sovereign Internet Law).Script error: No such module "Unsubst".
Defunct implementations
Open Root Server Network (ORSN)
Script error: No such module "labelled list hatnote". Open Root Server Network (ORSN) was a network of Domain Name System root nameservers for the Internet. ORSN root zone information was normally kept in synchronization with the "official" root nameservers coordinated by ICANN. ORSN Public DNS Servers were operated by the community of ORSN, providing Domain Name System access freely for everyone, without any limitation. ORSN public DNS servers did not log usage. "The ORSN project was canceled on May 2019 and will never come back." [15]
AlterNIC
Script error: No such module "Labelled list hatnote". AlterNIC was created before ICANN's creation to challenge the monopoly of InterNIC on domain name governance at the time.[16][17]
eDNS
eDNS (Enhanced Domain Name Service) was founded by a coalition of ISPs led by Karl Denninger of the Chicago-area MCSNet.[18][19] It ceased operation in 1998. It served the following domains: biz (general business use), corp (corporations), fam (for and about family), k12 (for and about children), npo (non-profit organizations), per (personal domains), web (web-based sites, Web pages).Script error: No such module "Unsubst".
Open RSC
One of the notable challengers to ICANN's control of the DNS namespace was Open RSC (Open Root Server Confederation), a group that grew out of private discussions and developed into a public Listserv mailing list. It grew large enough that the group decided to submit an application to the United States government to run the DNS.[20]
The organization posted bylaws and articles of incorporation outlining Open RSC's position following extensive public discussion regarding the manner in which the DNS was operated.[21][22]Template:Elaborate
ICANN chairwoman Esther Dyson acknowledged adopting features such as membership from Open RSC in her response to the United States Department of Commerce.[23]Script error: No such module "Unsubst".
Open RSC publishes a root zone containing additional top level domains not found in the ICANN root zone.Template:Examples needed
RealNames
Microsoft offered the RealNames service on its Internet Explorer browser address bar. RealNames, to users of Internet Explorer, was in effect a domain registry. RealNames shut down operations in 2002 following a decision by Microsoft to redirect the billion page views per calendar quarter that RealNames was resolving from the browser address bar into its MSN search engine.Script error: No such module "Unsubst".
See also
References
<templatestyles src="Reflist/styles.css" />
- ↑ Template:IETF RFC (informational), IAB Technical Comment on the Unique DNS Root, Internet Architecture Board, The Internet Society (May 2000), Quote: "There is no getting away from the unique root of the public DNS." (page 5)
- ↑ Script error: No such module "Citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ a b Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ George Lawton,Script error: No such module "citation/CS1"., SunWorld, 1996-09-16, retrieved through Archive.org
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
Script error: No such module "Check for unknown parameters".