<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="https://wiki.opennic.org/lib/exe/css.php?s=feed" type="text/css"?>
<rss version="2.0">
    <channel xmlns:g="http://base.google.com/ns/1.0">
        <title>OpenNIC Wiki</title>
        <description></description>
        <link>https://wiki.opennic.org/</link>
        <lastBuildDate>Thu, 22 Oct 2026 15:54:36 +0000</lastBuildDate>
        <generator>FeedCreator 1.8</generator>
        <image>
            <url>https://wiki.opennic.org/_media/wiki/dokuwiki.svg</url>
            <title>OpenNIC Wiki</title>
            <link>https://wiki.opennic.org/</link>
        </image>
        <item>
            <title>.null TLD - removed - external edit (Unknown date)</title>
            <link>https://wiki.opennic.org/dot/null?rev=1792559034&amp;do=diff</link>
            <description>.null TLD

Charter

.null is Chartered to be used similarly to how you might use a DNS version of Usenet&#039;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.</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Wed, 21 Oct 2026 05:03:54 +0000</pubDate>
        </item>
        <item>
            <title>.fur TLD - removed - external edit (Unknown date)</title>
            <link>https://wiki.opennic.org/dot/fur?rev=1792557254&amp;do=diff</link>
            <description>.fur TLD

Overview

The Top Level Domain “fur” is provided by FurNIC. FurNIC peers with OpenNIC to mutually provide access to the Top Level Domains of the other party.

History

There was a Top Level Domain “fur” in OpenNIC proper several years ago.</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Wed, 21 Oct 2026 04:34:14 +0000</pubDate>
        </item>
        <item>
            <title>.bit TLD - removed - external edit (Unknown date)</title>
            <link>https://wiki.opennic.org/dot/bit?rev=1792556770&amp;do=diff</link>
            <description>.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. If, after several hours, you are still not able to resolve your domain, please contact me using the information here.</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Wed, 21 Oct 2026 04:26:10 +0000</pubDate>
        </item>
        <item>
            <title>.oss TLD - removed - external edit (Unknown date)</title>
            <link>https://wiki.opennic.org/dot/oss?rev=1792553434&amp;do=diff</link>
            <description>.oss TLD

Charter

.oss is reserved exclusively for Open Source Software projects.

Contacts

	*  Administrator - JeffTaylor
	*  Hostmaster - hostmaster@opennic.oss
	*  Abuse - abuse@opennic.oss
	*  Web Site - &lt;http://reg.oss/&gt;

Domain Registration

	*  Website - &lt;http://reg.oss/&gt;
	*</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Wed, 21 Oct 2026 03:30:34 +0000</pubDate>
        </item>
        <item>
            <title>.o TLD - removed - external edit (Unknown date)</title>
            <link>https://wiki.opennic.org/dot/o?rev=1792552255&amp;do=diff</link>
            <description>.o TLD

Charter

This is a summary of the charter. See www.moderntld.com/about/charter for details.

The .o TLD, operated by the ModernTLD administration, is to be used by commercial and non-commercial entities (individual or groups) to promote themselves on the OpenNIC free network. This domain is intended to be used in a general sense, akin to .com in the ICANN network, and as such has a very general use case and little restrictions on registration. Registration is available on a first-come, f…</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Wed, 21 Oct 2026 03:10:55 +0000</pubDate>
        </item>
        <item>
            <title>.oz TLD - removed - external edit (Unknown date)</title>
            <link>https://wiki.opennic.org/dot/oz?rev=1792551312&amp;do=diff</link>
            <description>.oz TLD

General Description

dot OZ is the TLD (Top Level Domain) custom made for Australians, but still available to everyone. dot OZ is targeted to those who may want a domain with the cultural association with Australia, but without the requirements of .com.au, net.au or org.au registrations.</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Wed, 21 Oct 2026 02:55:12 +0000</pubDate>
        </item>
        <item>
            <title>Automated DNS Server Testing - removed - external edit (Unknown date)</title>
            <link>https://wiki.opennic.org/automateddnsservertesting?rev=1792550769&amp;do=diff</link>
            <description>Automated DNS Server Testing

