Differences

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

--- opennic:srvzone [2017-04-19T02:01:22Z] – created jonaharagon
+++ opennic:srvzone [2017-07-31T17:11:04Z] – [Getting the script] Updated IP address shdwdrgn
@@ Line 3: / Line 3: @@
 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.
-Note that this configuration may be used for both Tier-1 and Tier-2 servers, as well as private servers.
+Note that this configuration may be used for both [[tier1|Tier 1]] and [[tier2|Tier 2]] servers, as well as private servers.
 ===== Getting the script =====
@@ Line 9: / Line 9: @@
 This script will automatically generate a file for BIND9 that lists all of the OpenNIC zones and their master servers. The conf file needs to be located in the same directory as the script. For convenience, you may wish to place these files in /etc/bind/ (or wherever your distribution places your BIND9 configuration). Run the following commands to download the files.
-  wget http://173.160.58.202/opennic.oss/files/scripts/srvzone
+  wget http://161.97.219.84/opennic.oss/files/scripts/srvzone
-  wget http://173.160.58.202/opennic.oss/files/scripts/srvzone.conf
+  wget http://161.97.219.84/opennic.oss/files/scripts/srvzone.conf
   chown bind.bind srvzone
   chmod 700 srvzone
-Now edit srvzone.conf with your preferred editor. You will see a section with paths for several files, which can be changed to match your configuration. The first three entries dictate where BIND will store the zone files. Note that file_master does not apply to Tier-2 servers. In the example paths given, note that $TLD will be expanded to each zone name as it is created -- so for example the string "$TLD.zone" would save the .geek zone as "geek.zone". The destination variable indicated where you want the final zone configuration file to be stored, and tmp_dest is just a temporary location to create new files.
+Now edit srvzone.conf with your preferred editor. You will see a section with paths for several files, which can be changed to match your configuration. The first three entries dictate where BIND will store the zone files. Note that file_master does not apply to Tier 2 servers. In the example paths given, note that $TLD will be expanded to each zone name as it is created -- so for example the string "$TLD.zone" would save the .geek zone as "geek.zone". The destination variable indicated where you want the final zone configuration file to be stored, and tmp_dest is just a temporary location to create new files.
 Make sure the folder where you wish to store the files has been created. In the example srvzone.conf file, zones would be stored in /etc/bind/opennic/ so you want to create that folder and change the permissions to allow your bind user full access to read and write it.