EVOLUTION-NINJA

Edit File: man.named-checkzone.html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">

<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>named-checkzone</title>
<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.named-checkconf.html" title="named-checkconf">
<link rel="next" href="man.named-journalprint.html" title="named-journalprint">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
<div class="navheader">
<table width="100%" summary="Navigation header">
<tr><th colspan="3" align="center">named-checkzone</th></tr>
<tr>
<td width="20%" align="left">
<a accesskey="p" href="man.named-checkconf.html">Prev</a>�</td>
<th width="60%" align="center">Manual pages</th>
<td width="20%" align="right">�<a accesskey="n" href="man.named-journalprint.html">Next</a>
</td>
</tr>
</table>
<hr>
</div>
<div class="refentry">
<a name="man.named-checkzone"></a><div class="titlepage"></div>
<div class="refnamediv">
<h2>Name</h2>
named-checkzone, named-compilezone &#8212; zone file validity checking or converting tool
</div>
<div class="refsynopsisdiv">
<h2>Synopsis</h2>
<div class="cmdsynopsis"><code class="command">named-checkzone</code> [<code class="option">-d</code>] [<code class="option">-h</code>] [<code class="option">-j</code>] [<code class="option">-q</code>] [<code class="option">-v</code>] [<code class="option">-c <code>class</code></code>] [<code class="option">-f <code>format</code></code>] [<code class="option">-F <code>format</code></code>] [<code class="option">-J <code>filename</code></code>] [<code class="option">-i <code>mode</code></code>] [<code class="option">-k <code>mode</code></code>] [<code class="option">-m <code>mode</code></code>] [<code class="option">-M <code>mode</code></code>] [<code class="option">-n <code>mode</code></code>] [<code class="option">-l <code>ttl</code></code>] [<code class="option">-L <code>serial</code></code>] [<code class="option">-o <code>filename</code></code>] [<code class="option">-r <code>mode</code></code>] [<code class="option">-s <code>style</code></code>] [<code class="option">-S <code>mode</code></code>] [<code class="option">-t <code>directory</code></code>] [<code class="option">-T <code>mode</code></code>] [<code class="option">-w <code>directory</code></code>] [<code class="option">-D</code>] [<code class="option">-W <code>mode</code></code>] {zonename} {filename}</div>
<div class="cmdsynopsis"><code class="command">named-compilezone</code> [<code class="option">-d</code>] [<code class="option">-j</code>] [<code class="option">-q</code>] [<code class="option">-v</code>] [<code class="option">-c <code>class</code></code>] [<code class="option">-C <code>mode</code></code>] [<code class="option">-f <code>format</code></code>] [<code class="option">-F <code>format</code></code>] [<code class="option">-J <code>filename</code></code>] [<code class="option">-i <code>mode</code></code>] [<code class="option">-k <code>mode</code></code>] [<code class="option">-m <code>mode</code></code>] [<code class="option">-n <code>mode</code></code>] [<code class="option">-l <code>ttl</code></code>] [<code class="option">-L <code>serial</code></code>] [<code class="option">-r <code>mode</code></code>] [<code class="option">-s <code>style</code></code>] [<code class="option">-t <code>directory</code></code>] [<code class="option">-T <code>mode</code></code>] [<code class="option">-w <code>directory</code></code>] [<code class="option">-D</code>] [<code class="option">-W <code>mode</code></code>] {<code class="option">-o <code>filename</code></code>} {zonename} {filename}</div>
</div>
<div class="refsection">
<a name="id-1.14.24.7"></a><h2>DESCRIPTION</h2>
named-checkzone
 checks the syntax and integrity of a zone file. It performs the
 same checks as named does when loading a
 zone. This makes named-checkzone useful for
 checking zone files before configuring them into a name server.
 

 named-compilezone is similar to
	named-checkzone, but it always dumps the
 zone contents to a specified file in a specified format.
	Additionally, it applies stricter check levels by default,
 since the dump output will be used as an actual zone file
	loaded by named.
	When manually specified otherwise, the check levels must at
 least be as strict as those specified in the
	named configuration file.
 
