HP-UX IP Address and Client Management Administrator's Guide HP-UX 11i v2, HP-UX 11i v3
An example named.conf configuration file for a slave server is shown in “Creating the Slave
Server’s Data Files Manually” (page 76).
For more information on hosts_to_named, type man 1M hosts_to_named at the HP-UX
prompt.
Creating the Slave Server’s Data Files Manually
To create the slave server’s data files manually, complete the following steps:
1. Copy the files /etc/named.conf, /etc/named.data/db.cache, and
/etc/named.data/db.127.0.0 from the master server to the slave server.
2. On the slave server, make the following changes to the configuration file /etc/named.conf,
using a text editor:
• For every entry in the /etc/named.conf file containing the word primary, except
the entry containing db.127.0.0, replace the word primary with the word
secondary.
• In every entry containing the word secondary, add the Internet address of the master
server after the domain name.
• If you do not want the slave server to store backup files on disk, delete the last field of
every secondary line (the field that specifies the file name).
Following are the example /etc/named.conf configuration files for a slave server.
Example 1
The following example is a named.conf configuration file for a slave server that does not store
the database information in a local file.
// generated by named-bootconf.pl
options { check-names response fail; //do not change this
check-names slave warn; directory “/etc/named.data”; //running directory for named
/* * If there is a firewall between you and nameservers you want
* to talk to, you might need to uncomment the query-source
* directive below. Previous versions of BIND always asked
* questions using port 53, but BIND 8.1 uses an
* unprivileged port by default */ // query-source address * port 53;
}; // // type domain source file // zone “0.0.127.IN.ADDR.ARPA” {
type master;
file “db.127.0.0”;
}; zone “div.inc.com”; { type slave;
masters {
15.19.8.119;
};
}; zone “8.19.15.IN-ADDR.ARPA” { type slave;
masters {
15.19.8.119;
};
}; zone “.” { type hint;
file “db.cache”;
};
Example 2
The following example is a named.conf configuration file for a slave server that stores the
database information in a local file.
// generated by named-bootconf.pl
options { check-names response fail; //do not change this
check-names slave warn; directory “/etc/named.data”; //running directory for named
/* * If there is a firewall between you and nameservers you want
* to talk to, you might need to uncomment the query-source
* questions using port 53, but BIND 8.1 uses an
* unprivileged port by default. */ // query-source address * port 53;
}; // // type domain source file // zone “0.0.127.IN.ADDR.ARPA” {
type master;
file “db.127.0.0”;
}; zone “div.inc.com”; { type slave;
file “db.div”;
76 Configuring and Administering the BIND Name Service