OpenNIC Infrastructure and Security Explained

OpenNIC is a decentralized alternative to the traditional DNS system, allowing users to access the internet through a network of volunteer-operated servers. These servers are scattered across the globe, providing a more resilient and censorship-resistant internet experience.

One of the key benefits of OpenNIC is its use of a distributed architecture, which means that no single point of failure can bring down the entire network. This is achieved through a network of nodes, each of which can operate independently.

OpenNIC's infrastructure is built on top of the OpenNIC Registry, a database that contains information about the network's nodes and their associated domains. This registry is maintained by a team of volunteer administrators who ensure that the network remains stable and secure.

The OpenNIC community relies on a robust security framework to protect its users and infrastructure from malicious activity. This framework includes measures such as IP blocking, rate limiting, and regular security audits.

For your interest: Open Root Server Network

OpenNIC TLDs are a unique aspect of the OpenNIC network, offering a range of domain name extensions that cater to specific communities and interests. These TLDs are not managed by ICANN, allowing for more flexibility and innovation.

One of the most interesting TLDs is .bbs, which is specific to Bulletin Board Systems (BBSs) on the Internet. This TLD has been around since 2000 and is still active today.

OpenNIC also offers TLDs for communities that might not otherwise have a voice on the ICANN Internet. For example, .ku is for the Kurdish people, .te is for Tamil Eelam, and .ti is for Tibet. These TLDs are part of the OpenNIC network through a peering agreement with the New Nations organization.

Here are some of the OpenNIC TLDs, including their intended use and date introduced:

These TLDs offer a unique opportunity for communities and individuals to express themselves and connect with others who share similar interests.

OpenNIC is a trustworthy alternative to traditional domain name registries like ICANN. OpenNIC is a user-controlled Network Information Center.

Each person registered with OpenNIC has access to a mailing list and a vote on development decisions. This ensures that decisions are made democratically, not by a single governing body.

You don't need to register to access OpenNIC's service, but participating in discussions can be a great way to contribute to the community.

The OpenNIC website is a great resource for finding your closest DNS servers. Immediately, you'll have a list of DNS servers near you.

You can select the first two DNS servers from the list and note them down as your closest servers. You may need to repeat this process if you notice slower access times to certain sites.

The DNS servers are available in both IPv4 and IPv6. Make sure to note them down somewhere for future reference.

On the OpenNIC website, you won't need to perform any setup or configuration, the list of DNS servers is readily available.

A fresh viewpoint: List of DNS Record Types

OpenNIC has a robust infrastructure that enables the operation of special-use TLDs.

These TLDs, such as .opennic.glue, provide hostnames for Tier 1 DNS servers and organizational websites and services. Domains are granted to each Tier 1 server operator or upon approval of the OpenNIC community.

OpenNIC's infrastructure also includes .dns.opennic.glue, which provides hostnames for Tier 2 DNS servers on the OpenNIC network. Domains are automatically created upon the approval of a Tier 2 server.

Here's a breakdown of OpenNIC's technical zones:

OpenNIC operates special-use TLDs for technical or organizational purposes. These TLDs are designed to provide hostnames for specific types of servers and services.

One such TLD is .opennic.glue, which provides hostnames for Tier 1 DNS servers and organizational websites and services. Domains cannot be registered, and are instead granted to each Tier 1 server operator or upon approval of the OpenNIC community.

The .opennic.glue TLD is used for hostnames like "ns2.opennic.glue". This TLD is currently active.

Another TLD is .dns.opennic.glue, which provides hostnames for Tier 2 DNS servers on the OpenNIC network. Domains are automatically created upon the approval of a Tier 2 server.

Here is a summary of the technical zones provided by OpenNIC:

OpenNIC's repository structure is designed to make it easy to manage and maintain its various components.

A released version of OpenNIC is pinned to a specific commit in the master branch of each component repository. This ensures that the version of OpenNIC you're working with is stable and consistent across all its components.

A Bash script called `script/checkout.sh` is provided to help you checkout a specific version of OpenNIC. You can run this script with two arguments: the root directory for the cloned repositories and an optional version number.

By default, `script/checkout.sh` will checkout the latest version of OpenNIC.

The .bit domain was depeered due to disagreements between the OpenNIC and Namecoin projects.

This is a rare occurrence, but it highlights the importance of collaboration and communication in the OpenNIC community.

The .bit domain was previously used for Namecoin systems, websites, and services, but it's no longer available for registration.

It's worth noting that the OpenNIC community is known for its flexibility and adaptability, but even they can't always resolve disputes peacefully.

In this case, the .bit domain was dropped from OpenNIC's peering agreements.

You can access the OpenNIC network by using an alternate DNS server, which resolves domain names to IP addresses, including non-standard top-level domains like .geek, .indy, and .null. These domains aren't currently used by the internet, but you can register them on the OpenNIC DNS system and map them to an IP address of your choice.

The OpenNIC Project has established its own DNS network, which includes a list of available top-level domains, such as .geek, .indy, .bbs, and .gopher. You can register a domain within these top-level domains and use the OpenNIC DNS system.

Related reading: IP Address Management

To access OpenNIC sites, you need to configure your computer to use the OpenNIC DNS servers. This can be done by modifying your network connection's DNS settings using the nmcli command, a terminal interface to Network Manager.

Here's a step-by-step guide to configuring your Linux computer to use an OpenNIC DNS server:

1. Get a list of connections using the nmcli command: `$ sudo nmcli connection`

2. Identify the connection you want to modify and update its ipv4.dns property using the nmcli command: `$ sudo nmcli con modify "Wired connection 1" ipv4.dns "134.195.4.2"` (replace with your closest OpenNIC DNS server)

3. Prevent Network Manager from auto-updating /etc/resolv.conf with your router's DNS settings: `$ sudo nmcli con modify "Wired connection 1" ipv4.ignore-auto-dns yes`

4. Bring your network connection down and then up again to instantiate the new settings: `$ sudo nmcli con down "Wired connection 1"` and `$ sudo nmcli con up "Wired connection 1"`

By following these steps, you can access the OpenNIC network and use non-standard top-level domains like .geek and .indy.

Here's an interesting read: Network Domain

In July 2019, the OpenNIC community voted 13–2 for dropping support for .bit domains due to their "anonymous nature" which led to them being used as malware hubs.

OpenNIC previously resolved .bit (Namecoin) domains through a centralized server that generated a DNS zone from the Namecoin blockchain.

This server provided access to .bit domains through a Tier 1 server that bridges the OpenNIC system and Namecoin.

Some OpenNIC DNS servers made use of a Spamhaus-maintained blocklist of malicious .bit domains.

The .bit TLD was depeered due to disagreements between the OpenNIC and Namecoin projects.

This action resulted in the TLD being dropped from OpenNIC's peering agreements.

The .bit TLD was previously used for Namecoin systems, websites, and services.

The depeering of .bit is a notable example of how peering agreements can be affected by project disagreements.

OpenNIC has a history of depeering TLDs due to various reasons, including project disagreements.

Some TLDs that are currently active and have been peered with OpenNIC include .bazar and .coin.