BIND 8.1.2 Release Notes

New and Changed Features
New Features
Chapter 1 21
the forwarders list. If this query is not successful, the server by
itself searches for the answer. If the value is set as only, the server
queries only the forwarder IP addresses.
Name Checking Options
The server checks domain names based on their expected client contexts.
For example, you can check whether a domain name used as a hostname
complies with the RFCs that define valid host names.
The name checking option is of the following format:
check-names ( master | slave | response ) ( warn | fail |
ignore);
The server can check names in the following areas:
master - Checks master zone files.
slave - Checks slave zone files.
response - Checks in the response to queries that the server has
initiated.
Following are the checking methods 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 default values for the check-names option are:
check-names master fail;
check-names slave warn;
check-names response ignore;
If check-names response fail is specified, an invalid name is sent to
the client as a reply to the client’s question. And, the server sends a
REFUSED response code to the client.
You can also specify check-names in the zone statement, but this
overrides the options check-names statement. When you specify
check-names in a zone statement, the area is not specified, because it
can be derived from the zone type.
Access Control Options