dnssec-signzone.docbook 14.1 KB
Newer Older
1 2 3
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.0//EN"
               "http://www.oasis-open.org/docbook/xml/4.0/docbookx.dtd"
	       [<!ENTITY mdash "&#8212;">]>
Brian Wellington's avatar
Brian Wellington committed
4
<!--
Mark Andrews's avatar
Mark Andrews committed
5
 - Copyright (C) 2004, 2005  Internet Systems Consortium, Inc. ("ISC")
6
 - Copyright (C) 2000-2003  Internet Software Consortium.
Brian Wellington's avatar
Brian Wellington committed
7 8 9 10 11
 -
 - Permission to use, copy, modify, and distribute this software for any
 - purpose with or without fee is hereby granted, provided that the above
 - copyright notice and this permission notice appear in all copies.
 -
Mark Andrews's avatar
Mark Andrews committed
12 13 14 15 16 17 18
 - THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
 - REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
 - AND FITNESS.  IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
 - INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
 - LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
 - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
 - PERFORMANCE OF THIS SOFTWARE.
Brian Wellington's avatar
Brian Wellington committed
19
-->
Mark Andrews's avatar
Mark Andrews committed
20

Mark Andrews's avatar
Mark Andrews committed
21
<!-- $Id: dnssec-signzone.docbook,v 1.18 2005/06/24 00:17:08 marka Exp $ -->
22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37
<refentry>
  <refentryinfo>
    <date>June 30, 2000</date>
  </refentryinfo>

  <refmeta>
    <refentrytitle><application>dnssec-signzone</application></refentrytitle>
    <manvolnum>8</manvolnum>
    <refmiscinfo>BIND9</refmiscinfo>
  </refmeta>

  <refnamediv>
    <refname><application>dnssec-signzone</application></refname>
    <refpurpose>DNSSEC zone signing tool</refpurpose>
  </refnamediv>

38 39 40 41 42 43 44 45 46 47 48
  <docinfo>
    <copyright>
      <year>2004</year>
      <year>2005</year>
      <holder>Internet Systems Consortium, Inc. ("ISC")</holder>
    </copyright>
    <copyright>
      <year>2000</year>
      <year>2001</year>
      <year>2002</year>
      <year>2003</year>
Mark Andrews's avatar
Mark Andrews committed
49
      <holder>Internet Software Consortium.</holder>
50 51 52
    </copyright>
  </docinfo>

53 54 55 56 57 58 59 60
  <refsynopsisdiv>
    <cmdsynopsis>
      <command>dnssec-signzone</command>
      <arg><option>-a</option></arg>
      <arg><option>-c <replaceable class="parameter">class</replaceable></option></arg>
      <arg><option>-d <replaceable class="parameter">directory</replaceable></option></arg>
      <arg><option>-e <replaceable class="parameter">end-time</replaceable></option></arg>
      <arg><option>-f <replaceable class="parameter">output-file</replaceable></option></arg>
61
      <arg><option>-g</option></arg>
62
      <arg><option>-h</option></arg>
63
      <arg><option>-k <replaceable class="parameter">key</replaceable></option></arg>
64
      <arg><option>-l <replaceable class="parameter">domain</replaceable></option></arg>
65
      <arg><option>-i <replaceable class="parameter">interval</replaceable></option></arg>
66
      <arg><option>-j <replaceable class="parameter">jitter</replaceable></option></arg>
67 68 69 70
      <arg><option>-n <replaceable class="parameter">nthreads</replaceable></option></arg>
      <arg><option>-o <replaceable class="parameter">origin</replaceable></option></arg>
      <arg><option>-p</option></arg>
      <arg><option>-r <replaceable class="parameter">randomdev</replaceable></option></arg>
71
      <arg><option>-s <replaceable class="parameter">start-time</replaceable></option></arg>
72 73
      <arg><option>-t</option></arg>
      <arg><option>-v <replaceable class="parameter">level</replaceable></option></arg>
74
      <arg><option>-z</option></arg>
75 76 77 78 79 80 81
      <arg choice="req">zonefile</arg>
      <arg rep="repeat">key</arg>
    </cmdsynopsis>
  </refsynopsisdiv>

  <refsect1>
    <title>DESCRIPTION</title>
82 83 84 85 86 87 88
    <para><command>dnssec-signzone</command>
      signs a zone.  It generates
      NSEC and RRSIG records and produces a signed version of the
      zone. The security status of delegations from the signed zone
      (that is, whether the child zones are secure or not) is
      determined by the presence or absence of a
      <filename>keyset</filename> file for each child zone.
89 90 91 92 93 94 95 96 97
    </para>
  </refsect1>

  <refsect1>
    <title>OPTIONS</title>

    <variablelist>
      <varlistentry>
        <term>-a</term>
98 99 100 101 102
        <listitem>
          <para>
            Verify all generated signatures.
          </para>
        </listitem>
