HP-UX IP Address and Client Management Administrator's Guide (October 2009)

/usr/bin/hostname indigo.div.inc.com
Do not put a trailing dot at the end of the domain name.
2. Set the HOSTNAME variable in the /etc/rc.config.d/netconf file to the same value, as
in the following example:
HOSTNAME=indigo.div.inc.com
Your default domain is now set.
Configuring the Caching-Only Name Server
A caching-only name server is a name server not authoritative for any domain except
0.0.127.in-addr.arpa. The only function that a caching-only server performs is to look up
data and cache it. The caching-only name server has only one primary entry for the
0.0.127.in-addr.arpa domain (the loopback interface) in the configuration file, and does
not have any other entries for primary and secondary.
Every time a caching-only server queries other name servers and receives an answer, it caches
the responses. Over a period of time, the cache grows to include answers to almost all the queries
requested by resolvers querying the caching-only name server. Because the information is not
stored in the local files, the additional overhead of zone transfers is not necessary.
Hosts running Berkeley networking use 127.0.0.1 as the address of the loopback interface. Because
the network number 127.0.0 is not assigned to any one site but is used by all hosts running
Berkeley networking, each name server must be authoritative for the network 127.0.0.
To create a caching-only server, complete the following steps:
1. Copy the files /etc/named.data/db.127.0.0 and /etc/named.data/db.cache from
the master server to the caching-only server.
2. Execute the more command on the /etc/named.data/db.127.0.0 file copied from the
master server. The following output is displayed:
# more db.127.0.0
$TTL 86400
@ IN SOA myhostname.mydomain.com. root.myhostname.mydomain.com. (
1 ; Serial
10800 ; Refresh every 3 hours
3600 ; Retry every hour
604800 ; Expire after a week
86400 ) ; Minimum ttl of 1 day
IN NS myhostname.mydomain.com.
1 IN PTR localhost.
In this output, the value for myhostname refers to the hostname of the master server on
which the hosts_to_named command was originally run. Replace this value with the
hostname of the caching-only server (the local machine).
Another alternative would be to replace myhostname.mydomain.com with localhost.
3. When you run the hosts_to_named command to create the master server configuration
files, a file conf.cacheonly is created in the working directory of hosts_to_named.
Copy this file to the caching-only server, and rename it /etc/named.conf.
If you have created the master server configuration files manually, without runningthe
hosts_to_named command, create the configuration file /etc/named.conf for the
caching-only server as follows:
// generated by named-bootconf.pl
options {
check-names response fail; //do not change this
check-names slave warn; //running directory for named
directory “/etc/named.data”; //running directory for named
/*
* If there is a firewall between you and nameservers you
80 Configuring and Administering the BIND Name Service