BIND Configuration File Guide - server Statement

Syntax

server ip_addr {
  [ bogus yes_or_no; ]
  [ support-ixfr yes_or_no; ]
  [ transfers number; ]
  [ transfer-format ( one-answer | many-answers ); ]
  [ keys { key_id [key_id ... ] }; ]
};

Definition and Usage

The server statement defines the characteristics to be associated with a remote name server.

If you discover that a server is giving out bad data, marking it as bogus will prevent further queries to it. The default value of bogus is no.

The server supports two 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 option is more efficient, but is known to be understood only by BIND 8.1 and patched versions of BIND 4.9.5.

You can specify which method to use for a server with the transfer-format option. If the transfer-format option is not specified, the transfer-format specified by the options statement is used.

The transfers option will be used in a future release of the server to limit the number of concurrent in-bound zone transfers from the specified server. It is checked for syntax, but is otherwise ignored.

You can use the keys clause to identify a key_id defined by the key statement. The key is used for transaction security when talking to the remote server. The key statement must come before the server statement that references it. When a request is sent to the remote server, a request signature is generated using the key specified here and appended to the message. A request originating from the remote server is not required to be signed by this key.