Technical data

Configuring and Managing BIND
5.3 Configuring the BIND Server (BIND 8.1)
Table 5–5 Forwarding Options
Option Description
forward This option is meaningful only if the forwarders list is not
empty.
first Causes the server to query the forwarders first. If
that does not answer the question, the server looks
for the answer itself. A ROOT.HINT file must be
present. This is the default.
only The server queries only the forwarders. A
ROOT.HINT file is not necessary.
forwarders Specifies the IP addresses to be used for forwarding. The
default is the empty list (no forwarding).
Example 5–3 shows how to specify an options statement to invoke forwarding.
Example 5–3 Forwarding Options
options {
forwarders {
1.2.3.4;
5.6.7.8;
};
forward first;
};
5.3.2.4 Name Checking
The server can check domain names based on their expected client contexts. For
example, a domain name used as a host name can be checked for compliance with
the RFCs defining valid host names. Table 5–6 describes the three name-checking
methods.
Table 5–6 Name Checking Options
Option Description
ignore No checking is done.
warn Names are checked against their expected client contexts.
Invalid names are logged, but processing continues normally.
fail Names are checked against their expected client contexts.
Invalid names are logged, and the offending data is rejected.
The server can check names in three areas: master zone files, slave zone files
to queries the server has initiated. If check-names response fail has been
specified, and answering the client’s question would require sending an invalid
name to the client, the server sends a REFUSED response code to the client. The
defaults are:
•
check-names master fail
• check-names slave warn
• check-names response ignore
The check-names option can also be specified in the zone statement, in which case
it overrides the options check-names statement. When used in a zone statement,
the area is not specified (because it can be deduced from the zone type).
5–14 Configuring and Managing BIND