Every 15 minutes, full testing is performed on each publicly listed Tier 2 server. The results and history of this testing may be viewed from here. You can view either Tier 1 or Tier 2 server results, and filter the display based on region. This information may be helpful in choosing reliable servers near you.</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Wed, 21 Oct 2026 02:46:09 +0000</pubDate>
        </item>
        <item>
            <title>.bbs TLD - removed - external edit (Unknown date)</title>
            <link>https://wiki.opennic.org/dot/bbs?rev=1792547122&amp;do=diff</link>
            <description>.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</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Wed, 21 Oct 2026 01:45:22 +0000</pubDate>
        </item>
        <item>
            <title>.free TLD - removed - external edit (Unknown date)</title>
            <link>https://wiki.opennic.org/dot/free?rev=1792545993&amp;do=diff</link>
            <description>.free TLD

Charter

THE FREENIC ACCEPTABLE USE POLICY, TERMS AND CONDITIONS

Mission

The FreeNIC provides NAMESPACE, CERT AUTH and other services to its membership and to the general public to encourage the NON-COMMERCIAL USE of the Free Internet and the existing and future INTERNET infrastructure. For-profit organizations are permitted to use the Free Internet but must uphold the policy of NON-COMMERCIAL USE as detailed in the AUP. Commercial use for all other purposes is not acceptable and vi…</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Wed, 21 Oct 2026 01:26:33 +0000</pubDate>
        </item>
        <item>
            <title>dokuwiki-128.png - created - external edit</title>
            <link>https://wiki.opennic.org/?image=wiki%3Adokuwiki-128.png&amp;ns=wiki&amp;rev=1788375207&amp;tab_details=history&amp;media_do=diff&amp;do=media</link>
            <description>&lt;img src=&quot;https://wiki.opennic.org/_media/wiki/dokuwiki-128.png?w=500&amp;amp;h=500&amp;amp;tok=499250&quot; alt=&quot;dokuwiki-128.png&quot; loading=&quot;lazy&quot; width=&quot;500&quot; height=&quot;500&quot; /&gt;</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Wed, 02 Sep 2026 18:53:27 +0000</pubDate>
        </item>
        <item>
            <title>Welcome to the OpenNIC Wiki - [OpenNIC Search Engines] </title>
            <link>https://wiki.opennic.org/start?rev=1787928300&amp;do=diff</link>
            <description>Welcome to the OpenNIC Wiki

About OpenNIC

OpenNIC (also referred to as the OpenNIC Project) is a user owned and controlled top-level Network Information Center offering a non-national alternative to traditional Top-Level Domain (TLD) registries; such as</description>
            <author>intranic@undisclosed.example.com (intranic)</author>
            <pubDate>Fri, 28 Aug 2026 14:45:00 +0000</pubDate>
        </item>
        <item>
            <title>OpenNIC Operated Top-Level Domains - Removed as IntraNIC will not be peering with OpenNIC</title>
            <link>https://wiki.opennic.org/opennic/dot?rev=1787928279&amp;do=diff</link>
            <description>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.</description>
            <author>intranic@undisclosed.example.com (intranic)</author>
            <pubDate>Fri, 28 Aug 2026 14:44:39 +0000</pubDate>
        </item>
        <item>
            <title>Setting up a Tier 1 Server - added .o, and fixed .micro master</title>
            <link>https://wiki.opennic.org/opennic/tier1setup?rev=1787492506&amp;do=diff</link>
            <description>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 &lt;http://web.archive.org/web/20161228061854/wiki.opennicproject.org/RunningT1&gt;. It is outdated and should not be blindly used for copy-pasting.  Use this information as a starting point to further researching current methods.</description>
            <author>intranic@undisclosed.example.com (intranic)</author>
            <pubDate>Sun, 23 Aug 2026 13:41:46 +0000</pubDate>
        </item>
        <item>
            <title></title>
            <link>https://wiki.opennic.org/user/0x58656e61?rev=1785901487&amp;do=diff</link>
            <description>I have a DNS server at 50.117.253.214 (kneesurgery.moe) which is located in Yellowknife, NT, Canada.
