Differences

This shows you the differences between two versions of the page.

--- opennic:tier1setup [2017-12-03T16:09:00Z] – [Setting up a Tier 1 Server] adventure30
+++ opennic:tier1setup [2021-03-20T16:40:32Z] (current) – Updated root server IP Shdwdrgn
@@ Line 5: / Line 5: @@
 FIXME This legacy wiki article has been copied from http://web.archive.org/web/20161228061854/wiki.opennicproject.org/RunningT1. It is outdated and should not be blindly used for copy-pasting.  Use this information as a starting point to further researching current methods.
+But where, if not here, are those settings documented?
 ===== BIND9 setup =====
-Setting up a OpenNIC ready Tier 1 server requires your DNS to slave all the TLDs within the OpenNIC name-space. We will go through each zone below (this document will be updated as more zones are created). Alternatively, this page will show how to configure bind9 to automatically update available TLDs and their master servers.
+Setting up a OpenNIC Tier 1 server, requires creating slave zones for all the TLDs within the OpenNIC name-space.
-As you can see below, all my zones reside in ''/etc/bind/zones'' and ''/etc/bind/zones/slaves''. You will have to change that to suit your style of setup. It is also recommended you run bind in a chroot jail, and that additional Tier 1 servers are listed as masters in each zone for redundancy. Below is the root zone, add this into your ''named.conf''.
+Each zone is presented below. This document will be updated as new zones are created.
-== named.conf ==
+This page will show how to configure BIND9 to automatically update available TLDs and their master servers.
+In this example BIND9 configuration, zones are stored in directories "/etc/bind/zones" and "/etc/bind/zones/slaves".  A Tier 1 BIND9 server may be deployed using other directories.  BIND9 directories are different in different computer operating systems.
+Run BIND9 in a chroot jail.
+Tier 1 servers are listed as 'master' in each zone for redundancy.
+Begin with the '.' root zone; add the following directive statement, to the BIND9 ("named") configuration file "named.conf".
+== named.conf: ==
 <code>
 zone "." {
 	type slave;
 	file "/etc/bind/zones/db.root";
-	masters { 75.127.96.89; };
+	masters { 168.119.153.26; };
 	allow-transfer { any; };
 	notify no;
@@ Line 21: / Line 32: @@
 </code>
-Below are the zones for each OpenNIC TLD, place these in your ''named.conf''.
+Below are the zones for each OpenNIC TLD.  Add these to the //named// configuration file; "named.conf".
 == opennic.glue ==
@@ Line 28: / Line 39: @@
 	type slave;
 	file "/etc/bind/zones/slaves/glue.zone";
-	masters { 75.127.96.89; };
+	masters { 168.119.153.26; };
 	allow-transfer { any; };
 	notify no;
@@ Line 39: / Line 50: @@
 	type slave;
 	file "/etc/bind/zones/slaves/dns.glue.zone";
-	masters { 75.127.96.89; };
+	masters { 168.119.153.26; };
 	allow-transfer { any; };
 	notify no;
@@ Line 295: / Line 306: @@
 </code>
-I hope that this guide has assisted getting your Tier 1 server ready for your new TLD. Remember to follow the insturctions on creating a new TLD if you have not already had your TLD approved for use within OpenNIC by vote of the membership. [[opennic:creating_new_tlds]]
+I hope (likely in vain) that this guide has assisted (even though the the preface states that it is totally outdated) getting your Tier 1 server ready for your new TLD.
+Remember to follow the instructions on creating a new TLD in case you have not yet had your TLD approved for use within OpenNIC by vote of the membership. [[opennic:creating_new_tlds]]