<!ENTITY mdash "—">]>
- Copyright (C) 2000-2002, 2004, 2005, 2007, 2009, 2014-2016 Internet Systems Consortium, Inc. ("ISC") - This Source Code Form is subject to the terms of the Mozilla Public - License, v. 2.0. If a copy of the MPL was not distributed with this <!-- Converted by db4-upgrade version 1.0 --> <
corpauthor>Internet Systems Consortium, Inc.</
corpauthor>
<
refentrytitle><
application>named-checkconf</
application></
refentrytitle>
<
refmiscinfo>BIND9</
refmiscinfo>
<
holder>Internet Systems Consortium, Inc. ("ISC")</
holder>
<
holder>Internet Software Consortium.</
holder>
<
refname><
application>named-checkconf</
application></
refname>
<
refpurpose>named configuration file syntax checking tool</
refpurpose>
<
cmdsynopsis sepchar=" ">
<
command>named-checkconf</
command>
<
arg choice="opt" rep="norepeat"><
option>-h</
option></
arg>
<
arg choice="opt" rep="norepeat"><
option>-v</
option></
arg>
<
arg choice="opt" rep="norepeat"><
option>-j</
option></
arg>
<
arg choice="opt" rep="norepeat"><
option>-t <
replaceable class="parameter">directory</
replaceable></
option></
arg>
<
arg choice="req" rep="norepeat">filename</
arg>
<
arg choice="opt" rep="norepeat"><
option>-p</
option></
arg>
<
arg choice="opt" rep="norepeat"><
option>-x</
option></
arg>
<
arg choice="opt" rep="norepeat"><
option>-z</
option></
arg>
<
refsection><
info><
title>DESCRIPTION</
title></
info>
<
para><
command>named-checkconf</
command>
checks the syntax, but not the semantics, of a
<
command>named</
command> configuration file. The file is parsed
and checked for syntax errors, along with all files included by it.
If no file is specified, <
filename>/
etc/
named.conf</
filename> is read
Note: files that <
command>named</
command> reads in separate
parser contexts, such as <
filename>
rndc.key</
filename> and
<
filename>
bind.keys</
filename>, are not automatically read
by <
command>named-checkconf</
command>. Configuration
errors in these files may cause <
command>named</
command> to
fail to run, even if <
command>named-checkconf</
command> was
successful. <
command>named-checkconf</
command> can be run
on these files explicitly, however.
<
refsection><
info><
title>OPTIONS</
title></
info>
Print the usage summary and exit.
<
term>-t <
replaceable class="parameter">directory</
replaceable></
term>
Chroot to <
filename>directory</
filename> so that include
directives in the configuration file are processed as if
run by a similarly chrooted <
command>named</
command>.
Print the version of the <
command>named-checkconf</
command>
Print out the <
filename>
named.conf</
filename> and included files
in canonical form if no errors were detected.
When printing the configuration files in canonical
form, obscure shared secrets by replacing them with
strings of question marks ('?'). This allows the
contents of <
filename>
named.conf</
filename> and related
files to be shared — for example, when submitting
bug reports — without compromising private data.
This option cannot be used without <
option>-p</
option>.
Perform a test load of all master zones found in
When loading a zonefile read the journal if it exists.
The name of the configuration file to be checked. If not
<
refsection><
info><
title>RETURN VALUES</
title></
info>
<
para><
command>named-checkconf</
command>
returns an exit status of 1 if
errors were detected and 0 otherwise.
<
refsection><
info><
title>SEE ALSO</
title></
info>
<
refentrytitle>named</
refentrytitle><
manvolnum>8</
manvolnum>
<
refentrytitle>named-checkzone</
refentrytitle><
manvolnum>8</
manvolnum>
<
citetitle>BIND 9 Administrator Reference Manual</
citetitle>.