The dnssec-signzone utility 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 signedkey file for each child zone.
OPTIONS
The following options are supported:
-a
Verify all generated signatures.
-cclass
Specify the DNS class of the zone.
-ddirectory
Look for signedkey files in directory.
-eend-time
Specify the date and time when the generated RRSIG records expire. As with start-time, 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 end-time is specified, 30 days from the start time is used as a default.
-foutput-file
The name of the output file containing the signed zone. The default is to append .signed to the input file name.
-g
Generate DS records for child zones from keyset files. Existing DS records will be removed.
-h
Prints a short summary of the options and arguments to dnssec-signzone().
-iinterval
Specify the cycle interval as an offset from the current time (in seconds). When a previously signed zone is passed as input, records could be resigned. If a SIG record expires after the cycle interval, it is retained. Otherwise, it is considered to be expiring
soon and will be replaced. The default cycle interval is one quarter of the difference between the signature end and start times. If neither end-time or start-time are specified, dnssec-signzone generates signatures that
are valid for 30 days, with a cycle interval of 7.5 days. Any existing SIG records due to expire in less than 7.5 days would be replaced.
-kkey
Treat specified key as a key-signing key, ignoring any key flags. This option can be specified multiple times.
-kkey
Treat specified key as a key-signing key, ignoring any key flags. This option can be specified multiple times.
-ldomain
Generate a DLV set in addition to the key (DNSKEY) and DS sets. The domain is appended to the name of the records.
-oorigin
Specify the zone origin. If not specified, the name of the zone file is assumed to be the origin.
-p
Use pseudo-random data when signing the zone. This is faster, but less secure, than using real random data. This option can be useful when signing large zones or when the entropy source is limited.
-rrandomdev
Specify the source of randomness. If the operating system does not provide a /dev/random or equivalent device, the default source of randomness is keyboard input. The randomdev argument specifies the name of a character device or
file containing random data to be used instead of the default. The special value keyboard indicates that keyboard input should be used.
-sstart-time
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 start-time is specified, the current time minus one hour (to allow for clock skew) is used.
-t
Print statistics at completion.
-vlevel
Set the debugging level.
OPERANDS
The following options are supported:
zonefile
The file containing the zone to be signed. This file sets the debugging level.
key
The keys used to sign the zone. If no keys are specified, the default is all zone keys that have private key files in the current directory.
EXAMPLES
Example 1 Sign a zone with a DSA key.
The following command signs the example.com zone with the DSA key generated in the example on the dnssec-keygen(1M) manual page.
The zone's keys must be in the zone. If there are signedkey files associated with this zone or any child zones, they must be in the current directory.
dnssec-signzone -o example.com db.example.com
The command would print a string of the form:
Kexample.com.+003+26160
In this example, dnssec-signzone creates the file db.example.com.signed. This file should be referenced in a zone statement in a named.conf file.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes: