1ldns-signzone(1) General Commands Manual ldns-signzone(1)
2
6 ldns-signzone - sign a zonefile with DNSSEC data
7
9 ldns-signzone [ OPTIONS ] ZONEFILE KEY [KEY [KEY] ... ]
10
13 ldns-signzone is used to generate a DNSSEC signed zone. When run it
14 will create a new zonefile that contains RRSIG and NSEC resource
15 records, as specified in RFC 4033, RFC 4034 and RFC 4035.
16 Keys must be specified by their base name (i.e. without .private). If
18 the DNSKEY that belongs to the key in the .private file is not present
19 in the zone, it will be read from the file <base name>.key. If that
20 file does not exist, the DNSKEY value will be generated from the pri‐
21 vate key.
22 Multiple keys can be specified, Key Signing Keys are used as such when
24 they are either already present in the zone, or specified in a .key
25 file, and have the KSK bit set.
26
29 -b Augments the zone and the RR's with extra comment texts for a
30 more readable layout, easier to debug. DS records will have a
31 bubblebabble version of the data in the comment text, NSEC3
32 records will have the unhashed owner names in the comment text.
33 Without this option, only DNSKEY RR's will have their Key Tag
35 annotated in the comment text.
36 -d Normally, if the DNSKEY RR for a key that is used to sign the
39 zone is not found in the zone file, it will be read from .key,
40 or derived from the private key (in that order). This option
41 turns that feature off, so that only the signatures are added to
42 the zone.
43 -e date
46 Set expiration date of the signatures to this date, the format
47 can be YYYYMMDD[hhmmss], or a timestamp.
48 -f file
51 Use this file to store the signed zone in (default <original‐
52 file>.signed)
53 -i date
56 Set inception date of the signatures to this date, the format
57 can be YYYYMMDD[hhmmss], or a timestamp.
58 -o origin
61 Use this as the origin of the zone
62 -u set SOA serial to the number of seconds since 1-1-1970
65 -v Print the version and exit
68 -z [scheme:]hash
71 Calculate the zone's digest and add those as ZONEMD RRs. The
72 (optional) `scheme' must be `simple` (or 1) and `hash' should be
73 `sha384' (or 1) or `sha512' (or 2). This option can be given
74 more than once.
75 -Z Allow ZONEMDs to be added without signing
78 -A Sign the DNSKEY record with all keys. By default it is signed
81 with a minimal number of keys, to keep the response size for the
82 DNSKEY query small, and only the SEP keys that are passed are
83 used. If there are no SEP keys, the DNSKEY RRset is signed with
84 the non-SEP keys. This option turns off the default and all
85 keys are used to sign the DNSKEY RRset.
86 -E name
89 Use the EVP cryptographic engine with the given name for sign‐
90 ing. This can have some extra options; see ENGINE OPTIONS for
91 more information.
92 -K algorithm-id,key-id
95 Use the key `key-id' as the signing key for algorithm `algo‐
97 rithm-id' as a Key Signing Key (KSK). This option is used when
98 you use an OpenSSL engine, see ENGINE OPTIONS for more informa‐
99 tion.
100 -k algorithm-id,key-id
103 Use the key `key-id' as the signing key for algorithm `algo‐
104 rithm-id' as a Zone Signing Key (ZSK). This option is used when
105 you use an OpenSSL engine, see ENGINE OPTIONS for more informa‐
106 tion.
107 -n Use NSEC3 instead of NSEC.
110 If you use NSEC3, you can specify the following extra options:
113 -a algorithm
116 Algorithm used to create the hashed NSEC3 owner names
117 -p Opt-out. All NSEC3 records in the zone will have the Opt-out
120 flag set. After signing, you can add insecure delegations to the
121 signed zone.
122 -s string
125 Salt
126 -t number
129 Number of hash iterations
130
133 You can modify the possible engines, if supported, by setting an
134 OpenSSL configuration file. This is done through the environment vari‐
135 able OPENSSL_CONF.
136 The key options (-k and -K) work as follows: you specify a DNSSEC algo‐
138 rithm (using its symbolic name, for instance, RSASHA256 or its numeric
139 identifier, for instance, 8), followed by a comma and a key identifier
140 (white space is not allowed between the algorithm and the comma and be‐
141 tween the comma and the key identifier).
142 The key identifier can be any of the following:
144 <id>
146 <slot>:<id>
147 id_<id>
148 slot_<slot>-id_<id>
149 label_<label>
150 slot_<slot>-label_<label>
151 Where '<id>' is the PKCS #11 key identifier in hexadecimal notation,
153 '<label>' is the PKCS #11 human-readable label, and '<slot>' is the
154 slot number where the token is present.
155 More recent versions of OpenSSL engines may support the PKCS #11 URI
157 scheme (RFC 7512), please consult your engine's documentation.
158 If not already present, a DNSKEY RR is generated from the key data, and
160 added to the zone.
161
164 ldns-signzone nlnetlabs.nl Knlnetlabs.nl.+005+12273
165 Sign the zone in the file 'nlnetlabs.nl' with the key in the
166 files 'Knlnetlabs.nl.+005+12273.private'. If the DNSKEY is not
167 present in the zone, use the key in the file 'Knlnet‐
168 labs.nl.+005+12273.key'. If that is not present, generate one
169 with default values from 'Knlnetlabs.nl.+005+12273.private'.
170
174 Written by the ldns team as an example for ldns usage.
175 Portions of engine support by Vadim Penzin <vadim@penzin.net>.
176
179 Report bugs to <ldns-team@nlnetlabs.nl>.
180
183 Copyright (C) 2005-2008 NLnet Labs. This is free software. There is NO
184 warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PUR‐
185 POSE.
186 13 March 2018 ldns-signzone(1)