Red Hat LINUX 7.2 Reference Manual page 229

Section 14.2:BIND Configuration Files
Figure 14–4 Example of listen-on option
options {
listen-on { 10.0.1.1; };
};
In this way, only requests that arrive from the network interface serving the private network
(10.0.1.1) will be accepted.
– notify — Controls whether named notifies the slave servers when a zone is updated. The
default is yes, but you can set this to no, to prevent slaves from being notified, or explicit,
to only notify servers in an also-notify list.
– pid-file — Allows you to specify the location of the process ID file created by named
when it starts.
– statistics-file — Allows you to specify the location of where the statistics file is
written. By default, named statistics are saved in /var/named/named.stats.
Dozens of other options are also available, many of which rely upon one another to work properly.
See the BIND 9 Administrator Reference Manual for more details.
• server — Defines particular options that affect how named should act toward remote name-
servers, especially regarding notifications and zone transfers.
The transfer-format option controls whether one resource records is send with each mes-
sage (one-answer) or multiple resource records are sent with each message (many-answers).
While many-answers is more efficient, only newer BIND nameservers understand it.
• trusted-keys — Contains assorted public keys used for DNSSEC. See Section 14.4.3, Secu-
rity for an introduction to BIND security.
• view " <view-name> " — Creates special views that respond with a particular type of infor-
mation depending upon the host contacting the nameserver. This allows some hosts to receive one
answer regarding a particular zone while other hosts receive totally different information. Alter-
natively, certain zones may only be made available to particular trusted hosts while non-trusted
hosts may still make queries for other zones.
Multiple views may be used, so long as their names are unique. The match-clients option
specifies the IP addresses that apply to a particular view. Any option statements may also be
used within a view, overriding the global options already configured for named. Most view state-
ments contain multiple zone statements that apply to the match-clients list. The order in
which view statements are listed is important, as the first view statement that matches a partic-
ular client's IP address is used.
See Section 14.4.2, Multiple Views for more information about the view statement.
229