Configuring and Managing MPE/iX Internet Services (MPE/iX 6.5)

196 AppendixB
BIND 8 Configuration File
sites
// for load balancing.
allow-query { any; };
allow-transfer { any; };
transfers-in 10; // DEFAULT_XFERS_RUNNING, cannot
be
// set > than MAX_XFERS_RUNNING
(20)
transfers-per-ns 2; // DEFAULT_XFERS_PER_NS
transfers-out 0; // not implemented
max-transfer-time-in 120; // MAX_XFER_TIME; the default
number
// of minutes an inbound zone
transfer
// may run. May be set on a
per-zone
// basis.
/*
* The “transfer-format” option specifies the way outbound zone
* transfers (i.e. from us to them) are formatted. Two values are
* allowed:
*
* one-answer Each RR gets its own DNS message.
* This format is not very efficient,
* but is widely understood.All
* versions of BIND prior to 8.1 generate
* this format for outbound zone
* and require it on inbound transfers.
*
* many-answers As many RRs as will fit are put into
* each DNS message. This format is
* the most efficient, but is only known
* to work with BIND 8. Patches to
* BIND 4.9.5 named-xfer that enable it
* to understand ‘many-answers’ will be
* available.
*
* If you are going to be doing zone transfers to older servers, you
* shouldn’t use ‘many-answers’. ‘transfer-format’ may also be set
* on a host-by-host basis using the ‘server’ statement (see below).
*/
transfer-format one-answer;
query-source address * port *;
/*
* The “forward” option is only meaningful if you’ve defined
* forwarders. “first” gives the normal BIND
* forwarding behavior, i.e. ask the forwarders first, and if that
* doesn’t work then do the full lookup. You can also say
* “forward only;” which is what used to be specified with
* “slave” or “options forward-only”. “only” will never attempt
* a full lookup; only the forwarders will be used.
*/