ddnnsssseecc--ssiiggnnzzoonnee 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 _k_e_y_s_e_t file for each child zone.
-a Verify all generated signatures.
-c _c_l_a_s_s Specifies the DNS class of the zone.
-C Compatibility mode: Generate a _k_e_y_s_e_t_-_z_o_n_e_n_a_m_e file in addition to _d_s_s_e_t_-_z_o_n_e_n_a_m_e when signing a zone, for use by older versions of ddnnsssseecc--ssiiggnnzzoonnee.
-d _d_i_r_e_c_t_o_r_y Look for _d_s_s_e_t_- or _k_e_y_s_e_t_- files in ddiirreeccttoorryy.
-E _e_n_g_i_n_e Uses a crypto hardware (OpenSSL engine) for the crypto operations it supports, for instance signing with private keys from a secure key store. When compiled with PKCS#11 support it defaults to pkcs11; the empty name resets it to no engine.
-g Generate DS records for child zones from _d_s_s_e_t_- or _k_e_y_s_e_t_- file. Existing DS records will be removed.
-K _d_i_r_e_c_t_o_r_y Key repository: Specify a directory to search for DNSSEC keys. If not specified, defaults to the current directory.
-k _k_e_y Treat specified key as a key signing key ignoring any key flags. This option may be specified multiple times.
-l _d_o_m_a_i_n Generate a DLV set in addition to the key (DNSKEY) and DS sets. The domain is appended to the name of the records.
-s _s_t_a_r_t_-_t_i_m_e 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 ssttaarrtt--ttiimmee is specified, the current time minus 1 hour (to allow for clock skew) is used.
-e _e_n_d_-_t_i_m_e Specify the date and time when the generated RRSIG records expire. As with ssttaarrtt--ttiimmee, 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 eenndd--ttiimmee is specified, 30 days from the start time is used as a default. eenndd--ttiimmee must be later than ssttaarrtt--ttiimmee.
-f _o_u_t_p_u_t_-_f_i_l_e The name of the output file containing the signed zone. The default is to append _._s_i_g_n_e_d to the input filename.
-h Prints a short summary of the options and arguments to ddnnsssseecc--ssiiggnnzzoonnee.
-i _i_n_t_e_r_v_a_l
When a previously-signed zone is passed as input, records may be resigned. The
iinntteerrvvaall
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.
The default cycle interval is one quarter of the difference between the signature end and start times. So if neither
eenndd--ttiimmee
or
ssttaarrtt--ttiimmee
are specified,
ddnnsssseecc--ssiiggnnzzoonnee
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.
-I _i_n_p_u_t_-_f_o_r_m_a_t The format of the input zone file. Possible formats are ""tteexxtt"" (default) and ""rraaww"". 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 signed directly. The use of this option does not make much sense for non-dynamic zones.
-j _j_i_t_t_e_r
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 have to be regenerated at about the same time. The
jjiitttteerr
option specifies a jitter window that will be used to randomize the signature expire time, thus spreading incremental signature regeneration over time.
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.
-n _n_c_p_u_s Specifies the number of threads to use. By default, one thread is started for each detected CPU.
-N _s_o_a_-_s_e_r_i_a_l_-_f_o_r_m_a_t The SOA serial number format of the signed zone. Possible formats are ""kkeeeepp"" (default), ""iinnccrreemmeenntt"" and ""uunniixxttiimmee"".
""kkeeeepp"" Do not modify the SOA serial number.
""iinnccrreemmeenntt"" Increment the SOA serial number using RFC 1982 arithmetics.
""uunniixxttiimmee"" Set the SOA serial number to the number of seconds since epoch.
-o _o_r_i_g_i_n The zone origin. If not specified, the name of the zone file is assumed to be the origin.
-O _o_u_t_p_u_t_-_f_o_r_m_a_t The format of the output file containing the signed zone. Possible formats are ""tteexxtt"" (default) and ""rraaww"".
-p 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.
-P
Disable post sign verification tests.
The post sign verification test ensures that for each algorithm in use there is at least one non revoked self signed KSK key, that all revoked KSK keys are self signed, and that all records in the zone are signed by the algorithm. This option skips these tests.
-r _r_a_n_d_o_m_d_e_v Specifies the source of randomness. If the operating system does not provide a _/_d_e_v_/_r_a_n_d_o_m or equivalent device, the default source of randomness is keyboard input. _r_a_n_d_o_m_d_e_v specifies the name of a character device or file containing random data to be used instead of the default. The special value _k_e_y_b_o_a_r_d indicates that keyboard input should be used.
-S
Smart signing: Instructs
ddnnsssseecc--ssiiggnnzzoonnee
to search the key repository for keys that match the zone being signed, and to include them in the zone if appropriate.
When a key is found, its timing metadata is examined to determine how it should be used, according to the following rules. Each successive rule takes priority over the prior ones:
If no timing metadata has been set for the key, the key is published in the zone and used to sign the zone.
If the key's publication date is set and is in the past, the key is published in the zone.
If the key's activation date is set and in the past, the key is published (regardless of publication date) and used to sign the zone.
If the key's revocation date is set and in the past, and the key is published, then the key is revoked, and the revoked key is used to sign the zone.
If either of the key's unpublication or deletion dates are set and in the past, the key is NOT published or used to sign the zone, regardless of any other metadata.
-T _t_t_l Specifies the TTL to be used for new DNSKEY records imported into the zone from the key repository. If not specified, the default is the minimum TTL value from the zone's SOA record. This option is ignored when signing without --SS, since DNSKEY records are not imported from the key repository in that case. It is also ignored if there are any pre-existing DNSKEY records at the zone apex, in which case new records' TTL values will be set to match them.
-t Print statistics at completion.
-u Update NSEC/NSEC3 chain when re-signing a previously signed zone. With this option, a zone signed with NSEC can be switched to NSEC3, or a zone signed with NSEC3 can be switch to NSEC or to NSEC3 with different parameters. Without this option, ddnnsssseecc--ssiiggnnzzoonnee will retain the existing chain when re-signing.
-v _l_e_v_e_l Sets the debugging level.
-x Only sign the DNSKEY RRset with key-signing keys, and omit signatures from zone-signing keys. (This is similar to the ddnnsssseecc--ddnnsskkeeyy--kksskkoonnllyy yyeess;; zone option in nnaammeedd.)
-z Ignore KSK flag on key when determining what to sign. This causes KSK-flagged keys to sign all records, not just the DNSKEY RRset. (This is similar to the uuppddaattee--cchheecckk--kksskk nnoo;; zone option in nnaammeedd.)
-3 _s_a_l_t Generate an NSEC3 chain with the given hex encoded salt. A dash (_s_a_l_t) can be used to indicate that no salt is to be used when generating the NSEC3 chain.
-H _i_t_e_r_a_t_i_o_n_s When generating an NSEC3 chain, use this many interations. The default is 10.
-A
When generating an NSEC3 chain set the OPTOUT flag on all NSEC3 records and do not generate NSEC3 records for insecure delegations.
Using this option twice (i.e.,
--AAAA) turns the OPTOUT flag off for all records. This is useful when using the
--uu
option to modify an NSEC3 chain which previously had OPTOUT set.
zonefile The file containing the zone to be signed.
key Specify which keys should be used to sign the zone. If no keys are specified, then the zone will be examined for DNSKEY records at the zone apex. If these are found and there are matching private keys, in the current directory, then these will be used for signing.
The following command signs the
eexxaammppllee..ccoomm
zone with the DSA key generated by
ddnnsssseecc--kkeeyyggeenn
(Kexample.com.+003+17247). Because the
--SS
option is not being used, the zone's keys must be in the master file (_d_b_._e_x_a_m_p_l_e_._c_o_m). This invocation looks for
_d_s_s_e_t
files, in the current directory, so that DS records can be imported from them (--gg).
% dnssec-signzone -g -o example.com db.example.com \ Kexample.com.+003+17247 db.example.com.signed %
In the above example, ddnnsssseecc--ssiiggnnzzoonnee creates the file _d_b_._e_x_a_m_p_l_e_._c_o_m_._s_i_g_n_e_d. This file should be referenced in a zone statement in a _n_a_m_e_d_._c_o_n_f file.
This example re-signs a previously signed zone with default parameters. The private keys are assumed to be in the current directory.
% cp db.example.com.signed db.example.com % dnssec-signzone -o example.com db.example.com db.example.com.signed %
ddnnsssseecc--kkeeyyggeenn(8), BIND 9 Administrator Reference Manual, RFC 4033.
Internet Systems Consortium