OpenNIC Wiki : Tier2ServerConfig

• Categories
• PageIndex
• RecentChanges
• RecentlyCommented
• Login/Register
• Search:

Configuring Your Name Server

Here are some basic instructions on configuring your name server to access the OpenNIC Top-Level Domains (TLDs). This page has, at the moment, instructions for only a limited range of nameservers. If you've configured another DNS server to use OpenNIC, please post some instructions to the MailingLists discussion list (or edit this page!) so we can expand this page.

Please note that these instructions are for configuring a nameserver as an OpenNIC Tier 2 server or for your own use. Configuration of an Tier1ServerConfig OpenNIC Tier 1 server is significantly different. You should ask the MailingLists mailing list for advice.

General Information

OpenNIC is a simple addition to the BIND configuration file to inform your name server of the new Top-Level Domains (TLDs) administered by OpenNIC. What this does, basically, is set your server back to the old days when that file was a cache of pointers to the root servers. BIND these days just uses that cache as a list of servers to query at startup for up-to-date root lists, but we don't have to do that.

Note: In any place in the information below where you would normally see an IP number, those numbers have been replaced with a link to the page of VolunteerHosts Public Name Servers. Please see this list to choose the appropriate server for your use.

You will also need to join the MailingLists Announcements list (or join the MailingLists Discussion list) so you'll get notified when we add new Tier 1 servers, so you can add them to the list of masters on your name server. The more widespread we get with our Tier 1 servers, the less susceptible we are to a disruption due to a network outage anywhere.

And, for the curious, here's an example TldRootFile tld-root file after we've merged the OpenNIC changes into it, along with the script that generates it.

BIND 9

Needs content...

BIND 8

Most Unix systems put the BIND 8 configuration file at either /etc/named.conf (as most Linux distributions do) or ar /var/named/named.conf (as the bind8 port installer for OpenBSD does).

In the named.conf, you should have a block that looks like this:

Change it to look like this (you can have from 1 to many entries in the "master" section; we recommend at least 3 Tier 1 servers):

BIND 4

Most Unix systems put the BIND 4 configuration file at either /etc/named.boot (as most Linux distributions do) or ar /var/named/named.boot (as the default install for OpenBSD does).

In the named.boot, you should have a line that looks like this:

Change it to look like this (please choose the nearest VolunteerHosts Tier 1 server for this):

DJBDNS

Instructions provided by Alan Hodgson, .geek hostnaster.

1) Change into your dnscache root/servers directory.

2) Replace your root servers file (root/servers/@) with the IP numbers of the VolunteerHosts OpenNIC Tier 1 servers, obtained by using dnsq to query the Tier 0 IP number (this step can be done manually, as well).

3) If it looks okay (i.e. a list of IP addresses), replace the file.

4) Restart dnscache

5) Verify that it's working

Windows 2000 DNS Server

Contributed by Michael Patrick.

1. Bring up the DNS Administrator from Administrative Tools...
2. Bring up the properties of the DNS Server
3. Go to the "Root Hints" tab
4. Remove the root server entries
5. Replace them with the Tier 1 servers from here.
6. Stop and Start the DNS service
7. If needed, clear and refresh your view of the cache and you should see .glue
8. try it out on http://www.opennic.glue.

My C:\WINNT\system32\dns\cache.dns file after modification (I would recommend keeping a copy of your file in case something bad happens to it). [And keep in mind that server IPs can change.]

Note: Many of these nameservers are no longer operational!

• [Source]
• [History]
• 2007-07-20 01:49:08
• Owner: BrianKoontz
• Your hostname is ec2-18-224-31-14.us-east-2.compute.amazonaws.com

Valid XHTML :: Valid CSS: :: Powered by WikkaWiki