1DNSSEC-SIGNZONE(8) BIND9 DNSSEC-SIGNZONE(8)
2
6 dnssec-signzone - DNSSEC zone signing tool
7
9 dnssec-signzone [-a] [-c class] [-d directory] [-e end-time]
10 [-f output-file] [-g] [-h] [-k key] [-l domain]
11 [-i interval] [-I input-format] [-j jitter]
12 [-N soa-serial-format] [-o origin] [-O output-format]
13 [-p] [-r randomdev] [-s start-time] [-t] [-v level]
14 [-z] {zonefile} [key...]
15
17 dnssec-signzone signs a zone. It generates NSEC and RRSIG records and
18 produces a signed version of the zone. The security status of
19 delegations from the signed zone (that is, whether the child zones are
20 secure or not) is determined by the presence or absence of a keyset
21 file for each child zone.
22
24 -a
25 Verify all generated signatures.
26 -c class
28 Specifies the DNS class of the zone.
29 -k key
31 Treat specified key as a key signing key ignoring any key flags.
32 This option may be specified multiple times.
33 -l domain
35 Generate a DLV set in addition to the key (DNSKEY) and DS sets. The
36 domain is appended to the name of the records.
37 -d directory
39 Look for keyset files in directory as the directory
40 -g
42 Generate DS records for child zones from keyset files. Existing DS
43 records will be removed.
44 -s start-time
46 Specify the date and time when the generated RRSIG records become
47 valid. This can be either an absolute or relative time. An absolute
48 start time is indicated by a number in YYYYMMDDHHMMSS notation;
49 20000530144500 denotes 14:45:00 UTC on May 30th, 2000. A relative
50 start time is indicated by +N, which is N seconds from the current
51 time. If no start-time is specified, the current time minus 1 hour
52 (to allow for clock skew) is used.
53 -e end-time
55 Specify the date and time when the generated RRSIG records expire.
56 As with start-time, an absolute time is indicated in YYYYMMDDHHMMSS
57 notation. A time relative to the start time is indicated with +N,
58 which is N seconds from the start time. A time relative to the
59 current time is indicated with now+N. If no end-time is specified,
60 30 days from the start time is used as a default.
61 -f output-file
63 The name of the output file containing the signed zone. The default
64 is to append .signed to the input filename.
65 -h
67 Prints a short summary of the options and arguments to
68 dnssec-signzone.
69 -i interval
71 When a previously-signed zone is passed as input, records may be
72 resigned. The interval option specifies the cycle interval as an
73 offset from the current time (in seconds). If a RRSIG record
74 expires after the cycle interval, it is retained. Otherwise, it is
75 considered to be expiring soon, and it will be replaced.
76 The default cycle interval is one quarter of the difference between
78 the signature end and start times. So if neither end-time or
79 start-time are specified, dnssec-signzone generates signatures that
80 are valid for 30 days, with a cycle interval of 7.5 days.
81 Therefore, if any existing RRSIG records are due to expire in less
82 than 7.5 days, they would be replaced.
83 -I input-format
85 The format of the input zone file. Possible formats are "text"
86 (default) and "raw". This option is primarily intended to be used
87 for dynamic signed zones so that the dumped zone file in a non-text
88 format containing updates can be signed directly. The use of this
89 option does not make much sense for non-dynamic zones.
90 -j jitter
92 When signing a zone with a fixed signature lifetime, all RRSIG
93 records issued at the time of signing expires simultaneously. If
94 the zone is incrementally signed, i.e. a previously-signed zone is
95 passed as input to the signer, all expired signatures have to be
96 regenerated at about the same time. The jitter option specifies a
97 jitter window that will be used to randomize the signature expire
98 time, thus spreading incremental signature regeneration over time.
99 Signature lifetime jitter also to some extent benefits validators
101 and servers by spreading out cache expiration, i.e. if large
102 numbers of RRSIGs don't expire at the same time from all caches
103 there will be less congestion than if all validators need to
104 refetch at mostly the same time.
105 -n ncpus
107 Specifies the number of threads to use. By default, one thread is
108 started for each detected CPU.
109 -N soa-serial-format
111 The SOA serial number format of the signed zone. Possible formats
112 are "keep" (default), "increment" and "unixtime".
113 "keep"
115 Do not modify the SOA serial number.
116 "increment"
118 Increment the SOA serial number using RFC 1982 arithmetics.
119 "unixtime"
121 Set the SOA serial number to the number of seconds since
122 epoch.
123 -o origin
125 The zone origin. If not specified, the name of the zone file is
126 assumed to be the origin.
127 -O output-format
129 The format of the output file containing the signed zone. Possible
130 formats are "text" (default) and "raw".
131 -p
133 Use pseudo-random data when signing the zone. This is faster, but
134 less secure, than using real random data. This option may be useful
135 when signing large zones or when the entropy source is limited.
136 -r randomdev
138 Specifies the source of randomness. If the operating system does
139 not provide a /dev/random or equivalent device, the default source
140 of randomness is keyboard input. randomdev specifies the name of a
141 character device or file containing random data to be used instead
142 of the default. The special value keyboard indicates that keyboard
143 input should be used.
144 -t
146 Print statistics at completion.
147 -v level
149 Sets the debugging level.
150 -z
152 Ignore KSK flag on key when determining what to sign.
153 zonefile
155 The file containing the zone to be signed.
156 key
158 Specify which keys should be used to sign the zone. If no keys are
159 specified, then the zone will be examined for DNSKEY records at the
160 zone apex. If these are found and there are matching private keys,
161 in the current directory, then these will be used for signing.
162
164 The following command signs the example.com zone with the DSA key
165 generated by dnssec-keygen (Kexample.com.+003+17247). The zone's keys
166 must be in the master file (db.example.com). This invocation looks for
167 keyset files, in the current directory, so that DS records can be
168 generated from them (-g).
169 % dnssec-signzone -g -o example.com db.example.com \
171 Kexample.com.+003+17247
172 db.example.com.signed
173 %
174 In the above example, dnssec-signzone creates the file
176 db.example.com.signed. This file should be referenced in a zone
177 statement in a named.conf file.
178 This example re-signs a previously signed zone with default parameters.
180 The private keys are assumed to be in the current directory.
181 % cp db.example.com.signed db.example.com
183 % dnssec-signzone -o example.com db.example.com
184 db.example.com.signed
185 %
186
188 dnssec-keygen(8), BIND 9 Administrator Reference Manual, RFC 2535.
189
191 Internet Systems Consortium
192
194 Copyright © 2004-2007 Internet Systems Consortium, Inc. ("ISC")
195 Copyright © 2000-2003 Internet Software Consortium.
196BIND9 June 30, 2000 DNSSEC-SIGNZONE(8)