 |
» |
|
|
|
The boot file of a caching-only name server has no primary
or secondary lines, except the primary line for the 0.0.127.in-addr.arpa domain (the loopback interface). Hosts running
Berkeley networking use 127.0.0.1 as the address of the loopback
interface. Since 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 network 127.0.0. Follow these steps to create a caching-only server: Copy the files /etc/named.data/db.127.0.0 and /etc/named.data/db.cache from the primary server to the caching-only server. If you ran hosts_to_named to create the primary master server, hosts_to_named created a file called boot.cacheonly in the directory from which it was run. Copy this
file to the caching-only server, and rename it /etc/named.boot. If you created the primary master server manually, without
running hosts_to_named, create a boot file for the caching-only server
called /etc/named.boot. It should look like the following example: ;
; type domain source file
;
directory /etc/named.data ;running directory for named
primary 0.0.127.IN-ADDR.ARPA db.127.0.0
cache db.cache |
If you will be using 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”. You
can also configure remote name servers in /etc/resolv.conf. If you will not be using an /etc/resolv.conf file, follow these steps: Set the default domain name with the hostname command, as in the following example, /usr/bin/hostname indigo.div.inc.com |
and 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.
|