</div>
<div class="refsection">
<a name="id-1.14.24.8"></a><h2>OPTIONS</h2>
<div class="variablelist"><dl class="variablelist">
<dt>-d</dt>
<dd>
 Enable debugging.
 </dd>
<dt>-h</dt>
<dd>
 Print the usage summary and exit.
 </dd>
<dt>-q</dt>
<dd>
 Quiet mode - exit code only.
 </dd>
<dt>-v</dt>
<dd>
 Print the version of the named-checkzone
 program and exit.
 </dd>
<dt>-j</dt>
<dd>
 When loading a zone file, read the journal if it exists.
 The journal file name is assumed to be the zone file name
	 appended with the string <code class="filename">.jnl</code>.
 </dd>
<dt>-J <code>filename</code></dt>
<dd>
 When loading the zone file read the journal from the given
 file, if it exists. (Implies -j.)
 </dd>
<dt>-c <code>class</code></dt>
<dd>
 Specify the class of the zone. If not specified, "IN" is assumed.
 </dd>
<dt>-i <code>mode</code></dt>
<dd>

	 Perform post-load zone integrity checks. Possible modes are
	 "full" (default),
	 "full-sibling",
	 "local",
	 "local-sibling" and
	 "none".
	 

	 Mode "full" checks that MX records
	 refer to A or AAAA record (both in-zone and out-of-zone
	 hostnames). Mode "local" only
	 checks MX records which refer to in-zone hostnames.
	 

	 Mode "full" checks that SRV records
	 refer to A or AAAA record (both in-zone and out-of-zone
	 hostnames). Mode "local" only
	 checks SRV records which refer to in-zone hostnames.
	 

	 Mode "full" checks that delegation NS
	 records refer to A or AAAA record (both in-zone and out-of-zone
	 hostnames). It also checks that glue address records
	 in the zone match those advertised by the child.
	 Mode "local" only checks NS records which
	 refer to in-zone hostnames or that some required glue exists,
	 that is when the nameserver is in a child zone.
	 

	 Mode "full-sibling" and
	 "local-sibling" disable sibling glue
	 checks but are otherwise the same as "full"
	 and "local" respectively.
	 

	 Mode "none" disables the checks.
	 
</dd>
<dt>-f <code>format</code></dt>
<dd>
	 Specify the format of the zone file.
	 Possible formats are "text" (default),
	 "raw", and "map".
	 </dd>
<dt>-F <code>format</code></dt>
<dd>

	 Specify the format of the output file specified.
	 For named-checkzone,
	 this does not cause any effects unless it dumps the zone
	 contents.
	 

	 Possible formats are "text" (default),
	 which is the standard textual representation of the zone,
	 and "map", "raw",
 and "raw=N", which store the zone in a
 binary format for rapid loading by named.
 "raw=N" specifies the format version of
 the raw zone file: if N is 0, the raw file can be read by
 any version of named; if N is 1, the file
 can be read by release 9.9.0 or higher; the default is 1.
	 
</dd>
<dt>-k <code>mode</code></dt>
<dd>
 Perform "check-names" checks with the
	 specified failure mode.
 Possible modes are "fail"
	 (default for named-compilezone),
 "warn"
	 (default for named-checkzone) and
 "ignore".
 </dd>
<dt>-l <code>ttl</code></dt>
<dd>
 Sets a maximum permissible TTL for the input file.
 Any record with a TTL higher than this value will cause
 the zone to be rejected. This is similar to using the
 max-zone-ttl option in
 <code class="filename">named.conf</code>.
 </dd>
<dt>-L <code>serial</code></dt>
<dd>
 When compiling a zone to "raw" or "map" format, set the
 "source serial" value in the header to the specified serial
 number. (This is expected to be used primarily for testing
 purposes.)
 </dd>
<dt>-m <code>mode</code></dt>
<dd>
 Specify whether MX records should be checked to see if they
 are addresses. Possible modes are "fail",
 "warn" (default) and
 "ignore".
 </dd>
