The Configuration File /Etc/Named.conf - Novell LINUX ENTERPRISE SERVER 11 - ADMINISTRATION Administration Manual

enter host 127.0.0.1, which should always work. If you get an error message, use
rcnamed status to see whether the server is actually running. If the name server
does not start or behaves unexpectedly, you can usually find the cause in the log file
/var/log/messages.
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
in named.conf" (page 291) are just examples. Adjust these entries to your own setup.
Example 21.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 files do not need to be modified 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 configuration file /etc/named.conf or the
zone files, 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.
21.5 The Configuration File
/etc/named.conf
All the settings for the BIND name server itself are stored in the file /etc/named
.conf. However, the zone data for the domains to handle (consisting of the hostnames,
IP addresses, and so on) are stored in separate files in the /var/lib/named directory.
The details of this are described later.
Example 21.1, "Forwarding Options
The Domain Name System 291