<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN">

<refentry>

<refentryinfo>

<date>June 13, 2000</date>

</refentryinfo>

<refmeta>

<refentrytitle><application>named-checkzone</application></refentrytitle>

<manvolnum>8</manvolnum>

<refmiscinfo>BIND9</refmiscinfo>

</refmeta>

<refnamediv>

<refname><application>named-checkzone</application></refname>

<refpurpose>zone file validity checking tool</refpurpose>

</refnamediv>

<refsynopsisdiv>

<cmdsynopsis>

<command>named-checkzone</command>

<arg><option>-d</option></arg>

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

<arg><option>-q</option></arg>

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

<arg><option>-c <replaceable class="parameter">class</replaceable></option></arg>

<arg><option>-k <replaceable class="parameter">mode</replaceable></option></arg>

<arg><option>-n <replaceable class="parameter">mode</replaceable></option></arg>

<arg><option>-o <replaceable class="parameter">filename</replaceable></option></arg>

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

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

<arg><option>-D</option></arg>

<arg><option>-W <replaceable class="parameter">mode</replaceable></option></arg>

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

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

</cmdsynopsis>

</refsynopsisdiv>

<refsect1>

<title>DESCRIPTION</title>

<para>

<command>named-checkzone</command> checks the syntax and integrity of

a zone file. It performs the same checks as <command>named</command>

does when loading a zone. This makes

<command>named-checkzone</command> useful for checking zone

files before configuring them into a name server.

</para>

</refsect1>

<refsect1>

<title>OPTIONS</title>

<variablelist>

<varlistentry>

<term>-d</term>

<listitem>

<para>

Enable debugging.

</para>

</listitem>

</varlistentry>

<varlistentry>

<term>-q</term>

<listitem>

<para>

Quiet mode - exit code only.

</para>

</listitem>

</varlistentry>

<varlistentry>

<term>-v</term>

<listitem>

<para>

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

program and exit.

</para>

</listitem>

</varlistentry>

<varlistentry>

<term>-j</term>

<listitem>

<para>

When loading the zone file read the journal if it exists.

</para>

</listitem>

<varlistentry>

<term>-c <replaceable class="parameter">class</replaceable></term>

<listitem>

<para>

Specify the class of the zone. If not specified "IN" is assumed.

</para>

</listitem>

</varlistentry>

<varlistentry>

<term>-k <replaceable class="parameter">mode</replaceable></term>

<listitem>

<para>

Perform <command>"check-name"</command> checks with the specified failure mode.

Possible modes are <command>"fail"</command>,

<command>"warn"</command> (default) and

<command>"ignore"</command>.

</para>

</listitem>

</varlistentry>

<varlistentry>

<term>-n <replaceable class="parameter">mode</replaceable></term>

<listitem>

<para>

Specify whether NS records should be checked to see if they

are addresses. Possible modes are <command>"fail"</command>,

<command>"warn"</command> (default) and

<command>"ignore"</command>.

</para>

</listitem>

</varlistentry>

<varlistentry>

<term>-o <replaceable class="parameter">filename</replaceable></term>

<listitem>

<para>

Write zone output to <filename>directory</filename>.

</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>-w <replaceable class="parameter">directory</replaceable></term>

<listitem>

<para>

chdir to <filename>directory</filename> so that relative

filenames in master file $INCLUDE directives work. This

is similar to the directory clause in

<filename>named.conf</filename>.

</para>

</listitem>

</varlistentry>

<varlistentry>

<term>-D</term>

<listitem>

<para>

Dump zone file in canonical format.

</para>

</listitem>

</varlistentry>

<varlistentry>

<term>-W <replaceable class="parameter">mode</replaceable></term>

<listitem>

<para>

Specify whether to check for non-terminal wildcards.

Non-terminal wildcards are almost always the result of a

failure to understand the wildcard matching algorithm (RFC 1034).

Possible modes are <command>"warn"</command> (default) and

<command>"ignore"</command>.

</para>

</listitem>

</varlistentry>

<varlistentry>

<term>zonename</term>

<listitem>

<para>

The domain name of the zone being checked.

</para>

</listitem>

</varlistentry>

<varlistentry>

<term>filename</term>

<listitem>

<para>

The name of the zone file.

</para>

</listitem>

</varlistentry>

</variablelist>

</refsect1>

<refsect1>

<title>RETURN VALUES</title>

<para>

<command>named-checkzone</command> returns an exit status of 1 if

errors were detected and 0 otherwise.

</refsect1>

<refsect1>

<title>SEE ALSO</title>

<para>

<citerefentry>

<refentrytitle>named</refentrytitle>

<manvolnum>8</manvolnum>

</citerefentry>,

<citetitle>RFC 1035</citetitle>,

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

</para>

</refsect1>

<refsect1>

<title>AUTHOR</title>

<para>

<corpauthor>Internet Systems Consortium</corpauthor>

</para>

</refsect1>

</refentry>