HP-UX Reference (11i v3 07/02) - 4 File Formats (vol 8)

n
named.conf(4) named.conf(4)
(BIND 9.3)
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.
key_id A domain name uniquely identifying the key. Also known as the key name. 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.
algoname A string that specifies a security/authentication algorithm.
hmac-md5 is the only algo-
rithm which is currently supported with TSIG authentication.
secretstring A base-64-encoded secret string to be used by the algorithm.
The logging Statement
logging Statement Grammar
logging {
[ channel channel_name {
( file path name
[ versions ( number | unlimited )]
[ size size spec ]
| null
| stderr
| syslog syslog_facility
) ;
[ 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 ; )...
}; ]...
};
The
category and channel clauses may be repeated in any order.
logging Statement Definition and Usage
The logging statement configures a wide variety of logging options for the name server. Its
channel
phrase associates output methods, format options, and severity levels with a name, channel_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 defaults to:
logging {
category "unmatched" { "null"; };
category "default" { "default_syslog"; "default_debug"; };
};
In BIND 9.3, the logging configuration is established only when the entire configuration file has been
parsed. In BIND 8, it was established as soon as the logging statement was parsed. When the server
starts up, all logging messages related to syntax errors in the configuration file go to the default channels,
or to standard error if the -g option is specified.
The channel Phrase
All log output goes to one or more user-defined or predefined channels. Every channel definition must
include a destination clause that says whether messages selected for the channel go to a file, or to a particu-
lar syslog facility, or to the standard error stream, or are discarded. It can optionally also limit the mes-
sage severity level that will be accepted by the channel (the default is info), and whether to include a
named-generated time stamp, the category name, and/or severity level (the default is not to include any).
HP-UX 11i Version 3: February 2007 − 5 − Hewlett-Packard Company 237