HP-UX Reference (11i v2 04/09) - 4 File Formats (vol 8)

n
named.conf(4) named.conf(4)
The UNIX control channel type of BIND 8 is not supported in BIND 9.2, and is not expected to be added
in future releases. If it is present in the
controls statement from a BIND 8 configuration file, it is
ignored and a warning is logged.
include Statement Grammar
include filename ;
include Statement Definition and Usage
The include statement inserts the specified file at the point where the
include statement is encoun-
tered. The
include statement facilitates the administration of configuration files by permitting the
reading or writing of some things but not others. For example, the statement could include private keys
that are readable only by a nameserver.
key Statement Grammar
key key_id {
algorithm string;
secret string;
};
key Statement Definition and Usage
The key statement defines a shared secret key for use with TSIG. The key statement can occur at the
top level of the configuration file or inside a
view statement. Keys defined in top-level key statements
can be used in all views. Keys intended for use in a controls statement must be defined at the top
level.
The
key_id, also known as the key name, is a domain name uniquely identifying the key. It can be
used in a server statement to sign requests with this key or in address match lists to verify that incoming
requests have been signed with a key matching this name, algorithm, and secret.
The
algorithm_id is a string that specifies a security/authentication algorithm. "hmac-md5" is the
only algorithm which is currently supported with TSIG authentication. The
secret_string is a base-
64 encoded secret string to be used by the algorithm.
logging Statement Grammar
logging {
[ channel channel_name {
( file path name
[ versions ( number | unlimited ) ]
[ size size spec ]
| syslog syslog_facility
| stderr
| null );
[ severity (critical | error | warning | notice |
info | debug [ level ] | dynamic ); ]
[ print-category yes or no; ]
[ print-severity yes or no; ]
[ print-time yes or no; ]
}; ]
[ category category_name {
channel_name ; [ channel_name ; ... ]
}; ]
...
};
logging Statement Definition and Usage
The
logging statement configures a wide variety of logging options for the nameserver. Its channel
phrase associates output methods, format options and severity levels with a name that can be used with
the category phrase to select how various classes of messages are logged.
Only one
logging statement is used to define any number of channels and categories. If there is no
logging statement, the logging configuration will be:
logging {
category "unmatched" { "null"; };
category "default" { "default_syslog"; "default_debug"; };
HP-UX 11i Version 2: September 2004 − 4 − Hewlett-Packard Company Section 4−−179