Installing and Administering Internet Services

100 Chapter3
Configuring and Administering the BIND Name Service
Configuring a Primary Master Name Server
used as a hostname can be checked for compliance with the RFCs
defining valid hostnames.
check-names (master | slave | response ) (warn | fail |\
ignore);
The server can check names in three areas:
master: check master zone files
slave: check slave zone files
response: check in response to queries the server has initiated.
Three checking methods are available for check-names:
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 defaults are check-names master fail; check-names slave warn;
and check-names response ignore.Ifcheck-names response fail is
specified, the server will send a REFUSED response code to the client.
check-names may 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.)
Access Control Options: Access to the server can be restricted based
on the IP address of the requesting system. See address_match_list for
details on how to specify IP address lists. The access control options are
listed in Table 3-6 below.
Table 3-6 Access Control Options
Options Descriptions
allow-query {
address_match_list} ;
This specifies which hosts are allowed to ask ordinary
questions. allow-query may also be specified in
the zone statement. If it is specified in the zone
statement, it overrides the options allow-query
statement. The default is to allow queries from all
hosts.