named-checkconf — named configuration file syntax checking tool
named-checkconf
[-chjlvz]
[-p
[-x
]]
[-t ]
{filename}
directory
named-checkconf
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
by default.
Note: files that named reads in separate
parser contexts, such as rndc.key and
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.
List all the configured zones. Each line of output contains the zone name, class (e.g. IN), view, and type (e.g. master or slave).
Check "core" configuration only. This suppresses the loading of plugin modules, and causes all parameters to plugin statements to be ignored.
Ignore warnings on deprecated options.
Print out the named.conf and included files
in canonical form if no errors were detected.
See also the -x option.
directory
Chroot to 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
contents of named.conf and related
files to be shared — for example, when submitting
bug reports — without compromising private data.
This option cannot be used without -p.
Perform a test load of all master zones found in
named.conf.
The name of the configuration file to be checked. If not
specified, it defaults to /etc/named.conf.
BIND 9.15.4 (Development Release)