HP-UX OSRA for Web Services 2.5 Blueprint and Configuration Guide

test.nameX.example.com)
The following lines were left out of the database:
172.16.118.67 hptem270.nameX.example.com hptem270
(first name not in test.nameX.example.com)
Creating "PTR" data (address to name mapping) for net 172.16.118 ...Creating "MX" (mail
exchanger) data ... Building default named.boot file ...
Building default db.cache file ...
WARNING: db.cache must be filled in with
the name(s) and address(es) of therootserver(s)
Building default boot.cacheonly for caching only servers ...
done
3. If you are using DNS forwarders to resolve names and addresses that the local named server
cannot resolve, update the db.cache file with the forwarder names. This example uses two
forwarders, so you must update the db.cache as follows:
; FILL IN THE NAMES AND ADDRESSES OF THE ROOT SERVERS
;
; . 99999999 IN NS root.server.
; root.server. 99999999 IN A ??.??.??.??
. 99999999 IN NS namX-resolver.nameX.test.net. namX-resolver.nameX.test.net. 99999999 IN A
172.243.128.51
. 99999999 IN NS namY-resolver.nameY.test.net. namY-resolver.nameY.test.net. 99999999 IN A
172.243.160.51
4. Update the options section of the named.conf file:
Specify a forwarders directive if forwarders are being used.
Specify the rrset-order directive so that equal priority MX records are returned in
round-robin order instead of random order:
#
# type domain source file
#
options {
directory "/usr/local/domain";
forwarders {
172.243.128.51;
172.243.160.51;
};
rrset-order { order cyclic; };
};
zone "0.0.127.IN-ADDR.ARPA" {
type master;
file "db.127.0.0";
};
zone "test.nameX.example.com" {
type master;
file "db.test";
};
zone "10.10.IN-ADDR.ARPA" {
type master;
file "db.10.10";
};
zone "118.16.172.IN-ADDR.ARPA" {
type master;
file "db.172.16.118";
};
zone "." {
type hint;
file "db.cache";
};
5. Start or restart the named server as follows:
a. Stop the currently running server:
# ps -eax | grep -v grep | grep named | read pid restofline
# (($?==0)) && kill $pid
b. Start the named server:
Horizontal Scaling of Web and Application Servers 31