OpenNIC Wiki - opennic

DNSSEC Validation - update current keys and samples

joestr1@undisclosed.example.com (joestr1) — Wed, 29 Apr 2026 17:49:34 +0000

DNSSEC Validation DNSSEC is a mechanism that prevents DNS forgeries that could potentially redirect you or your Tier 2 users to malicious sites. Tier 2 Configuration FIXME We're looking for guides for other DNS software, contributions welcome! Tier 2 providers may enable DNSSEC validation by following the guide(s) below, corresponding to their

.o TLD - .o TLD

EMREOYUN@undisclosed.example.com (EMREOYUN) — Wed, 15 Apr 2026 21:07:34 +0000

.o TLD Charter The .o TLD, is to be used by commercial and non-commercial entities (individuals or groups) to promote themselves on the OpenNIC network. This domain is intended to be general-purpose, and as such, registration is open with minimal restrictions.

OpenNIC Operated Top-Level Domains - .o TLD

EMREOYUN@undisclosed.example.com (EMREOYUN) — Wed, 15 Apr 2026 21:02:52 +0000

OpenNIC Operated Top-Level Domains These are the Top-Level Domains (TLDs) which are currently being served by OpenNIC, are being constructed with the approval of OpenNIC or which have been proposed to OpenNIC. There are links to the appropriate Web and email contacts for those which are currently accepting domain name registrations.

TLS Certificates - Update Debian instructions

koala@undisclosed.example.com (koala) — Fri, 10 Jan 2025 17:09:56 +0000

TLS Certificates Current deployment There is an experimental acme server in place at to automatically obtain TLS certificates for servers under all OpenNIC top level domains (Restricted by Name Constraints). The trust anchor for these certificates can be downloaded

Automatic OpenNIC Zone Generation

resingm@undisclosed.example.com (resingm) — Sun, 18 Jun 2023 11:47:52 +0000

Automatic OpenNIC Zone Generation The information below is based on a Debian/Ubuntu server with BIND9 installed. You may need to make adjustments for different distributions or if you are using a chroot setup. The directions below do not require that you already have access to OpenNIC domains for configuration. All steps will be performed from the command line.

OpenNIC TLD/Root Servers - [Zone Authoritative Servers]

Olde16@undisclosed.example.com (Olde16) — Sun, 22 Jan 2023 19:24:42 +0000

OpenNIC TLD/Root Servers For an up-to-date list of all servers and their status, check out the servers status site. Root Servers Do not query this server directly. Use the Tier 2 servers instead. Root servers are not used for recursively resolving domain names.

OpenNIC Infrastructure - Added a few links to spice it up a little

Olde16@undisclosed.example.com (Olde16) — Sun, 22 Jan 2023 18:57:38 +0000

OpenNIC Infrastructure OpenNIC infrastructure related wiki pages → Root Servers and TLD Servers → Tier 1 Servers → Tier 2 Servers → Namespaces / Zones

BIND9 Zone Configuration - [/etc/bind/db.opennic] Updated name servers

Olde16@undisclosed.example.com (Olde16) — Tue, 03 Jan 2023 19:08:24 +0000

