named-checkconf — named configuration file syntax checking tool
checks the syntax, but not the semantics, of a
named configuration file. The file is parsed
and checked for syntax errors, along with all files included by it.
If no file is specified,
/etc/named.conf is read
Note: files that named reads in separate
parser contexts, such as
bind.keys, are not automatically read
by named-checkconf. Configuration
errors in these files may cause named to
fail to run, even if named-checkconf was
successful. named-checkconf can be run
on these files explicitly, however.
Print the usage summary and exit.
When loading a zonefile read the journal if it exists.
Print out the
named.conf and included files
in canonical form if no errors were detected.
See also the
directory so that include
directives in the configuration file are processed as if
run by a similarly chrooted named.
Print the version of the named-checkconf program and exit.
When printing the configuration files in canonical
form, obscure shared secrets by replacing them with
strings of question marks ('?'). This allows the
named.conf and related
files to be shared — for example, when submitting
bug reports — without compromising private data.
This option cannot be used without
Perform a test load of all master zones found in
The name of the configuration file to be checked. If not
specified, it defaults to
BIND 9.9.13 (Extended Support Version)