103 104 105 106
      </varlistentry>

      <varlistentry>
        <term>-c <replaceable class="parameter">class</replaceable></term>
107 108 109 110 111
        <listitem>
          <para>
            Specifies the DNS class of the zone.
          </para>
        </listitem>
112 113
      </varlistentry>

114 115
      <varlistentry>
        <term>-k <replaceable class="parameter">key</replaceable></term>
116 117 118 119 120 121
        <listitem>
          <para>
            Treat specified key as a key signing key ignoring any
            key flags.  This option may be specified multiple times.
          </para>
        </listitem>
122 123
      </varlistentry>

124 125
      <varlistentry>
        <term>-l <replaceable class="parameter">domain</replaceable></term>
126 127 128 129 130 131
        <listitem>
          <para>
            Generate a DLV set in addition to the key (DNSKEY) and DS sets.
            The domain is appended to the name of the records.
          </para>
        </listitem>
132 133
      </varlistentry>

134 135
      <varlistentry>
        <term>-d <replaceable class="parameter">directory</replaceable></term>
136 137 138 139 140 141
        <listitem>
          <para>
            Look for <filename>keyset</filename> files in
            <option>directory</option> as the directory
          </para>
        </listitem>
142 143
      </varlistentry>

144 145
      <varlistentry>
        <term>-g</term>
146 147 148 149 150 151
        <listitem>
          <para>
            Generate DS records for child zones from keyset files.
            Existing DS records will be removed.
          </para>
        </listitem>
152 153
      </varlistentry>

154 155
      <varlistentry>
        <term>-s <replaceable class="parameter">start-time</replaceable></term>
156 157 158 159 160 161 162 163 164 165 166 167
        <listitem>
          <para>
            Specify the date and time when the generated RRSIG records
            become valid.  This can be either an absolute or relative
            time.  An absolute start time is indicated by a number
            in YYYYMMDDHHMMSS notation; 20000530144500 denotes
            14:45:00 UTC on May 30th, 2000.  A relative start time is
            indicated by +N, which is N seconds from the current time.
            If no <option>start-time</option> is specified, the current
            time minus 1 hour (to allow for clock skew) is used.
          </para>
        </listitem>
168 169 170 171
      </varlistentry>

      <varlistentry>
        <term>-e <replaceable class="parameter">end-time</replaceable></term>
172 173 174 175 176 177 178 179 180 181 182
        <listitem>
          <para>
            Specify the date and time when the generated RRSIG records
            expire.  As with <option>start-time</option>, an absolute
            time is indicated in YYYYMMDDHHMMSS notation.  A time relative
            to the start time is indicated with +N, which is N seconds from
            the start time.  A time relative to the current time is
            indicated with now+N.  If no <option>end-time</option> is
            specified, 30 days from the start time is used as a default.
          </para>
        </listitem>
183 184 185 186
      </varlistentry>

      <varlistentry>
        <term>-f <replaceable class="parameter">output-file</replaceable></term>
187 188 189 190 191 192 193 194
        <listitem>
          <para>
            The name of the output file containing the signed zone.  The
            default is to append <filename>.signed</filename> to
            the
            input file.
          </para>
        </listitem>
195 196 197 198
      </varlistentry>

      <varlistentry>
        <term>-h</term>
199 200 201 202 203 204
        <listitem>
          <para>
            Prints a short summary of the options and arguments to
            <command>dnssec-signzone</command>.
          </para>
        </listitem>
205 206 207 208
      </varlistentry>

      <varlistentry>
        <term>-i <replaceable class="parameter">interval</replaceable></term>
209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229
        <listitem>
          <para>
            When a previously signed zone is passed as input, records
            may be resigned.  The <option>interval</option> option
            specifies the cycle interval as an offset from the current
            time (in seconds).  If a RRSIG record expires after the
            cycle interval, it is retained.  Otherwise, it is considered
            to be expiring soon, and it will be replaced.
          </para>
          <para>
            The default cycle interval is one quarter of the difference
            between the signature end and start times.  So if neither
            <option>end-time</option> or <option>start-time</option>
            are specified, <command>dnssec-signzone</command>
            generates
            signatures that are valid for 30 days, with a cycle
            interval of 7.5 days.  Therefore, if any existing RRSIG records
            are due to expire in less than 7.5 days, they would be
            replaced.
          </para>
        </listitem>
230 231
      </varlistentry>

232
      <varlistentry>
233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253
        <term>-j <replaceable class="parameter">jitter</replaceable></term>
        <listitem>
          <para>
            When signing a zone with a fixed signature lifetime, all
            RRSIG records issued at the time of signing expires
            simultaneously.  If the zone is incrementally signed, i.e.
            a previously signed zone is passed as input to the signer,
            all expired signatures has to be regenerated at about the
            same time.  The <option>jitter</option> option specifies a
            jitter window that will be used to randomize the signature
            expire time, thus spreading incremental signature
            regeneration over time.
          </para>
          <para>
            Signature lifetime jitter also to some extent benefits
            validators and servers by spreading out cache expiration,
            i.e. if large numbers of RRSIGs don't expire at the same time
            from all caches there will be less congestion than if all
            validators need to refetch at mostly the same time.
          </para>
        </listitem>