It&#039;s the same as a Tier 2 server but I don&#039;t know if I&#039;m allowed to call it that since it isn&#039;t in the servers list due to Yellowknife being an invalid location or something.</description>
            <author>0x58656e61@undisclosed.example.com (0x58656e61)</author>
            <pubDate>Wed, 05 Aug 2026 03:44:47 +0000</pubDate>
        </item>
        <item>
            <title> - removed</title>
            <link>https://wiki.opennic.org/user/furyashnyy?rev=1781730379&amp;do=diff</link>
            <description></description>
            <author>Furyashnyy@undisclosed.example.com (Furyashnyy)</author>
            <pubDate>Wed, 17 Jun 2026 21:06:19 +0000</pubDate>
        </item>
        <item>
            <title>.o TLD</title>
            <link>https://wiki.opennic.org/opennic/dot/o?rev=1781642848&amp;do=diff</link>
            <description>.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.</description>
            <author>EMREOYUN@undisclosed.example.com (EMREOYUN)</author>
            <pubDate>Tue, 16 Jun 2026 20:47:28 +0000</pubDate>
        </item>
        <item>
            <title> - use delegation signer (DS) instead of DNSKEY</title>
            <link>https://wiki.opennic.org/systemd-resolve-daemon?rev=1778402094&amp;do=diff</link>
            <description>Since Debian 13 ”Trixie”, the resolv.conf is generated by the systemd-resolved, the systemd Resolver Daemon.

To get an overview over the currently configured resolvers we run the resolvectl command:
root@machine:~# resolvectl
Global
         Protocols: +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
  resolv.conf mode: stub
       DNS Servers: 127.0.0.1 ::1</description>
            <author>joestr1@undisclosed.example.com (joestr1)</author>
            <pubDate>Sun, 10 May 2026 08:34:54 +0000</pubDate>
        </item>
        <item>
            <title>DNSSEC Validation - update current keys and samples</title>
            <link>https://wiki.opennic.org/opennic/dnssec?rev=1777484974&amp;do=diff</link>
            <description>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&#039;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</description>
            <author>joestr1@undisclosed.example.com (joestr1)</author>
            <pubDate>Wed, 29 Apr 2026 17:49:34 +0000</pubDate>
        </item>
        <item>
            <title></title>
            <link>https://wiki.opennic.org/user/joestr1?rev=1776757012&amp;do=diff</link>
            <description>My name is Joel.

You can reach me via e-mail. :)

I am operating a Tier 2 server in Austria.</description>
            <author>joestr1@undisclosed.example.com (joestr1)</author>
            <pubDate>Tue, 21 Apr 2026 07:36:52 +0000</pubDate>
        </item>
        <item>
            <title>OpenNIC Compatible Webspace Providers - add note to KeyHelp</title>
            <link>https://wiki.opennic.org/webspaceproviders?rev=1776756901&amp;do=diff</link>
            <description>OpenNIC Compatible Webspace Providers

Requirements for listing

	*  Provider needs to accept free or paid sign-ups using an automated or semi-automated sign-up form, no closed/invite-only groups
	*  Paid-only providers need to have “paid-only” included in the notes section</description>
            <author>joestr1@undisclosed.example.com (joestr1)</author>
            <pubDate>Tue, 21 Apr 2026 07:35:01 +0000</pubDate>
        </item>
        <item>
            <title>__DrMmPro__ - created</title>
            <link>https://wiki.opennic.org/user/drmmpro?rev=1769696001&amp;do=diff</link>
            <description>__DrMmPro__

Drmmpro

	*  drmmpro</description>
            <author>drmmpro@undisclosed.example.com (drmmpro)</author>
            <pubDate>Thu, 29 Jan 2026 14:13:21 +0000</pubDate>
        </item>
        <item>
            <title>Professor J.Thesmos - created</title>
            <link>https://wiki.opennic.org/user/proasia?rev=1769661435&amp;do=diff</link>
            <description>Professor J.Thesmos

