Configuring and Managing MPE/iX Internet Services (August 2002)

Appendix C
BIND 8.1 Enhanced Features
BIND 8 Highlights
232
Name Checking
The server can check domain names based upon their expected client contexts. For example, a domain name
used as a hostname can be checked for compliance with the RFCs defining valid hostnames.
Three checking methods are available:
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, and in responses 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 will send a REFUSED response code to the
client.
The defaults are:
check-names master fail;
check-names slave warn;
check-names response ignore;
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
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.
allow-query Specifies which hosts are allowed to ask ordinary questions. allow-query
may also be specified in the zone statement, in which case it overrides the
options allow-query statement. If not specified, the default is to allow
queries from all hosts.
allow-transfer Specifies which hosts are allowed to receive zone transfers from the server.
allow-transfer may also be specified in the zone statement, in which
case it overrides the options allow-transfer statement. If not specified,
the default is to allow transfers from all hosts.
Interfaces
The interfaces and ports that the server will answer queries from may be specified using the listen-on
option. listen-on takes an optional port, and an address_match_list. The server will listen on all
interfaces allowed by the address match list. If a port is not specified, port 53 will be used.
Multiple listen-on statements are allowed. For example:
listen-on { 5.6.7.8; };
listen-on port 1234 { !1.2.3.4; 1.2/16; };
If no listen-on is specified, the server will listen on port 53 on all interfaces.