HP-UX IP Address and Client Management Administrator's Guide HP-UX 11i v2, HP-UX 11i v3

masters {
15.19.8.119;
};
}; zone “8.19.15.IN-ADDR.ARPA” { type slave;
file
“db.15.19.8”; masters {
15.19.8.119;
};
}; zone “.” { type hint;
file “db.cache”;
};
In this example, the slave server uses the file db.div to store the database information. The slave
server uses this file as a backup file. When the slave server reboots, it reads the authoritative
data from the backup file, and later contacts the master server to verify the data. If the master
server contains new data, the slave server saves this new data in the backup file.
The format of the data files copied from the master server is described in “Configuring a Master
Name Server” (page 66).
Setting the Default Domain Name
You can initialize the default domain name either by specifying the domain name in the
/etc/resolv.conf file or by specifying the host name using the hostname command in the
/etc/rc.config.d/netconf file.
If you use an /etc/resolv.conf file on your host, configure the default domain name with
the search or domain keyword. See “Configuring the Resolver to Query a Remote Name Server”
(page 78).
If you do not use an /etc/resolv.conf file to configure the default domain name, follow
these steps:
1. Set the default domain name with the hostname command by appending the domain name
to the host name. For example, type the following at the HP-UX prompt to set the default
host name to indigo.div.inc.com:
/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:
Configuring the Caching-Only Name Server 77