a4544a5a0e622ef69e38641f87ab1b5685e05911Phill Cunnington

218850cd2701baccfca6d95a95e7bcbffe1293cePeter Major<refentry xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="man.dnssec-coverage">

218850cd2701baccfca6d95a95e7bcbffe1293cePeter Major <info>

218850cd2701baccfca6d95a95e7bcbffe1293cePeter Major <date>2014-01-11</date>

218850cd2701baccfca6d95a95e7bcbffe1293cePeter Major </info>

218850cd2701baccfca6d95a95e7bcbffe1293cePeter Major <refentryinfo>

3fc1b5e9b2ff286cd528a06154cc998198de1e70Craig McDonnell <corpname>ISC</corpname>

c42550c0e86e2c3f821f5e754ea8ba52d8bb5427Tony Bamford <corpauthor>Internet Systems Consortium, Inc.</corpauthor>

3fc1b5e9b2ff286cd528a06154cc998198de1e70Craig McDonnell </refentryinfo>

218850cd2701baccfca6d95a95e7bcbffe1293cePeter Major

218850cd2701baccfca6d95a95e7bcbffe1293cePeter Major <refmeta>

218850cd2701baccfca6d95a95e7bcbffe1293cePeter Major <refentrytitle><application>dnssec-coverage</application></refentrytitle>

218850cd2701baccfca6d95a95e7bcbffe1293cePeter Major <manvolnum>8</manvolnum>

218850cd2701baccfca6d95a95e7bcbffe1293cePeter Major <refmiscinfo>BIND9</refmiscinfo>

218850cd2701baccfca6d95a95e7bcbffe1293cePeter Major </refmeta>

218850cd2701baccfca6d95a95e7bcbffe1293cePeter Major

218850cd2701baccfca6d95a95e7bcbffe1293cePeter Major <refnamediv>

218850cd2701baccfca6d95a95e7bcbffe1293cePeter Major <refname><application>dnssec-coverage</application></refname>

218850cd2701baccfca6d95a95e7bcbffe1293cePeter Major <refpurpose>checks future DNSKEY coverage for a zone</refpurpose>

218850cd2701baccfca6d95a95e7bcbffe1293cePeter Major </refnamediv>

218850cd2701baccfca6d95a95e7bcbffe1293cePeter Major

218850cd2701baccfca6d95a95e7bcbffe1293cePeter Major <docinfo>

218850cd2701baccfca6d95a95e7bcbffe1293cePeter Major <copyright>

218850cd2701baccfca6d95a95e7bcbffe1293cePeter Major <year>2013</year>

218850cd2701baccfca6d95a95e7bcbffe1293cePeter Major <year>2014</year>

218850cd2701baccfca6d95a95e7bcbffe1293cePeter Major <year>2015</year>

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

218850cd2701baccfca6d95a95e7bcbffe1293cePeter Major </copyright>

218850cd2701baccfca6d95a95e7bcbffe1293cePeter Major </docinfo>

218850cd2701baccfca6d95a95e7bcbffe1293cePeter Major

218850cd2701baccfca6d95a95e7bcbffe1293cePeter Major <refsynopsisdiv>

218850cd2701baccfca6d95a95e7bcbffe1293cePeter Major <cmdsynopsis sepchar=" ">

218850cd2701baccfca6d95a95e7bcbffe1293cePeter Major <command>dnssec-coverage</command>

218850cd2701baccfca6d95a95e7bcbffe1293cePeter Major <arg choice="opt" rep="norepeat"><option>-K <replaceable class="parameter">directory</replaceable></option></arg>

218850cd2701baccfca6d95a95e7bcbffe1293cePeter Major <arg choice="opt" rep="norepeat"><option>-l <replaceable class="parameter">length</replaceable></option></arg>

218850cd2701baccfca6d95a95e7bcbffe1293cePeter Major <arg choice="opt" rep="norepeat"><option>-f <replaceable class="parameter">file</replaceable></option></arg>

218850cd2701baccfca6d95a95e7bcbffe1293cePeter Major <arg choice="opt" rep="norepeat"><option>-d <replaceable class="parameter">DNSKEY TTL</replaceable></option></arg>

218850cd2701baccfca6d95a95e7bcbffe1293cePeter Major <arg choice="opt" rep="norepeat"><option>-m <replaceable class="parameter">max TTL</replaceable></option></arg>