254 255
      </varlistentry>

256 257
      <varlistentry>
        <term>-n <replaceable class="parameter">ncpus</replaceable></term>
258 259 260 261 262 263
        <listitem>
          <para>
            Specifies the number of threads to use.  By default, one
            thread is started for each detected CPU.
          </para>
        </listitem>
264 265 266 267
      </varlistentry>

      <varlistentry>
        <term>-o <replaceable class="parameter">origin</replaceable></term>
268 269 270 271 272 273
        <listitem>
          <para>
            The zone origin.  If not specified, the name of the zone file
            is assumed to be the origin.
          </para>
        </listitem>
274 275 276 277
      </varlistentry>

      <varlistentry>
        <term>-p</term>
278 279 280 281 282 283 284 285
        <listitem>
          <para>
            Use pseudo-random data when signing the zone.  This is faster,
            but less secure, than using real random data.  This option
            may be useful when signing large zones or when the entropy
            source is limited.
          </para>
        </listitem>
286 287 288 289
      </varlistentry>

      <varlistentry>
        <term>-r <replaceable class="parameter">randomdev</replaceable></term>
290 291 292 293 294 295 296 297 298 299 300 301 302
        <listitem>
          <para>
            Specifies the source of randomness.  If the operating
            system does not provide a <filename>/dev/random</filename>
            or equivalent device, the default source of randomness
            is keyboard input.  <filename>randomdev</filename>
            specifies
            the name of a character device or file containing random
            data to be used instead of the default.  The special value
            <filename>keyboard</filename> indicates that keyboard
            input should be used.
          </para>
        </listitem>
303 304 305 306
      </varlistentry>

      <varlistentry>
        <term>-t</term>
307 308 309 310 311
        <listitem>
          <para>
            Print statistics at completion.
          </para>
        </listitem>
312 313 314 315
      </varlistentry>

      <varlistentry>
        <term>-v <replaceable class="parameter">level</replaceable></term>
316 317 318 319 320
        <listitem>
          <para>
            Sets the debugging level.
          </para>
        </listitem>
321 322
      </varlistentry>

323 324
      <varlistentry>
        <term>-z</term>
325 326 327 328 329
        <listitem>
          <para>
            Ignore KSK flag on key when determining what to sign.
          </para>
        </listitem>
330 331
      </varlistentry>

332 333
      <varlistentry>
        <term>zonefile</term>
334 335 336 337 338
        <listitem>
          <para>
            The file containing the zone to be signed.
          </para>
        </listitem>
339 340 341 342
      </varlistentry>

      <varlistentry>
        <term>key</term>
343 344 345 346 347 348 349
        <listitem>
          <para>
            The keys used to sign the zone.  If no keys are specified, the
            default all zone keys that have private key files in the
            current directory.
          </para>
        </listitem>
350 351 352 353 354 355 356 357
      </varlistentry>

    </variablelist>
  </refsect1>

  <refsect1>
    <title>EXAMPLE</title>
    <para>
358 359 360 361 362 363 364 365
      The following command signs the <userinput>example.com</userinput>
      zone with the DSA key generated in the <command>dnssec-keygen</command>
      man page.  The zone's keys must be in the zone.  If there are
      <filename>keyset</filename> files associated with child
      zones,
      they must be in the current directory.
      <userinput>example.com</userinput>, the following command would be
      issued:
366
    </para>
367 368
    <para><userinput>dnssec-signzone -o example.com db.example.com
        Kexample.com.+003+26160</userinput>
369 370
    </para>
    <para>
371
      The command would print a string of the form:
372 373
    </para>
    <para>
374 375 376 377 378
      In this example, <command>dnssec-signzone</command> creates
      the file <filename>db.example.com.signed</filename>.  This
      file
      should be referenced in a zone statement in a
      <filename>named.conf</filename> file.
379 380 381 382 383
    </para>
  </refsect1>

  <refsect1>
    <title>SEE ALSO</title>
384 385
    <para><citerefentry>
        <refentrytitle>dnssec-keygen</refentrytitle><manvolnum>8</manvolnum>
386 387 388 389 390 391 392 393
      </citerefentry>,
      <citetitle>BIND 9 Administrator Reference Manual</citetitle>,
      <citetitle>RFC 2535</citetitle>.
    </para>
  </refsect1>

  <refsect1>
    <title>AUTHOR</title>
394
    <para><corpauthor>Internet Systems Consortium</corpauthor>
395 396 397
    </para>
  </refsect1>

398
</refentry><!--
399 400 401 402
 - Local variables:
 - mode: sgml
 - End:
-->