HostedDB - Dedicated UNIX Servers

Securing-Optimizing-RH-Linux-1_2_234
Comments and suggestions concerning this book should be mailed to gmourani@videotron.ca © Copyright 1999-2000 Gerhard Mourani and Open Network Architecture ® 234 Don’t forget to copy the “db.cache” file to the “/var/named/” directory on your server where you’re installing DNS server after retrieving it over the Internet. Secondary slave name Server The purpose of a slave name server is to share the load with the master server or handles the entire load if the master server is down. A slave name server loads its data over the network from another name server (usually the master name server but can load from another slave name server too). This process is called a zone transfer. Necessary files to setup a secondary slave name server are: named.conf db.127.0.0 db.cache named script Configuration of the “/etc/named.conf” file for a slave name server Use this configuration for the server machine on your network that acts as a slave name server. You must modify the “named.conf” file on the slave name server host. Change every occurrence of primary to secondary except for “0.0.127.in-addr.arpa” and add a masters line with the IP address of the master server as show bellow. Create the named.conf file (touch /etc/named.conf) and add: options {         directory "/var/named";         fetch-glue no;         recursion no;         allow-query { 208.164.186/24; 127.0.0/8; };         allow-transfer { 208.164.186.1; };         transfer-format many-answers; }; // These files are not specific to any zone zone "." in {         type hint;         file "db.cache"; }; zone "0.0.127.in-addr.arpa" in {         type master;         file "db.127.0.0"; }; // These are our slave zone files  zone "openarch.com" in {         type slave;         file "db.openarch";         masters { 208.164.186.1; }; }; zone "186.164.208.in-addr.arpa" in {         type slave;         file "db.208.164.186";         masters { 208.164.186.1; }; };