HP OpenVMS Systems Documentation

There are many categories, so you can send the logs you want to see anywhere, without seeing logs you do not want. If you do not specify a list of channels for a category, then log messages in that category are sent to the default category instead. If you do not specify a default category, the following "default default" is used:

category default { default_syslog; default_debug; };

For example, if you want to log security events to a file but you also want to keep the default logging behavior, specify the following:

channel my_security_channel {
    file "my_security_file";
    severity info;
};
category security { my_security_channel;
    default_syslog;
    default_debug;
};

To discard all messages in a category, specify the null channel:

category lame-servers { null; };
category cname { null; };

The following categories are available:

category default { default_syslog; default_debug; };

category panic { default_syslog; default_stderr; };

category eventlib { default_debug; };

category packet { default_debug; };

The options statement sets up global options to be used by BIND. This statement can appear only once in a configuration file; if more than one occurrence is found, the first occurrence determines the actual options used, and a warning is generated. If there is no options statement, an options block with each option set to its default is used. The options statement has the following syntax:

options {
[ directory path_name; ]
[ named-xfer path_name; ]
[ dump-file path_name; ]
[ pid-file path_name; ]
[ statistics-file path_name; ]
[ auth-nxdomain yes_or_no; ]
[ fake-iquery yes_or_no; ]
[ fetch-glue yes_or_no; ]
[ multiple-cnames yes_or_no; ]
[ notify yes_or_no; ]
[ recursion yes_or_no; ]
[ forward ( only | first ); ]
[ forwarders { [ in_addr ; [ in_addr ; ... ] ] }; ]
[ check-names ( master | slave | response ) ( warn | fail | ignore); ]
[ allow-query { address_match_list }; ]
[ allow-transfer { address_match_list }; ]
[ listen-on [ port ip_port ] { address_match_list }; ]
[ query-source [ address ( ip_addr | * ) ] [ port ( ip_port | * ) ] ; ]
[ max-transfer-time-in number; ]
[ transfer-format ( one-answer | many-answers ); ]
[ transfers-in  number; ]
[ transfers-out number; ]
[ transfers-per-ns number; ]
[ coresize size_spec ; ]
[ datasize size_spec ; ]
[ files size_spec ; ]
[ stacksize size_spec ; ]
[ cleaning-interval number; ]
[ interface-interval number; ]
[ statistics-interval number; ]
[ topology { address_match_list }; ]

};

Table D-3 lists the path name options.

Example D-1 shows how to specify path name options with the options statement.

options {
 directory   "SYS$SPECIFIC:[TCPIP$BIND]";
 dump-file  "TCPIP$BIND_SERVER_ZONES_DUMP.DB";
 memstatistics-file  "TCPIP$BIND_SERVER_MEMSTATISTICS.LOG";
 pid-file  "TCPIP$BIND_SERVER.PID";
 statistics-file  "TCPIP$BIND_SERVER_STATISTICS.LOG"
};

Table D-4 lists the Boolean options.

Example D-2 shows how to specify Boolean options in an options statement.

options {
 auth-nxdomain  yes;
 deallocate-on-exit no;
 fake-iquery  no;
 fetch-glue  yes;
 host-statistics  no;
 multiple-cnames  no;
 notify   yes;
 recursion  yes;
};

You can use the forwarding facility to create a large sitewide cache on a few servers, reducing traffic over links to external name servers. You can also use the forwarding facility to allow queries by servers that do not have direct access to the Internet, but wish to look up exterior names anyway. Forwarding occurs on only those queries for which the server is not authoritative and does not have the answer in its cache. Table D-5 lists the forwarding options.

Example D-3 shows how to specify an options statement to invoke forwarding.

options {
 forwarders {
   1.2.3.4;
   5.6.7.8;
 };
 forward first;
};

The server can check domain names based on their expected client contexts. For example, a domain name used as a host name can be checked for compliance with the RFCs defining valid host names. Table D-6 describes the three name-checking methods.

The server can check names in three areas: master zone files, slave zone files to queries the server has initiated. If check-names response fail has been specified, and answering the client's question would require sending an invalid name to the client, the server sends a REFUSED response code to the client. The defaults are:

• check-names master fail
• check-names slave warn
• check-names response ignore

The check-names option can also be specified in the zone statement, in which case it overrides the options check-names statement. When used in a zone statement, the area is not specified (because it can be deduced from the zone type).

Example D-4 shows how to specify an options statement for name checking. The statement specifies that nonconforming names coming from a slave are ignored.

options  {
          check-names slave ignore;
};

Access to the server can be restricted based on the IP address of the requesting system. Table D-7 describes the access control options.

Example D-5 shows how to specify an options statement to control access to the server.

options {
 allow-query { any; } ;
 allow-transfer {
       1.2.3/24;
      5.6.7.8;
 };
};

The interfaces and ports from which the server answers queries can be specified using the listen-on option. The listen-on option takes an optional port and an address_match_list . The server listens on all interfaces allowed by the address match list. All queries must be directed to the interface and port number specified on the listen-on statement. If a port is not specified, the server uses port 53.

Multiple listen-on statements are allowed. For example,

    listen-on { 5.6.7.8; };
    listen-on port 1234 { !1.2.3.4; 1.2/16; };

If a listen-on option is not specified, the server listens on port 53 on all interfaces.

D.3.2.7 Query Address

If the server does not know the answer to a question, it queries other name servers. The query-source option specifies the source address and source port used for such queries. If the address is an asterisk (*) or is omitted, the server uses a wildcard IP address (INADDR_ANY). If the port is an asterisk (*) or is omitted, the server uses a random unprivileged port. The default query-source statement is as follows:

    query-source address * port *;

The query-source option currently applies only to UDP queries; TCP queries always use a wildcard IP address and a random unprivileged port.

D.3.2.8 Zone Transfers

Table D-8 describes the zone transfer options.

Example D-6 shows how to specify an options statement to control zone transfers.

options {
 max-transfer-time-in 120;
 transfer-format  one-answer;
 transfers-in  10;
 transfers-per-ns 2;
};