Operation Manual

To use the name server of the provider (or one already running on your network) as the
forwarder, enter the corresponding IP address or addresses in the options section
under forwarders. The addresses included in Example 25.1, “Forwarding Options
in named.conf” (page 434) are just examples. Adjust these entries to your own setup.
Example 25.1
Forwarding Options in named.conf
options {
directory "/var/lib/named";
forwarders { 10.11.12.13; 10.11.12.14; };
listen-on { 127.0.0.1; 192.168.1.116; };
allow-query { 127/8; 192.168/16 };
notify no;
};
The options entry is followed by entries for the zone, localhost, and
0.0.127.in-addr.arpa. The type hint entry under “.” should always be
present. The corresponding les do not need to be modied and should work as they
are. Also make sure that each entry is closed with a “;” and that the curly braces are in
the correct places. After changing the conguration le /etc/named.conf or the
zone les, tell BIND to reread them with rcnamed reload. Achieve the same by
stopping and restarting the name server with rcnamed restart. Stop the server at
any time by entering rcnamed stop.
25.5 The /etc/named.conf
Conguration File
All the settings for the BIND name server itself are stored in the /etc/named.conf
le. However, the zone data for the domains to handle (consisting of the hostnames,
IP addresses, and so on) are stored in separate les in the /var/lib/named directory.
The details of this are described later.
/etc/named.conf is roughly divided into two areas. One is the options section
for general settings and the other consists of zone entries for the individual domains.
A logging section and acl (access control list) entries are optional. Comment lines
begin with a # sign or //. A minimal /etc/named.conf is shown in Example 25.2,
“A Basic /etc/named.conf” (page 435).
434 Reference