Introduction

	*  Professor John Thesmos
	*  proasia
	*  Github</description>
            <author>proasia@undisclosed.example.com (proasia)</author>
            <pubDate>Thu, 29 Jan 2026 04:37:15 +0000</pubDate>
        </item>
        <item>
            <title> - Update ip used by dig, since 75.127.96.89 has been down since at least 2020 (https://github. ...</title>
            <link>https://wiki.opennic.org/tier_2_unbound?rev=1767636474&amp;do=diff</link>
            <description>This simple config excerpt should be used as a basis for a Tier 2 Unbound installation:


server:
    access-control: 0.0.0.0/0 allow
    hide-identity: yes
    hide-trustanchor: yes
    hide-version: yes
    interface: x.x.x.x
    minimal-responses: yes
    log-queries: no
    root-hints: &quot;/usr/local/etc/unbound/opennic.cache&quot;
    
    # ratelimiting examples
    ip-ratelimit-factor: 0
    ip-ratelimit: 20
    ratelimit-below-domain: gov 30
    ratelimit: 100

    # See https://nlnetlabs.nl/doc…</description>
            <author>luana@undisclosed.example.com (luana)</author>
            <pubDate>Mon, 05 Jan 2026 18:07:54 +0000</pubDate>
        </item>
        <item>
            <title></title>
            <link>https://wiki.opennic.org/user/pangea?rev=1742486150&amp;do=diff</link>
            <description>Depracated... Project no longer active.</description>
            <author>pangea@undisclosed.example.com (pangea)</author>
            <pubDate>Thu, 20 Mar 2025 15:55:50 +0000</pubDate>
        </item>
        <item>
            <title>TLS Certificates - Update Debian instructions</title>
            <link>https://wiki.opennic.org/opennic/tls?rev=1736528996&amp;do=diff</link>
            <description>TLS Certificates

Current deployment

There is an experimental acme server in place at &lt;https://playground.acme.libre&gt; 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</description>
            <author>koala@undisclosed.example.com (koala)</author>
            <pubDate>Fri, 10 Jan 2025 17:09:56 +0000</pubDate>
        </item>
        <item>
            <title>Resources - [Web Resources] </title>
            <link>https://wiki.opennic.org/wiki/resources?rev=1728184675&amp;do=diff</link>
            <description>Resources

This page should give you a head-start on what to do with the OpenNIC domain name system.

Web Resources

A more complete list can be found here: Web Resources
 OpenNIC Domain Name  ICANN Domain Nmae  Category  Description  &lt;http://grep.geek&gt;  -  Search Engine  Search engine for web pages as part of the OpenNIC project</description>
            <author>shroom@undisclosed.example.com (shroom)</author>
            <pubDate>Sun, 06 Oct 2024 03:17:55 +0000</pubDate>
        </item>
        <item>
            <title>gp68</title>
            <link>https://wiki.opennic.org/user/gp68?rev=1725361964&amp;do=diff</link>
            <description>gp68

I prefer open solutions and open sources.
That&#039;s why I like opennic.

Contact:

IRC! 

Just look out for a guy called the_old_p and it&#039;s very likely to be me.

Email: the-old-p@proton.me

What does he do?

	*  Programming with
		*  Assembler 
		*</description>
            <author>gp68@undisclosed.example.com (gp68)</author>
            <pubDate>Tue, 03 Sep 2024 11:12:44 +0000</pubDate>
        </item>
        <item>
            <title>Unbound Howto</title>
            <link>https://wiki.opennic.org/user/gp68/unbound?rev=1725361439&amp;do=diff</link>
            <description>Unbound Howto

This setup is build as an example to work as tier1 or tier2 server. 

There is an update script which sets up all slave zones and does an tier1 anmd tiar2 server test after update. 

The update script also checks dnssec basics and updates the files in git.</description>
            <author>gp68@undisclosed.example.com (gp68)</author>
            <pubDate>Tue, 03 Sep 2024 11:03:59 +0000</pubDate>
        </item>
        <item>
            <title>Web Resources - created</title>
            <link>https://wiki.opennic.org/wiki/resources/web?rev=1696724061&amp;do=diff</link>
            <description>Web Resources
Work in progress
We scraped the OpenNIC web space and found a total of `n*` active websites.

This page should give you plenty of insights into the web part of OpenNIC.
 OpenNIC Domain Name  ICANN Domain Name  Category  Description  &lt;http://be.libre&gt;  -</description>
            <author>pangea@undisclosed.example.com (pangea)</author>
            <pubDate>Sun, 08 Oct 2023 00:14:21 +0000</pubDate>
        </item>
        <item>
            <title>Automatic OpenNIC Zone Generation</title>
            <link>https://wiki.opennic.org/opennic/srvzone?rev=1687088872&amp;do=diff</link>
            <description>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.</description>
            <author>resingm@undisclosed.example.com (resingm)</author>
            <pubDate>Sun, 18 Jun 2023 11:47:52 +0000</pubDate>
        </item>
        <item>
            <title>Olde16 - [Find me on:] </title>
            <link>https://wiki.opennic.org/user/olde16?rev=1675947176&amp;do=diff</link>
            <description>Olde16

Hi there!

What do I do here?

I host Tier 2 servers for everyone to use!

 OpenNIC Domain  ICANN Domain  Features  Ports  Info  ns33.de  dns3.dns-ga.de  DoT  53,853  Use DoH via &lt;https://secure-dns.dns-ga.de/dns-query&gt;  ns5.de  dns2.dns-ga.de  DoT,DoH,DNSCrypt  53,443,853,10053  Use</description>
            <author>Olde16@undisclosed.example.com (Olde16)</author>
            <pubDate>Thu, 09 Feb 2023 12:52:56 +0000</pubDate>
        </item>
        <item>
            <title>OpenNIC TLD/Root Servers - [Zone Authoritative Servers] </title>
            <link>https://wiki.opennic.org/opennic/tld-servers?rev=1674415482&amp;do=diff</link>
            <description>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.</description>
            <author>Olde16@undisclosed.example.com (Olde16)</author>
            <pubDate>Sun, 22 Jan 2023 19:24:42 +0000</pubDate>
        </item>
        <item>
            <title>OpenNIC Infrastructure - Added a few links to spice it up a little</title>
            <link>https://wiki.opennic.org/opennic/start?rev=1674413858&amp;do=diff</link>
            <description>OpenNIC Infrastructure

OpenNIC infrastructure related wiki pages

→ Root Servers and TLD Servers

→ Tier 1 Servers

→ Tier 2 Servers

→ Namespaces / Zones</description>
            <author>Olde16@undisclosed.example.com (Olde16)</author>
            <pubDate>Sun, 22 Jan 2023 18:57:38 +0000</pubDate>
        </item>
        <item>
            <title>BIND9 Zone Configuration - [/etc/bind/db.opennic]  Updated name servers</title>
            <link>https://wiki.opennic.org/opennic/t2slaved/zonefile?rev=1672772904&amp;do=diff</link>
            <description>BIND9 Zone Configuration

Tier 1 Server

Tier 2 Server

/etc/bind/named.conf.local




view &quot;opennic&quot; {
        allow-query { any; };
        match-clients { any; };
        recursion yes;
        max-cache-size 30%;

######################################## ROOT OPENNIC
        zone &quot;.&quot; {
                type secondary;
                file &quot;/etc/bind/zones/slaves/db.root&quot;;
                masters { 195.201.99.61; 168.119.153.26; };
                allow-transfer { any; };
                notif…</description>
            <author>Olde16@undisclosed.example.com (Olde16)</author>
            <pubDate>Tue, 03 Jan 2023 19:08:24 +0000</pubDate>
        </item>
        <item>
            <title>Slaved Zones with BIND9 - Updated Page, Added cosmetics, rewritten a few sentences to include ...</title>
            <link>https://wiki.opennic.org/opennic/t2slaved?rev=1669554145&amp;do=diff</link>
            <description>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</description>
            <author>Olde16@undisclosed.example.com (Olde16)</author>
            <pubDate>Sun, 27 Nov 2022 13:02:25 +0000</pubDate>
        </item>
        <item>
            <title>Keep in Mind - Added uses </title>
            <link>https://wiki.opennic.org/user/eddiethealien?rev=1667019445&amp;do=diff</link>
            <description>**Eddie The Alien**

----------

### DewBoy System ###

----------

a fake persona maker and db
--
GOALS

	*  Automate the creation of fake personas
	*  Make the management of fake personas easier
	*  Use these personas for various purposes

	*  osnit</description>
            <author>eddieTheAlien@undisclosed.example.com (eddieTheAlien)</author>
            <pubDate>Sat, 29 Oct 2022 04:57:25 +0000</pubDate>
        </item>
        <item>
            <title> - old revision restored (2021-11-30T13:23:00Z)</title>
            <link>https://wiki.opennic.org/user/eleix?rev=1638361075&amp;do=diff</link>
            <description>Eleix

PGP Fingerprint: 337bbed7052979f31917319afde753bbf811730d

Associated Accounts
Discord: Rix #1010
IRC: eleix
Mailing Lists: boothf
Servers
ns8.ca.dns.opennic.glue     IPv4: 198.50.135.212  IPv6: 2607:5300:203:7f27:5054:ff:fe57:4a07 Hostname:ns8.ca.dns.opennic.caramelfox.net
ICANN Root Mirror           IPv4: 198.50.135.208  IPv6: 2607:5300:203:7f27:5054:ff:fe45:85b5 Hostname:root.dns.caramelfox.net</description>
            <author>megan@undisclosed.example.com (megan)</author>
            <pubDate>Wed, 01 Dec 2021 12:17:55 +0000</pubDate>
        </item>
        <item>
            <title> - old revision restored (2021-11-30T12:09:02Z)</title>
            <link>https://wiki.opennic.org/user/fusl?rev=1638361061&amp;do=diff</link>
            <description>[root@fusl ~]# cat /etc/motd
 _____ _     _        _        _____          _
|_   _| |__ (_)___   (_)___   |  ___|   _ ___| |
  | | | &#039;_ \| / __|  | / __|  | |_ | | | / __| |
  | | | | | | \__ \  | \__ \  |  _|| |_| \__ \ |
  |_| |_| |_|_|___/  |_|___/  |_|   \__,_|___/_|

[root@fusl ~]# whoami
Hi, I&#039;m Katie (nickname Fusl)

[root@fusl ~]# whereis fusl
fusl: /universe/observable_universe/laniakea_supercluster/virgo_supercluster/local_sheet/local_group/milky_way_subgroup/milky_way/orion_arm/gould…</description>
            <author>megan@undisclosed.example.com (megan)</author>
            <pubDate>Wed, 01 Dec 2021 12:17:41 +0000</pubDate>
        </item>
        <item>
            <title> - old revision restored (2021-11-30T12:02:45Z)</title>
            <link>https://wiki.opennic.org/user/okashi_o?rev=1638361040&amp;do=diff</link>
            <description>Sup, I run .epic I guess.

Email: okashi@okashi.me

Website: &lt;https://okashi.me&gt;</description>
            <author>megan@undisclosed.example.com (megan)</author>
            <pubDate>Wed, 01 Dec 2021 12:17:20 +0000</pubDate>
        </item>
        <item>
            <title> - ↷ Page name changed from webspaceprovidero to webspaceproviders</title>
            <link>https://wiki.opennic.org/webspaceprovidero?rev=1638360948&amp;do=diff</link>
            <description></description>
            <author>megan@undisclosed.example.com (megan)</author>
            <pubDate>Wed, 01 Dec 2021 12:15:48 +0000</pubDate>
        </item>
        <item>
            <title> - removed</title>
            <link>https://wiki.opennic.org/user/yoshi15?rev=1638278619&amp;do=diff</link>
            <description></description>
            <author>Vip00722@undisclosed.example.com (Vip00722)</author>
            <pubDate>Tue, 30 Nov 2021 13:23:39 +0000</pubDate>
        </item>
        <item>
            <title>BIND Whitelist - [BIND-whitelist-9.3.4-P1.README] </title>
            <link>https://wiki.opennic.org/bind_whitelist?rev=1638274246&amp;do=diff</link>
            <description>BIND Whitelist

BIND-whitelist is a version-specific patch for BIND that implements whitelist functionality. It uses a very fast Berkeley database backend to track and whitelist IPs (both IPv4 and IPv6) that routinely query OpenNIC TLDs. So long as a specific IP queries for OpenNIC</description>
            <author>Vip00722@undisclosed.example.com (Vip00722)</author>
            <pubDate>Tue, 30 Nov 2021 12:10:46 +0000</pubDate>
        </item>
        <item>
            <title> - ↷ Page name changed from webspaceprovider to webspaceprovidero</title>
            <link>https://wiki.opennic.org/webspaceprovider?rev=1638273471&amp;do=diff</link>
            <description></description>
            <author>Vip00722@undisclosed.example.com (Vip00722)</author>
            <pubDate>Tue, 30 Nov 2021 11:57:51 +0000</pubDate>
        </item>
        <item>
            <title>Getting Help</title>
            <link>https://wiki.opennic.org/help?rev=1637097783&amp;do=diff</link>
            <description>Getting Help

OpenNIC provides various contact methods when you need help getting started or just want to chat. Currently those contact methods are:

	*  Mailing List: discuss@lists.opennicproject.org
	*  IRC: #opennic on the Libera IRC network
	*  Traditional Email: &lt;support@opennicproject.org&gt;</description>
            <author>stephanj@undisclosed.example.com (stephanj)</author>
            <pubDate>Tue, 16 Nov 2021 21:23:03 +0000</pubDate>
        </item>
        <item>
            <title>Setting up OpenNIC</title>
            <link>https://wiki.opennic.org/setup?rev=1625770235&amp;do=diff</link>
            <description>Setting up OpenNIC

	*  Setting up OpenNIC on macOS
	*  Setting up OpenNIC on Windows 7, 8, 10
	*  to setup on OpenWRT go to interfaces -&gt; WAN -&gt; Advanced. Then uncheck “get DNS from server” and enter PASS tier 1 and-or tier 2 IP&#039;s from servers.opennic.org</description>
            <author>liberit@undisclosed.example.com (liberit)</author>
            <pubDate>Thu, 08 Jul 2021 18:50:35 +0000</pubDate>
        </item>
        <item>
            <title>RogueScholar - Created my user page</title>
            <link>https://wiki.opennic.org/user/roguescholar?rev=1607782659&amp;do=diff</link>
            <description>RogueScholar

PGP Fingerprint: DD3F 5DEC 271F AA1D 2F11 82D1 AC77 588D 3F3B CA1E
  Associated Accounts    Keybase:  rscholar    GitHub:  RogueScholar    Twitter:  SingularErgoSum</description>
            <author>RogueScholar@undisclosed.example.com (RogueScholar)</author>
            <pubDate>Sat, 12 Dec 2020 14:17:39 +0000</pubDate>
        </item>
        <item>
            <title>Local BIND Caching Server - updated util ips</title>
            <link>https://wiki.opennic.org/opennic/t2hints?rev=1606419099&amp;do=diff</link>
            <description>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</description>
            <author>fusl@undisclosed.example.com (fusl)</author>
            <pubDate>Thu, 26 Nov 2020 19:31:39 +0000</pubDate>
        </item>
        <item>
            <title>Welcome to your new DokuWiki - removed</title>
            <link>https://wiki.opennic.org/wiki/welcome?rev=1597599671&amp;do=diff</link>
            <description>Welcome to your new DokuWiki

Congratulations, your wiki is now up and running. Here are a few more tips to get you started.

Enjoy your work with DokuWiki,

-- the developers

Create your first pages

Your wiki needs to have a start page. As long as it doesn&#039;t exist, this link will be red:</description>
            <author>fusl@undisclosed.example.com (fusl)</author>
            <pubDate>Sun, 16 Aug 2020 17:41:11 +0000</pubDate>
        </item>
        <item>
            <title>.gopher TLD - [Contacts] </title>
            <link>https://wiki.opennic.org/opennic/dot/gopher?rev=1597330911&amp;do=diff</link>
            <description>.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.</description>
            <author>Starbaby75 @undisclosed.example.com (Starbaby75 )</author>
            <pubDate>Thu, 13 Aug 2020 15:01:51 +0000</pubDate>
        </item>
        <item>
            <title>.dyn TLD - [Example Script] HTTPS instead of HTTP</title>
            <link>https://wiki.opennic.org/opennic/dot/dyn?rev=1596629600&amp;do=diff</link>
            <description>.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.</description>
            <author>Stemby@undisclosed.example.com (Stemby)</author>
            <pubDate>Wed, 05 Aug 2020 12:13:20 +0000</pubDate>
        </item>
    </channel>
</rss>
