DNS BIND Server Clause

This section describes the server clause available in BIND 9.x named.conf.

The server clause allows certain characteristics to be defined when this server is interacting with the remote server defined by ip-addr (IPv4 or IPv6). The ip_addr will only take a single IP value. There may be any number of server statements. Full list of statements.

There is no requirement to have any server statements in which case default behaviours for all remote servers will be used.

  server ip-addr {
  [ bogus yes | no ; ]
	[ edns yes | no ; ]
  [ keys "key-name"; ["key-name"; ... ; ]
  [ provide-ixfr yes | no; ]
  [ request-ixfr yes | no; ]
  [ transfers number; ]
  [ transfer-format ( one-answer | many-answers ); ]
  ;}

bogus

 bogus yes | no 

Indicates that traffic from this server should be ignored e.g. if known to be giving bad data, generating a DoS attack or some other reason. This statement can be used in the server clause only.

edns

 edns yes | no ;

Defines whether to use EDNS (RFC 2671) with a specific server (yes) or not (no). The default is yes. This statement may only be used in a server clause.

keys

 keys "key-name"; ["key-name"; ... ;];
 keys "key-name"; ["server1-key-name";

The key-name field references a key clause with the same key-name and mandates that TSIG transactions (zone transfer or DDNS operation) with use this key. While syntax allows for multiple keys current versions of BIND (9.x) only support a single key-name per server. This statement may only be used in a server clause.

transfers

 [ transfers number ; ]

Limits the number of concurrent zone transfers from any given server. If not present the default for transfers-per-ns is used. This option may be specified only in a server clause.

Problems, comments, suggestions, corrections (including broken links) or something to add? Please take the time from a busy life to 'mail us' (at top of screen), the webmaster (below) or info-support at zytrax. You will have a warm inner glow for the rest of the day.