BIND Definition of Address List Match

This section defines the term 'address_list_match' used with many statements. Full list of options statements. The full syntax allows many variations:

address_match_list = element ; [ element; ... ]

An address_match_list is comprised of one or more elements each of which has the following syntax:

element = [!] (ip [/prefix] | key key_id | "acl_name" | { address_match_list } )

The elements which make up an address match list can be:

The four predefined address_match_list names are:

One of the main uses for address_match_lists is with IP addresses for access control. When a given IP address is compared to an address_match_list the list is traversed in order until an element matches at which point processing stops. The action taken will depend on the context of the statement to which it is being applied as shown in the following example:

options {
    allow-transfer { !;;};

If the IP address requests a transfer it does not match the first element but matches the second element and the transfer is permitted, if however the IP requests a transfer it matches the first element which is negated meaning the transfer is denied. Because a match stops processing the match order is significant. If the above were rewritten to reverse the order then would always be permitted to transfer because the first item always matches:

options {
     allow-transfer {; !;};

The general rule may be expressed as "a non-negated match permits the operation and a negated match denies the operation, if there is no match the operation is denied". The following example shows the use of an acl clause to standardize an address_match_list by simply changing the contents of the acl these changes are propagated to all users of the acl clause:

acl "good-guys" {
     !; // denies first 16 IPs;  // allows rest of subnet
     localnets;   // allows our network
     2001:db8:0:1::/64; // allows this subnet only
options {
      allow-transfer {"good-guys";};

The key_id parameter allows the address_match_list to reference a key clause - the match in this case will occur if the keys match.

Nesting is generally only used with the topology (not currently implemented) and the sortlist statement and the address_match_list behavior is slightly changed. Nesting use is described in the context of the sortlist statement.

Pro DNS and BIND by Ron Aitchison


tech info
guides home
dns articles
1 objectives
big picture
2 concepts
3 reverse map
4 dns types
5 install bind
6 samples
7 named.conf
8 dns records
9 howtos
10 tools
11 trouble
12 bind api's
13 dns security
bits & bytes
15 messages
notes & tips
registration FAQ
dns resources
dns rfc's
change log