218850cd2701baccfca6d95a95e7bcbffe1293cePeter Major <arg choice="opt" rep="norepeat"><option>-r <replaceable class="parameter">interval</replaceable></option></arg>

218850cd2701baccfca6d95a95e7bcbffe1293cePeter Major <arg choice="opt" rep="norepeat"><option>-c <replaceable class="parameter">compilezone path</replaceable></option></arg>

218850cd2701baccfca6d95a95e7bcbffe1293cePeter Major <arg choice="opt" rep="norepeat"><option>-k</option></arg>

218850cd2701baccfca6d95a95e7bcbffe1293cePeter Major <arg choice="opt" rep="norepeat"><option>-z</option></arg>

218850cd2701baccfca6d95a95e7bcbffe1293cePeter Major <arg choice="opt" rep="norepeat">zone</arg>

218850cd2701baccfca6d95a95e7bcbffe1293cePeter Major </cmdsynopsis>

218850cd2701baccfca6d95a95e7bcbffe1293cePeter Major </refsynopsisdiv>

c42550c0e86e2c3f821f5e754ea8ba52d8bb5427Tony Bamford

218850cd2701baccfca6d95a95e7bcbffe1293cePeter Major <refsection><info><title>DESCRIPTION</title></info>

c42550c0e86e2c3f821f5e754ea8ba52d8bb5427Tony Bamford

218850cd2701baccfca6d95a95e7bcbffe1293cePeter Major <para><command>dnssec-coverage</command>

218850cd2701baccfca6d95a95e7bcbffe1293cePeter Major verifies that the DNSSEC keys for a given zone or a set of zones

218850cd2701baccfca6d95a95e7bcbffe1293cePeter Major have timing metadata set properly to ensure no future lapses in DNSSEC

218850cd2701baccfca6d95a95e7bcbffe1293cePeter Major coverage.

218850cd2701baccfca6d95a95e7bcbffe1293cePeter Major </para>

218850cd2701baccfca6d95a95e7bcbffe1293cePeter Major <para>

218850cd2701baccfca6d95a95e7bcbffe1293cePeter Major If <option>zone</option> is specified, then keys found in

c42550c0e86e2c3f821f5e754ea8ba52d8bb5427Tony Bamford the key repository matching that zone are scanned, and an ordered

218850cd2701baccfca6d95a95e7bcbffe1293cePeter Major list is generated of the events scheduled for that key (i.e.,

c42550c0e86e2c3f821f5e754ea8ba52d8bb5427Tony Bamford publication, activation, inactivation, deletion). The list of

218850cd2701baccfca6d95a95e7bcbffe1293cePeter Major events is walked in order of occurrence. Warnings are generated

218850cd2701baccfca6d95a95e7bcbffe1293cePeter Major if any event is scheduled which could cause the zone to enter a

218850cd2701baccfca6d95a95e7bcbffe1293cePeter Major state in which validation failures might occur: for example, if

218850cd2701baccfca6d95a95e7bcbffe1293cePeter Major the number of published or active keys for a given algorithm drops

218850cd2701baccfca6d95a95e7bcbffe1293cePeter Major to zero, or if a key is deleted from the zone too soon after a new

key is rolled, and cached data signed by the prior key has not had

time to expire from resolver caches.

</para>

<para>

If <option>zone</option> is not specified, then all keys in the

key repository will be scanned, and all zones for which there are

keys will be analyzed. (Note: This method of reporting is only

accurate if all the zones that have keys in a given repository

share the same TTL parameters.)

</para>

</refsection>

<refsection><info><title>OPTIONS</title></info>

<variablelist>

<varlistentry>

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

<listitem>

<para>

Sets the directory in which keys can be found. Defaults to the

current working directory.

</para>

</listitem>

</varlistentry>

<varlistentry>

<term>-f <replaceable class="parameter">file</replaceable></term>

<listitem>

<para>

If a <option>file</option> is specified, then the zone is

read from that file; the largest TTL and the DNSKEY TTL are

determined directly from the zone data, and the

<option>-m</option> and <option>-d</option> options do

not need to be specified on the command line.

</para>

</listitem>

</varlistentry>

<varlistentry>

<term>-l <replaceable class="parameter">duration</replaceable></term>

<listitem>

<para>

