c1350cf5bc50458ba79cc93ff9e0e5fe3f1aeeb0jeff.schenk<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"

c1350cf5bc50458ba79cc93ff9e0e5fe3f1aeeb0jeff.schenk "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"

c1350cf5bc50458ba79cc93ff9e0e5fe3f1aeeb0jeff.schenk [<!ENTITY mdash "&#8212;">]>

c1350cf5bc50458ba79cc93ff9e0e5fe3f1aeeb0jeff.schenk

c1350cf5bc50458ba79cc93ff9e0e5fe3f1aeeb0jeff.schenk<refentry id="man.named-checkconf">

c1350cf5bc50458ba79cc93ff9e0e5fe3f1aeeb0jeff.schenk <refentryinfo>

c1350cf5bc50458ba79cc93ff9e0e5fe3f1aeeb0jeff.schenk <date>June 14, 2000</date>

c1350cf5bc50458ba79cc93ff9e0e5fe3f1aeeb0jeff.schenk </refentryinfo>

c1350cf5bc50458ba79cc93ff9e0e5fe3f1aeeb0jeff.schenk

<refmeta>

<refentrytitle><application>named-checkconf</application></refentrytitle>

<manvolnum>8</manvolnum>

<refmiscinfo>BIND9</refmiscinfo>

</refmeta>

<docinfo>

<copyright>

<year>2004</year>

<year>2005</year>

<year>2007</year>

<year>2009</year>

<year>2014</year>

<holder>Internet Systems Consortium, Inc. ("ISC")</holder>

</copyright>

<copyright>

<year>2000</year>

<year>2001</year>

<year>2002</year>

<holder>Internet Software Consortium.</holder>

</copyright>

</docinfo>

<refnamediv>

<refname><application>named-checkconf</application></refname>

<refpurpose>named configuration file syntax checking tool</refpurpose>

</refnamediv>

<refsynopsisdiv>

<cmdsynopsis>

<command>named-checkconf</command>

<arg><option>-h</option></arg>

<arg><option>-v</option></arg>

<arg><option>-j</option></arg>

<arg><option>-t <replaceable class="parameter">directory</replaceable></option></arg>

<arg choice="req">filename</arg>

<arg><option>-p</option></arg>

<arg><option>-x</option></arg>

<arg><option>-z</option></arg>

</cmdsynopsis>

</refsynopsisdiv>

<refsect1>

<title>DESCRIPTION</title>

<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

by default.

</para>

<para>

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.

</para>

</refsect1>

<refsect1>

<title>OPTIONS</title>

<variablelist>

<varlistentry>

<term>-h</term>

<listitem>

<para>

Print the usage summary and exit.

</para>

</listitem>

</varlistentry>

<varlistentry>

<term>-t <replaceable class="parameter">directory</replaceable></term>

<listitem>

<para>

Chroot to <filename>directory</filename> so that include

directives in the configuration file are processed as if

run by a similarly chrooted named.

</para>

</listitem>

</varlistentry>

<varlistentry>

<term>-v</term>

<listitem>

<para>

Print the version of the <command>named-checkconf</command>

program and exit.

</para>

</listitem>

</varlistentry>

<varlistentry>

<term>-p</term>

<listitem>

<para>

Print out the <filename>named.conf</filename> and included files

in canonical form if no errors were detected.

</para>

</listitem>

</varlistentry>

<varlistentry>

<term>-x</term>

<listitem>

<para>

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 &mdash; for example, when submitting

bug reports &mdash; without compromising private data.

This option cannot be used without <option>-p</option>.

</para>

</listitem>

</varlistentry>

<varlistentry>

<term>-z</term>

<listitem>

<para>

Perform a test load of all master zones found in

<filename>named.conf</filename>.

</para>

</listitem>

</varlistentry>

<varlistentry>

<term>-j</term>

<listitem>

<para>

When loading a zonefile read the journal if it exists.

</para>

</listitem>

</varlistentry>

<varlistentry>

<term>filename</term>

<listitem>

<para>

The name of the configuration file to be checked. If not

specified, it defaults to <filename>/etc/named.conf</filename>.

</para>

</listitem>

</varlistentry>

</variablelist>

</refsect1>

<refsect1>

<title>RETURN VALUES</title>

<para><command>named-checkconf</command>

returns an exit status of 1 if

errors were detected and 0 otherwise.

</para>

</refsect1>

<refsect1>

<title>SEE ALSO</title>

<para><citerefentry>

<refentrytitle>named</refentrytitle><manvolnum>8</manvolnum>

</citerefentry>,

<citerefentry>

<refentrytitle>named-checkzone</refentrytitle><manvolnum>8</manvolnum>

</citerefentry>,

<citetitle>BIND 9 Administrator Reference Manual</citetitle>.

</para>

</refsect1>

<refsect1>

<title>AUTHOR</title>

<para><corpauthor>Internet Systems Consortium</corpauthor>

</para>

</refsect1>

</refentry><!--