BIND9 Zone Configuration Tier 1 Server Tier 2 Server /etc/bind/named.conf.local view "opennic" { allow-query { any; }; match-clients { any; }; recursion yes; max-cache-size 30%; ######################################## ROOT OPENNIC zone "." { type secondary; file "/etc/bind/zones/slaves/db.root"; masters { 195.201.99.61; 168.119.153.26; }; allow-transfer { any; }; notif…

Slaved Zones with BIND9 - Updated Page, Added cosmetics, rewritten a few sentences to include ...

Olde16@undisclosed.example.com (Olde16) — Sun, 27 Nov 2022 13:02:25 +0000

Slaved Zones with BIND9 Also refer to BIND9 Zone Configuration for ready to use zone file examples of Tier 1 and Tier 2 Servers. Consider using the srvzone script. For those wishing to set up a more robust local nameserver, or if you plan on running a public Tier 1 or Tier 2 server for OpenNIC, configuring BIND with slave zones is the preferred method. Please read

Setting up a Tier 1 Server - Updated root server IP

Shdwdrgn@undisclosed.example.com (Shdwdrgn) — Sat, 20 Mar 2021 16:40:32 +0000

Setting up a Tier 1 Server Tier 1 servers are the core DNS servers hosting authoritative zones for all OpenNIC TLDs and the OpenNIC root (.) zone. FIXME This legacy wiki article has been copied from . It is outdated and should not be blindly used for copy-pasting. Use this information as a starting point to further researching current methods.

Local BIND Caching Server - updated util ips

fusl@undisclosed.example.com (fusl) — Thu, 26 Nov 2020 19:31:39 +0000

Local BIND Caching Server The easiest setup is to use a local caching server. The following will configure a private nameserver for your personal use. :!: If you wish to run a public Tier 2 server, follow the Slaved Zones instructions, not these. If you are trying to anonymize your browsing history, please be aware that installing your own nameserver or using OpenNIC services will not hide your queries. OpenNIC operators are only in control of OpenNIC domains. Any queries you make to

.gopher TLD - [Contacts]

Starbaby75 @undisclosed.example.com (Starbaby75 ) — Thu, 13 Aug 2020 15:01:51 +0000

.gopher TLD Charter .gopher is chartered for use by sites offering content via the gopher protocol and is intended to showcase existing gopher sites as well as foster the establishment of new sites. Sites hosted on a .gopher domain should not serve content via any other protocol. Commercial or non-commercial entities may register .gopher domains. Multiple registrations by a single entity are permissible provided multiple qualifying uses exist.

.dyn TLD - [Example Script] HTTPS instead of HTTP

Stemby@undisclosed.example.com (Stemby) — Wed, 05 Aug 2020 12:13:20 +0000

.dyn TLD Charter Domains registered in .dyn serve as dynamic DNS pointers. These domains are restricted in functionality and require frequent validation to remain active. Unused domains will be removed after 28 days. .dyn is a TLD that is designed to resolve host names to dynamic Internet Protocol addresses, which usually are a result of the respective Internet Service Provider. Non-dynamic IP addresses also known as static IP addresses may be used.

List your server on servers.opennic.org - [Disabled and pending deletion servers] Add Tier 0 link

megan@undisclosed.example.com (megan) — Sat, 11 Apr 2020 10:02:53 +0000

List your server on servers.opennic.org Information as of 2020-04-11 After setting up and making sure your DNS server is operational, it's now time to list it! Announce it on IRC or the mailing list so everyone is kept informed. As a last minute check, make sure that your logging and security settings are tuned correctly.

Setup - created

megan@undisclosed.example.com (megan) — Sat, 11 Apr 2020 09:12:11 +0000

Setup This namespace contains tutorials, guides and tips on how to setup an OpenNIC DNS server. Tutorials * Installing using Webmin by fouroh-llc Topics * List your server on servers.opennic.org ---------- INFO: Most of the relevant wiki pages are still in the :opennic namespace such as Setting up a Tier 2 Server

Setting up a Tier 2 Server - [Post-Setup Configuration] add listing tutorial link

megan@undisclosed.example.com (megan) — Sat, 11 Apr 2020 09:02:51 +0000

Setting up a Tier 2 Server Tier 2 servers (DNS resolvers) can be used for public or private DNS lookups, on the OpenNIC and ICANN namespaces. Recommended Minimum Server Specifications * Linux * 1 CPU Core * 512 MB RAM * 4 GB SSD Considerations

listserver_edit_page.png - created

megan@undisclosed.example.com (megan) — Sat, 11 Apr 2020 08:35:12 +0000

Fresh Install

fouroh-llc@undisclosed.example.com (fouroh-llc) — Fri, 27 Mar 2020 11:44:12 +0000

Fresh Install This page includes a very brief overview of Webmin module screens, before turning the instance into a Tier-2 service stack. The page is going to grow and expand as feedback comes in for better, more detailed explanations. If you are already familiar with Webmin, or you do not wish to use it you may skip this page entirely.

base-011.png - created

fouroh-llc@undisclosed.example.com (fouroh-llc) — Thu, 26 Mar 2020 19:08:56 +0000

base-010.png - created

fouroh-llc@undisclosed.example.com (fouroh-llc) — Thu, 26 Mar 2020 15:26:15 +0000

base-009.png

fouroh-llc@undisclosed.example.com (fouroh-llc) — Thu, 26 Mar 2020 15:13:00 +0000

base-008.png

fouroh-llc@undisclosed.example.com (fouroh-llc) — Thu, 26 Mar 2020 14:40:03 +0000

base-007.png

fouroh-llc@undisclosed.example.com (fouroh-llc) — Thu, 26 Mar 2020 14:22:22 +0000

base-006.png

fouroh-llc@undisclosed.example.com (fouroh-llc) — Thu, 26 Mar 2020 13:57:26 +0000

base-005.png

fouroh-llc@undisclosed.example.com (fouroh-llc) — Thu, 26 Mar 2020 13:48:26 +0000

base-004.png

fouroh-llc@undisclosed.example.com (fouroh-llc) — Thu, 26 Mar 2020 13:14:50 +0000

- removed

fouroh-llc@undisclosed.example.com (fouroh-llc) — Thu, 26 Mar 2020 12:48:41 +0000

Installing using Webmin - [Installing using Webmin]

fouroh-llc@undisclosed.example.com (fouroh-llc) — Thu, 26 Mar 2020 12:24:28 +0000

Installing using Webmin Webmin provides more than just some webforms, it is part of a fully rounded virtualization and cloud platform. Virtualmin and Cloudmin are used to create complex networks, and they install on top of a brand new BIND instance. Webmin is the glue holding the networks together by installing its own perl-based web services, the standard GNU/Linux technology stack, using ssh and making remote procedure calls (RPC). By adding its own schema to OpenLDAP it supports fine-grained…

base-003.png - created

fouroh-llc@undisclosed.example.com (fouroh-llc) — Wed, 18 Mar 2020 17:40:12 +0000

base-002.png - created

fouroh-llc@undisclosed.example.com (fouroh-llc) — Wed, 18 Mar 2020 15:55:47 +0000

base-001.png - created

fouroh-llc@undisclosed.example.com (fouroh-llc) — Wed, 18 Mar 2020 13:01:15 +0000

- removed

fouroh-llc@undisclosed.example.com (fouroh-llc) — Wed, 18 Mar 2020 12:24:22 +0000

.epic TLD

okashi_o@undisclosed.example.com (okashi_o) — Fri, 13 Sep 2019 21:50:53 +0000

.epic TLD .epic is a general purpose TLD for whatever you might find, as the name suggests, epic. Registration Registrations are via or . Register for an account and register for a domain via the web interface. Charter Policies The following things are not accepted and will result in revocation of your domain:

OpenNIC service accounts - [OSS Host Proxmox Access]

fusl@undisclosed.example.com (fusl) — Tue, 04 Jun 2019 17:58:40 +0000

OpenNIC service accounts This wiki article contains service and PR accounts, groups and teams. GitHub (OpenNIC) * * Note: This is currently the primary code repository for OpenNIC * Owners: * Fusl, fusl * luggs-co * Shdwdrgn * stephan48 * timgws * woggo85 * Members:

.null TLD - [Contacts]

mborder@undisclosed.example.com (mborder) — Thu, 02 May 2019 06:45:14 +0000

.null TLD Charter .null is Chartered to be used similarly to how you might use a DNS version of Usenet's alt. hierarchy. Any member of the OpenNIC may register one .null Second-Level domain and domain allocations will be strictly first come-first served. No challenges to a domain holder on any basis other than .null policy violation or non-use of the domain will be considered.

wiki.opennic.org infrastructure

fusl@undisclosed.example.com (fusl) — Tue, 23 Apr 2019 08:59:41 +0000

wiki.opennic.org infrastructure Maintainers * fusl The Infrastructure The wiki.opennic.org website runs as simple virtual machine on Fusl's private infrastructure for open source projects shared with Archive Team and others at NFOrce in the Netherlands (Nedzone Datacenter).

Ansible Setup - old revision restored (2018-10-28T18:14:58Z)

fusl@undisclosed.example.com (fusl) — Wed, 21 Nov 2018 01:56:25 +0000

Ansible Setup Ansible is an open source project for automating the deployment and management of systems with yaml scripts, much like Puppet. This is a guide how to use the Ansible Playbook written for OpenNIC, to setup and run a Tier 2 server within just a few minutes. This guide assumes you know that you know that Ansible just needs to be installed on your local machine or the machine you use to control your other servers, and that the other servers just need to have python installed.

Why you shouldn't pick Tier 2 anycast servers - old revision restored (2018-04-18T16:58:10Z)

fusl@undisclosed.example.com (fusl) — Wed, 21 Nov 2018 01:55:36 +0000

Why you shouldn't pick Tier 2 anycast servers (-) Anycast server latency fluctuates a lot Sometimes, Tier 2 anycast servers are faster than normal Tier 2 servers, this is due to the way an anycast network works, however it could also be very slow at times due to the nature of BGP taking a shorter route path that is actually congested vs. a longer route path that is perfectly fine.

.bbs TLD - old revision restored (2017-04-07T18:27:10Z)

fusl@undisclosed.example.com (fusl) — Sun, 28 Oct 2018 15:55:40 +0000

.bbs TLD History opennic-discuss m/l (29Dec2000, From: Robin (krystal@devnull.net), Subject: OpenNIC Discuss: Sample Charters) Charter The .BBS TLD is aimed toward Bulletin Board System servers, and BBS affiliated/related/owned websites. Bulletin Board System being defined as an actual telnet accessable server, or by a website with the features typical of a BBS - Message bases, Email, Chat, etc

.bit TLD - [Contact]

CalumMc@undisclosed.example.com (CalumMc) — Fri, 19 Oct 2018 10:19:20 +0000

.bit TLD Updating time OpenNIC resolves .bit (Namecoin) domains through the use of a centralized server which generates a DNS zone from the Namecoin blockchain. A new zone is generated from the blockchain every 15 minutes, however it may take several hours for all of the public resolvers to receive the update.

FAQ - [How did OpenNIC start?]

fusl@undisclosed.example.com (fusl) — Thu, 26 Jul 2018 10:04:36 +0000

FAQ What is OpenNIC? OpenNIC is a user owned and controlled Network Information Center offering a democratic, non-national alternative to the traditional Top-Level Domain registries. Users of OpenNIC DNS servers, in addition to resolving host names in the Legacy

.pirate TLD - dotpirate.org seems to be offline

jonaharagon@undisclosed.example.com (jonaharagon) — Thu, 01 Mar 2018 00:23:16 +0000

.pirate TLD :!: Update Feb 28, 2018: The Dot Pirate organization does not appear to be in operation at the moment. Registrations are currently being handled by . FIXME This page needs an up-to-date charter. The following was copied from dotpirate.org

Tier 1 and 2 Server Operator Policies - created (nov 15 policy changes)

jonaharagon@undisclosed.example.com (jonaharagon) — Fri, 22 Dec 2017 19:42:00 +0000

Tier 1 and 2 Server Operator Policies As of November 15, 2017, server operators must adhere to the following policies. Tier 1 Operators Tier 1 Operators (the DNS Administrators for each TLD) are expected to maintain some key components of the infrastructure. Failure to meet the following minimum requirements may result in the appointment of a temporary maintainer for your

OpenNIC Mailing Lists - noting updated policies

jonaharagon@undisclosed.example.com (jonaharagon) — Fri, 22 Dec 2017 19:38:20 +0000

OpenNIC Mailing Lists The official OpenNIC mailing lists are served by Sympa at @lists.opennicproject.org. See below for descriptions of available lists and instructions for subscribing. OpenNIC Related Lists Discuss This low-volume list is for folks discussing the organization and operation of the OpenNIC project. All are welcome to subscribe. Subscribe using the

Mailing List Policies - created (nov 15 vote)

jonaharagon@undisclosed.example.com (jonaharagon) — Fri, 22 Dec 2017 19:36:33 +0000

Mailing List Policies Message Prefixes For the sake of clarity, formal Mailing List threads MUST begin with the following prefixes, depending on the content of the message: * “[DISCUSSION]”, or “[PROPOSAL]” — For formal discussions or proposals of official policies or changes that will eventually lead to a vote.

New OpenNIC TLDs - Bringing up-to-date with current policy.

jonaharagon@undisclosed.example.com (jonaharagon) — Fri, 22 Dec 2017 19:29:33 +0000

New OpenNIC TLDs How to get yourself a new TLD with OpenNIC. Prerequisites * You MUST have operated a Tier 2 DNS server continuously for at least 3 months, and said DNS server MUST be in operation while your TLD is being considered. * You should keep this

latency.png - removed

fusl@undisclosed.example.com (fusl) — Wed, 20 Sep 2017 10:11:31 +0000

latency.png - removed

fusl@undisclosed.example.com (fusl) — Wed, 20 Sep 2017 10:11:22 +0000

latency_remote.png

fusl@undisclosed.example.com (fusl) — Wed, 20 Sep 2017 10:09:06 +0000

latency_local.png - created

fusl@undisclosed.example.com (fusl) — Wed, 20 Sep 2017 10:06:09 +0000