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

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. 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
* 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 “.” { type hint;
file “db.cache”;
};
3. 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:
a. 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
/usr/bin/hostname
indigo.div.inc.com
b. 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
Do not put a trailing dot at the end of the domain name.
Your default domain is now set.
Configuring the Resolver to Query a Remote Name Server
A name server constitutes the server portion of BIND’s client/server mechanism. Resolvers are
clients that access the name server. Name servers contain complete information about a particular
network segment. Resolvers are library routines that create queries and send them across a
network to a name server. A resolver translates a program’s request for host information into a
query, sends the query to a name server, and translates the response into an answer. Programs
running on a host use a resolver to obtain information about a domain.
A resolver can perform the following functions:
• Query a name server.
• Interpret a response.
• Return the information to the program.
A resolver allows you to configure three aspects of its behavior: the default domain, the search
list, and the name servers that the resolver queries.
78 Configuring and Administering the BIND Name Service