Technical data

Configuring and Managing BIND
5.3 Configuring the BIND Server (BIND 8.1)
Table 5–2 (Cont.) BIND Name Server Configuration Statements
Statement Description
logging Configures logging options for the name server. Options include output methods,
format options, and severity levels that you associate with a name that can then
be used with the category phrase to select how various classes of messages are
logged. Use one logging statement to define as many channels and categories as
you want. See Section 5.3.1 for more information about these options.
options Sets up global server configuration options and sets defaults for other
statements. This statement is used only once in a configuration file. Options
statements include path names, Boolean options, forwarding information,
name checking, access control, interfaces, query addresses, zone transfers,
resource limits, periodic task intervals, and topology. See Section 5.3.2 for more
information about these options.
server ip_address Defines the characteristics associated with a remote name server. The server
supports the following zone transfer methods:
one-answer Uses one DNS message per resource record transferred.
many-answers Packs as many resource records as possible into a message.
This method is more efficient but is only understood by
BIND 8.1.2.
You can specify which method to use for a server with the
transfer-format
option. If transfer-format is not specified, the transfer-format specified
by the options statement is used.
zone domain_name Defines a zone. Valid types include master, slave, stub, and hint.
The following sample is a configuration file for a master server:
options {
directory "SYS$SPECIFIC:[TCPIP$BIND]";
};
zone "FRED.PARROT.BIRD.COM" in {
type master;
file "FRED_PARROT_BIRD_COM.DB";
};
zone "0.0.127.IN-ADDR.ARPA" in {
type master;
file "127_0_0.DB";
};
zone "LOCALHOST" in {
type master;
file "LOCALHOST.DB";
};
zone "208.20.16.IN-ADDR.ARPA" in {
type master;
file "208_20_16_IN-ADDR_ARPA.DB";
};
zone "." in {
type hint;
file "ROOT.HINT";
};
The following comment styles are valid in a BIND configuration file. Comments
can appear anywhere in the file.
• C-style comments that start with /* and end with */
5–6 Configuring and Managing BIND