0N/A - Copyright (C) 2004, 2005 Internet Systems Consortium, Inc. ("ISC") 0N/A - Copyright (C) 2000-2003 Internet Software Consortium. 0N/A - Permission to use, copy, modify, and distribute this software for any 0N/A - purpose with or without fee is hereby granted, provided that the above 5056N/A - copyright notice and this permission notice appear in all copies. 0N/A - THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH 0N/A - REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY 0N/A - AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT, 0N/A - INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM 0N/A - LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE 3516N/A - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR 0N/A - PERFORMANCE OF THIS SOFTWARE. 0N/ACONTENT="Modular DocBook HTML Stylesheet Version 1.79"></
HEAD 0N/A>dnssec-signzone</
SPAN 0N/A> -- DNSSEC zone signing tool</
DIV 0N/ACLASS="REFSYNOPSISDIV" > 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
> file for each child zone.
> Verify all generated signatures.
> Specifies the DNS class of the zone.
> Treat specified key as a key signing key ignoring any
key flags. This option may be specified multiple times.
> Generate a DLV set in addition to the key (DNSKEY) and DS sets.
The domain is appended to the name of the records.
> Generate DS records for child zones from keyset files.
Existing DS records will be removed.
> 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.
> is specified, the current
time minus 1 hour (to allow for clock skew) is used.
> Specify the date and time when the generated RRSIG records
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 <
CODE specified, 30 days from the start time is used as a default.
> The name of the output file containing the signed zone. The
> Prints a short summary of the options and arguments to
> When a previously signed zone is passed as input, records
may be resigned. The <
CODE 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.
> The default cycle interval is one quarter of the difference
between the signature end and start times. So if neither
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
> 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
jitter window that will be used to randomize the signature
expire time, thus spreading incremental signature
> 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.
> Specifies the number of threads to use. By default, one
thread is started for each detected CPU.
> The zone origin. If not specified, the name of the zone file
is assumed to be the origin.
> 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
> Specifies the source of randomness. If the operating
system does not provide a <
TT or equivalent device, the default source of randomness
the name of a character device or file containing random
data to be used instead of the default. The special value
> indicates that keyboard
> Print statistics at completion.
> Sets the debugging level.
> Ignore KSK flag on key when determining what to sign.
> The file containing the zone to be signed.
Sets the debugging level.
> The keys used to sign the zone. If no keys are specified, the
default all zone keys that have private key files in the
> The following command signs the <
KBD zone with the DSA key generated in the <
B man page. The zone's keys must be in the zone. If there are
> files associated with child zones,
they must be in the current directory.
>, the following command would be
> The command would print a string of the form:
should be referenced in a zone statement in a
>BIND 9 Administrator Reference Manual</
I> Internet Systems Consortium