The length of time to check for DNSSEC coverage. Key events

scheduled further into the future than <option>duration</option>

will be ignored, and assumed to be correct.

</para>

<para>

The value of <option>duration</option> can be set in seconds,

or in larger units of time by adding a suffix: 'mi' for minutes,

'h' for hours, 'd' for days, 'w' for weeks, 'mo' for months,

'y' for years.

</para>

</listitem>

</varlistentry>

<varlistentry>

<term>-m <replaceable class="parameter">maximum TTL</replaceable></term>

<listitem>

<para>

Sets the value to be used as the maximum TTL for the zone or

zones being analyzed when determining whether there is a

possibility of validation failure. When a zone-signing key is

deactivated, there must be enough time for the record in the

zone with the longest TTL to have expired from resolver caches

before that key can be purged from the DNSKEY RRset. If that

condition does not apply, a warning will be generated.

</para>

<para>

The length of the TTL can be set in seconds, or in larger units

of time by adding a suffix: 'mi' for minutes, 'h' for hours,

'd' for days, 'w' for weeks, 'mo' for months, 'y' for years.

</para>

<para>

This option is mandatory unless the <option>-f</option> has

been used to specify a zone file. (If <option>-f</option> has

been specified, this option may still be used; it will override

the value found in the file.)

</para>

</listitem>

</varlistentry>

<varlistentry>

<term>-d <replaceable class="parameter">DNSKEY TTL</replaceable></term>

<listitem>

<para>

Sets the value to be used as the DNSKEY TTL for the zone or

zones being analyzed when determining whether there is a

possibility of validation failure. When a key is rolled (that

is, replaced with a new key), there must be enough time

for the old DNSKEY RRset to have expired from resolver caches

before the new key is activated and begins generating

signatures. If that condition does not apply, a warning

will be generated.

</para>

<para>

The length of the TTL can be set in seconds, or in larger units

of time by adding a suffix: 'mi' for minutes, 'h' for hours,

'd' for days, 'w' for weeks, 'mo' for months, 'y' for years.

</para>

<para>

This option is mandatory unless the <option>-f</option> has

been used to specify a zone file, or a default key TTL was

set with the <option>-L</option> to

<command>dnssec-keygen</command>. (If either of those is true,

this option may still be used; it will override the value found

in the zone or key file.)

</para>

</listitem>

</varlistentry>

<varlistentry>

<term>-r <replaceable class="parameter">resign interval</replaceable></term>

<listitem>

<para>

Sets the value to be used as the resign interval for the zone

or zones being analyzed when determining whether there is a

possibility of validation failure. This value defaults to

22.5 days, which is also the default in

<command>named</command>. However, if it has been changed

by the <option>sig-validity-interval</option> option in

<filename>named.conf</filename>, then it should also be

changed here.

</para>

<para>

The length of the interval can be set in seconds, or in larger

units of time by adding a suffix: 'mi' for minutes, 'h' for hours,

'd' for days, 'w' for weeks, 'mo' for months, 'y' for years.

</para>

</listitem>

</varlistentry>

<varlistentry>

<term>-k</term>

<listitem>

<para>

Only check KSK coverage; ignore ZSK events. Cannot be

used with <option>-z</option>.

</para>

</listitem>

</varlistentry>

<varlistentry>

<term>-z</term>

<listitem>

<para>

Only check ZSK coverage; ignore KSK events. Cannot be

used with <option>-k</option>.

</para>

</listitem>

</varlistentry>

<varlistentry>

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

<listitem>

<para>

Specifies a path to a <command>named-compilezone</command> binary.

Used for testing.

</para>

</listitem>

</varlistentry>

</variablelist>

</refsection>

<refsection><info><title>SEE ALSO</title></info>

<para>

<citerefentry>

<refentrytitle>dnssec-checkds</refentrytitle><manvolnum>8</manvolnum>

</citerefentry>,

<citerefentry>

<refentrytitle>dnssec-dsfromkey</refentrytitle><manvolnum>8</manvolnum>

</citerefentry>,

<citerefentry>

<refentrytitle>dnssec-keygen</refentrytitle><manvolnum>8</manvolnum>

</citerefentry>,

<citerefentry>

<refentrytitle>dnssec-signzone</refentrytitle><manvolnum>8</manvolnum>

</citerefentry>

</para>

</refsection>

</refentry>