Alternative DNS Root and Its Various Implementations

Alternative DNS root systems offer a way to bypass traditional DNS root servers, which can be vulnerable to cyber attacks.

The most well-known alternative DNS root system is the Root DNS Server System (rDNS) developed by the Internet Corporation for Assigned Names and Numbers (ICANN).

rDNS allows for the creation of a separate root zone, which can be used to route traffic around traditional DNS root servers.

This can improve network security and resilience by reducing the reliance on a single point of failure.

One implementation of rDNS is the DNS over HTTPS (DoH) protocol, which uses encryption to protect DNS queries and responses.

DoH has been adopted by several major internet service providers, including Cloudflare and Google.

Intriguing read: Root Digiland Tablet

Some organizations provide alternative DNS root services, such as additional top-level domains. This allows users to access the internet through different domain name systems.

OpenNIC is a user-owned and -controlled alternative to traditional domain registries. It provides a non-national democratic alternative to traditional domain registries.

OpenNIC servers can 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. This makes it a viable option for users looking for an alternative to traditional DNS services.

The Open Root Server Network (ORSN) was a network of Domain Name System root nameservers for the Internet. It operated public DNS servers that provided access to the internet freely for everyone, without any limitation.

Here are some alternative DNS implementations:

Namecoin is a blockchain and cryptocurrency designed to support the alternative top-level domain .bit. It's an interesting solution for those looking to create their own domain name.

Namecoin was developed to provide a decentralized alternative to traditional DNS systems.

Alternate DNS roots are an alternative to the traditional DNS root system controlled by ICANN. They provide access to non-standard top-level domain names (TLDs) and can be used by organizations and individuals to create their own Internet DNS systems.

OpenNIC is a user-owned and controlled alternative to InterNIC and ICANN, providing a non-national democratic alternative to traditional domain registries. OpenNIC servers can 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.

The Open Root Server Network (ORSN) was a network of Domain Name System root nameservers for the Internet, operated by the community of ORSN. ORSN root zone information was normally kept in synchronization with the "official" root nameservers coordinated by ICANN.

Open RSC is a group that challenged ICANN's control of the DNS namespace, and they published a root zone containing additional top-level domains not found in the ICANN root zone. ICANN chairwoman Esther Dyson acknowledged adopting features such as membership from ORSC in her response to the United States Department of Commerce.

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.

Some organizations provide alternative DNS root services, such as additional top-level domains. These services can be used by organizations and individuals to create their own Internet DNS systems.

Broaden your view: Open Root Server Network

To use an alternate root, you need to replace the "named.root" file in your DNS server with a new file provided by the alternate root operator. This file usually contains a list of root servers that can be used to resolve non-standard TLDs.

Here are some examples of alternate root operators:

Keep in mind that alternate roots are not recognized by ICANN, which means that the majority of Internet users will not have access to any site you host under one of these domain names.

The Alternative DNS root concept has had its fair share of failed attempts. One notable example is the .nato TLD, which was attempted but ultimately abandoned.

Several alternative DNS root implementations have been proposed over the years, but none have gained widespread adoption. The .nato TLD is a notable example, but it's not the only one.

The .nato TLD was attempted in the 1990s, but it failed to gain traction. It's a reminder that even well-intentioned ideas can fall flat.

The .nato TLD was not the only alternative DNS root implementation to be proposed. Others, such as the .cat TLD, have also been attempted but ultimately abandoned.

The .cat TLD was proposed as an alternative to the traditional DNS root, but it ultimately failed to gain widespread adoption.

See what others are reading: Dns Records Example

The alternative DNS root is supported by several software and services. Unbound is a popular open-source DNS resolver that can be used to access the alternative DNS root.

One of the benefits of using Unbound is that it can be configured to use the alternative DNS root, allowing users to bypass traditional DNS services. This can be particularly useful for users in countries with censorship or internet restrictions.

Unbound can be used in conjunction with other software and services, such as DNSCrypt, to further enhance security and privacy.

Explore further: Internet Telephony Services Providers' Association

The Russian National Domain Name System (НСДИ) is an alternative DNS root project started by Roskomnadzor in 2019.

It's designed to provide an alternative DNS root for all users of the Internet within Russia, with the goal of continuing the functioning of the Russian Internet subnetwork in case of its disconnection from the rest of the Internet.

The project aims to become mandatory for all ISPs in Russia, and as of March 2021, servers are located on the Moscow Internet Exchange.

This alternative DNS root project is a response to the Sovereign Internet Law, which seeks to maintain control over the Russian Internet.

The Russian National Domain Name System is an interesting example of how countries are exploring alternative solutions for their internet infrastructure.

For another approach, see: Domain Name Warehousing

Most DNS servers, including Simple DNS Plus, are configured with a "root file" pointing to the standard DNS root servers controlled by ICANN.

These servers give you access to standard Internet name space including .com, .net, .org, and two letter country codes.

To host non-standard top level domain names, you don't need special configuration in Simple DNS Plus.

However, to resolve these domain names not hosted on your server, you need to replace the "named.root" file located in the Simple DNS Plus application data directory.

This directory is typically "C:\ProgramData\JH Software\Simple DNS Plus", but note that "c:\ProgramData" is hidden.

You can download the new "root file" from the alternate root operator, usually named "named.root" or "named.cache".

Some alternate root operators publish their "root file" for download, while others don't.

You can find more information about alternate root operators on Wikipedia at https://en.wikipedia.org/wiki/Alternative_DNS_root.

The ICANN / standard DNS root has 13 different servers spread around the globe.

These servers are operated with redundancy and security in mind, which is reassuring.

Before replacing your "named.root" file, you may want to check the number of servers listed in the new file and where they are located.

A unique perspective: Nordvpn Dns Servers

The current state of alternative DNS roots is a bit of a mixed bag. Scheme 5.4 is not suitable for rollout because it would prevent Knot resolvers from priming successfully.

This is a major concern because it could lead to problems with Knot resolvers. Even with the current scheme and its adapted versions, schemes 5.1 and 5.2, issues may arise if the root zone is modified.

Only two schemes, 5.5 and 5.5.1, are not associated with any significant drawbacks. This is a promising development, but it's essential to carefully evaluate the feasibility of these alternatives.

A fresh viewpoint: What Are Dns Resolvers

The purpose of the study was to investigate what would happen if each of the root server naming schemes were adopted. We particularly wanted to know whether priming queries sent by existing resolvers would still be successful.

The researchers wanted to find out if resolvers would accept, cache, and use the new names.

One of the key goals was to determine how error-prone resolvers would be, especially when it comes to validating DNSSEC signatures of the new records. This is crucial because failing to do so could lead to priming failures.

Intriguing read: Dns Resolvers

In the current state, Scheme 5.4 is not suitable for rollout because it would prevent Knot resolvers from priming successfully.

Schemes 5.1 and 5.2 are also prone to problems if the root zone is modified, such as when the IP addresses of root servers change.

Only two schemes, 5.5 and 5.5.1, are free from major issues, making them safer options.