Installing and Administering Internet Services

74 Chapter 3

Conﬁguring and Administering the BIND Name Service

Conﬁguring a Primary Master Name Server

mv /etc/named.data/named.boot /etc/named.boot

5. Copy the ﬁle /usr/examples/bind/db.cache.arpa to the

/etc/named.data directory. This ﬁle is a list of root name servers.

You can also use anonymous ftp to get the current list of root name

servers from rs.internic.net. Instructions are included in the

/usr/examples/bind/db.cache.arpa ﬁle.

6. Use the list of root name servers from the

/usr/examples/bind/db.cache.arpa ﬁle or from

rs.internic.net to update the /etc/named.data/db.cache ﬁle.

The hosts_to_named program creates this ﬁle but does not add any

data to it. The format of the db.cache ﬁle is described in “The

Primary Master Server’s Cache File” on page 76.

If your network is isolated from the Internet, contact the BIND

administrator responsible for your domain to get the names and

addresses of the root name servers.

The hosts_to_named program creates the following data ﬁles in the

directory from which it is run. These ﬁles are described in the next few

sections:

named.boot

db.cache (initially empty)

db.127.0.0

db.domain (one ﬁle for each domain speciﬁed with the -d option)

db.net (one ﬁle for each network number speciﬁed with the -n

option)

Naming these ﬁles db.name is a Hewlett-Packard convention.

You can also create these ﬁles manually using a text editor. If you choose

to create them manually, you must convert all host names to fully

qualiﬁed domain names (names containing all labels from the host to the

root, terminated with a dot; for example, indigo.div.inc.com.).

The hosts_to_named program completely rewrites the db.domain and

db.net ﬁles. All manual modiﬁcations to these ﬁles will be lost the next

time you run hosts_to_named, except changes to SOA records.

For more information, type man 1M hosts_to_named or man 1M

named at the HP-UX prompt.