dnssec-verify.html revision dd1ce8b52478fa98c844720af9e77fae2978f18d
0b74a2f80aba476dc8be8bc1c63891fc53945986vboxsync<!--
0b74a2f80aba476dc8be8bc1c63891fc53945986vboxsync - Copyright (C) 2012, 2014 Internet Systems Consortium, Inc. ("ISC")
0b74a2f80aba476dc8be8bc1c63891fc53945986vboxsync -
0b74a2f80aba476dc8be8bc1c63891fc53945986vboxsync - Permission to use, copy, modify, and/or distribute this software for any
0b74a2f80aba476dc8be8bc1c63891fc53945986vboxsync - purpose with or without fee is hereby granted, provided that the above
a0352d06ef77cf45a08eb08b4d65d570b7b294cbvboxsync - copyright notice and this permission notice appear in all copies.
0b74a2f80aba476dc8be8bc1c63891fc53945986vboxsync -
0b74a2f80aba476dc8be8bc1c63891fc53945986vboxsync - THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
0b74a2f80aba476dc8be8bc1c63891fc53945986vboxsync - REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
0b74a2f80aba476dc8be8bc1c63891fc53945986vboxsync - AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
0b74a2f80aba476dc8be8bc1c63891fc53945986vboxsync - INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
0b74a2f80aba476dc8be8bc1c63891fc53945986vboxsync - LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
0b74a2f80aba476dc8be8bc1c63891fc53945986vboxsync - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
0b74a2f80aba476dc8be8bc1c63891fc53945986vboxsync - PERFORMANCE OF THIS SOFTWARE.
0b74a2f80aba476dc8be8bc1c63891fc53945986vboxsync-->
0b74a2f80aba476dc8be8bc1c63891fc53945986vboxsync<!-- $Id$ -->
0b74a2f80aba476dc8be8bc1c63891fc53945986vboxsync<html>
0b74a2f80aba476dc8be8bc1c63891fc53945986vboxsync<head>
0b74a2f80aba476dc8be8bc1c63891fc53945986vboxsync<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
0b74a2f80aba476dc8be8bc1c63891fc53945986vboxsync<title>dnssec-verify</title>
0b74a2f80aba476dc8be8bc1c63891fc53945986vboxsync<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
0b74a2f80aba476dc8be8bc1c63891fc53945986vboxsync</head>
0b74a2f80aba476dc8be8bc1c63891fc53945986vboxsync<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en">
0b74a2f80aba476dc8be8bc1c63891fc53945986vboxsync<a name="man.dnssec-verify"></a><div class="titlepage"></div>
0b74a2f80aba476dc8be8bc1c63891fc53945986vboxsync<div class="refnamediv">
0b74a2f80aba476dc8be8bc1c63891fc53945986vboxsync<h2>Name</h2>
0b74a2f80aba476dc8be8bc1c63891fc53945986vboxsync<p><span class="application">dnssec-verify</span> &#8212; DNSSEC zone verification tool</p>
0b74a2f80aba476dc8be8bc1c63891fc53945986vboxsync</div>
0b74a2f80aba476dc8be8bc1c63891fc53945986vboxsync<div class="refsynopsisdiv">
0b74a2f80aba476dc8be8bc1c63891fc53945986vboxsync<h2>Synopsis</h2>
0b74a2f80aba476dc8be8bc1c63891fc53945986vboxsync<div class="cmdsynopsis"><p><code class="command">dnssec-verify</code> [<code class="option">-c <em class="replaceable"><code>class</code></em></code>] [<code class="option">-E <em class="replaceable"><code>engine</code></em></code>] [<code class="option">-I <em class="replaceable"><code>input-format</code></em></code>] [<code class="option">-o <em class="replaceable"><code>origin</code></em></code>] [<code class="option">-v <em class="replaceable"><code>level</code></em></code>] [<code class="option">-x</code>] [<code class="option">-z</code>] {zonefile}</p></div>
a0352d06ef77cf45a08eb08b4d65d570b7b294cbvboxsync</div>
0b74a2f80aba476dc8be8bc1c63891fc53945986vboxsync<div class="refsect1" lang="en">
0b74a2f80aba476dc8be8bc1c63891fc53945986vboxsync<a name="id2543394"></a><h2>DESCRIPTION</h2>
0b74a2f80aba476dc8be8bc1c63891fc53945986vboxsync<p><span><strong class="command">dnssec-verify</strong></span>
0b74a2f80aba476dc8be8bc1c63891fc53945986vboxsync verifies that a zone is fully signed for each algorithm found
0b74a2f80aba476dc8be8bc1c63891fc53945986vboxsync in the DNSKEY RRset for the zone, and that the NSEC / NSEC3
0b74a2f80aba476dc8be8bc1c63891fc53945986vboxsync chains are complete.
0b74a2f80aba476dc8be8bc1c63891fc53945986vboxsync </p>
0b74a2f80aba476dc8be8bc1c63891fc53945986vboxsync</div>
0b74a2f80aba476dc8be8bc1c63891fc53945986vboxsync<div class="refsect1" lang="en">
<a name="id2543405"></a><h2>OPTIONS</h2>
<div class="variablelist"><dl>
<dt><span class="term">-c <em class="replaceable"><code>class</code></em></span></dt>
<dd><p>
Specifies the DNS class of the zone.
</p></dd>
<dt><span class="term">-E <em class="replaceable"><code>engine</code></em></span></dt>
<dd>
<p>
Specifies the cryptographic hardware to use, when applicable.
</p>
<p>
When BIND is built with OpenSSL PKCS#11 support, this defaults
to the string "pkcs11", which identifies an OpenSSL engine
that can drive a cryptographic accelerator or hardware service
module. When BIND is built with native PKCS#11 cryptography
(--enable-native-pkcs11), it defaults to the path of the PKCS#11
provider library specified via "--with-pkcs11".
</p>
</dd>
<dt><span class="term">-I <em class="replaceable"><code>input-format</code></em></span></dt>
<dd><p>
The format of the input zone file.
Possible formats are <span><strong class="command">"text"</strong></span> (default)
and <span><strong class="command">"raw"</strong></span>.
This option is primarily intended to be used for dynamic
signed zones so that the dumped zone file in a non-text
format containing updates can be verified independently.
The use of this option does not make much sense for
non-dynamic zones.
</p></dd>
<dt><span class="term">-o <em class="replaceable"><code>origin</code></em></span></dt>
<dd><p>
The zone origin. If not specified, the name of the zone file
is assumed to be the origin.
</p></dd>
<dt><span class="term">-v <em class="replaceable"><code>level</code></em></span></dt>
<dd><p>
Sets the debugging level.
</p></dd>
<dt><span class="term">-x</span></dt>
<dd><p>
Only verify that the DNSKEY RRset is signed with key-signing
keys. Without this flag, it is assumed that the DNSKEY RRset
will be signed by all active keys. When this flag is set,
it will not be an error if the DNSKEY RRset is not signed
by zone-signing keys. This corresponds to the <code class="option">-x</code>
option in <span><strong class="command">dnssec-signzone</strong></span>.
</p></dd>
<dt><span class="term">-z</span></dt>
<dd>
<p>
Ignore the KSK flag on the keys when determining whether
the zone if correctly signed. Without this flag it is
assumed that there will be a non-revoked, self-signed
DNSKEY with the KSK flag set for each algorithm and
that RRsets other than DNSKEY RRset will be signed with
a different DNSKEY without the KSK flag set.
</p>
<p>
With this flag set, we only require that for each algorithm,
there will be at least one non-revoked, self-signed DNSKEY,
regardless of the KSK flag state, and that other RRsets
will be signed by a non-revoked key for the same algorithm
that includes the self-signed key; the same key may be used
for both purposes. This corresponds to the <code class="option">-z</code>
option in <span><strong class="command">dnssec-signzone</strong></span>.
</p>
</dd>
<dt><span class="term">zonefile</span></dt>
<dd><p>
The file containing the zone to be signed.
</p></dd>
</dl></div>
</div>
<div class="refsect1" lang="en">
<a name="id2543635"></a><h2>SEE ALSO</h2>
<p>
<span class="citerefentry"><span class="refentrytitle">dnssec-signzone</span>(8)</span>,
<em class="citetitle">BIND 9 Administrator Reference Manual</em>,
<em class="citetitle">RFC 4033</em>.
</p>
</div>
<div class="refsect1" lang="en">
<a name="id2543660"></a><h2>AUTHOR</h2>
<p><span class="corpauthor">Internet Systems Consortium</span>
</p>
</div>
</div></body>
</html>