Described below are elements used throughout the BIND configuration
file documentation. Elements which are only associated with one
statement are described only in the section describing that statement.
A list of one or more ip_address, ip_prefix or
acl_name elements, as described in the
Address Match Lists section.
One or more integers valued 0 through 255 separated only by dots
("."), such as 123 or 45.67 or
A quoted string which will be used as a DNS name, for example
A quoted string which will be used as a pathname, such as
An IP address in with exactly four elements in
An IP port number. number is limited to 0
through 65535, with values below 1024 typically restricted to
An IP network specified in dotted-decimal form, followed by "/"
and then the number of bits in the netmask. E.g. 127/8 is
the network 127.0.0.0 with netmask 255.0.0.0.
18.104.22.168/24 is network 22.214.171.124 with netmask
A non-negative integer with an entire range limited by the range of a
C language signed integer (2,147,483,647 on a machine with 32 bit
integers). Its acceptable value might further be limited by the
context in which it is used.
A number, the word unlimited, or the word
The maximum value of size_spec is that of unsigned long
integers on the machine. unlimited requests unlimited use, or
the maximum available amount. default uses the limit that
was in force when the server was started.
A number can optionally be followed by a scaling factor:
K or k for kilobytes, M or
m for megabytes, and G or g for
gigabytes, which scale by 1024, 1024*1024, and 1024*1024*1024
Integer storage overflow is currently silently ignored during
conversion of scaled values, resulting in values less than intended,
possibly even negative. Using unlimited is the best way
to safely set a really large number.
Either yes or no. The words
true and false are also accepted, as are the
numbers 1 and 0.