<dt>-M <code>mode</code></dt>
<dd>
	 Check if a MX record refers to a CNAME.
 Possible modes are "fail",
 "warn" (default) and
 "ignore".
	 </dd>
<dt>-n <code>mode</code></dt>
<dd>
 Specify whether NS records should be checked to see if they
 are addresses.
	 Possible modes are "fail"
	 (default for named-compilezone),
 "warn"
	 (default for named-checkzone) and
 "ignore".
 </dd>
<dt>-o <code>filename</code></dt>
<dd>
 Write zone output to <code class="filename">filename</code>.
	 If <code class="filename">filename</code> is <code class="filename">-</code> then
	 write to standard out.
	 This is mandatory for named-compilezone.
 </dd>
<dt>-r <code>mode</code></dt>
<dd>
 Check for records that are treated as different by DNSSEC but
	 are semantically equal in plain DNS.
 Possible modes are "fail",
 "warn" (default) and
 "ignore".
	 </dd>
<dt>-s <code>style</code></dt>
<dd>
	 Specify the style of the dumped zone file.
	 Possible styles are "full" (default)
	 and "relative".
	 The full format is most suitable for processing
	 automatically by a separate script.
	 On the other hand, the relative format is more
	 human-readable and is thus suitable for editing by hand.
	 For named-checkzone
	 this does not cause any effects unless it dumps the zone
	 contents.
	 It also does not have any meaning if the output format
	 is not text.
	 </dd>
<dt>-S <code>mode</code></dt>
<dd>
	 Check if a SRV record refers to a CNAME.
 Possible modes are "fail",
 "warn" (default) and
 "ignore".
	 </dd>
<dt>-t <code>directory</code></dt>
<dd>
 Chroot to <code class="filename">directory</code> so that
 include
 directives in the configuration file are processed as if
 run by a similarly chrooted named.
 </dd>
<dt>-T <code>mode</code></dt>
<dd>
	 Check if Sender Policy Framework (SPF) records exist
	 and issues a warning if an SPF-formatted TXT record is
	 not also present. Possible modes are "warn"
	 (default), "ignore".
	 </dd>
<dt>-w <code>directory</code></dt>
<dd>
 chdir to <code class="filename">directory</code> so that
 relative
 filenames in master file $INCLUDE directives work. This
 is similar to the directory clause in
 <code class="filename">named.conf</code>.
 </dd>
<dt>-D</dt>
<dd>
 Dump zone file in canonical format.
	 This is always enabled for named-compilezone.
 </dd>
<dt>-W <code>mode</code></dt>
<dd>
 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 "warn" (default)
 and
 "ignore".
 </dd>
<dt>zonename</dt>
<dd>
 The domain name of the zone being checked.
 </dd>
<dt>filename</dt>
<dd>
 The name of the zone file.
 </dd>
</dl></div>
</div>
<div class="refsection">
<a name="id-1.14.24.9"></a><h2>RETURN VALUES</h2>
named-checkzone
 returns an exit status of 1 if
 errors were detected and 0 otherwise.
 
</div>
<div class="refsection">
<a name="id-1.14.24.10"></a><h2>SEE ALSO</h2>
named(8),
 named-checkconf(8),
 RFC 1035,
 BIND 9 Administrator Reference Manual.
 
</div>
</div>
<div class="navfooter">
<hr>
<table width="100%" summary="Navigation footer">
<tr>
<td width="40%" align="left">
<a accesskey="p" href="man.named-checkconf.html">Prev</a>�</td>
<td width="20%" align="center"><a accesskey="u" href="Bv9ARM.ch13.html">Up</a></td>
<td width="40%" align="right">�<a accesskey="n" href="man.named-journalprint.html">Next</a>
</td>
</tr>
<tr>
<td width="40%" align="left" valign="top">
named-checkconf�</td>
<td width="20%" align="center"><a accesskey="h" href="Bv9ARM.html">Home</a></td>
<td width="40%" align="right" valign="top">�named-journalprint
</td>
</tr>
</table>
</div>
BIND 9.11.36 (Extended Support Version)
</body>
</html>