. . .nr rst2man-indent-level 0 . \\$1 \\n[an-margin] level \\n[rst2man-indent-level] level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] - \\n[rst2man-indent0] \\n[rst2man-indent1] \\n[rst2man-indent2] .. .rstReportMargin pre:
. RS \\$1 . nr rst2man-indent\\n[rst2man-indent-level] \\n[an-margin] . nr rst2man-indent-level +1 .rstReportMargin post:
.. . RE indent \\n[an-margin]
old: \\n[rst2man-indent\\n[rst2man-indent-level]]
.nr rst2man-indent-level -1 new: \\n[rst2man-indent\\n[rst2man-indent-level]]
..
-a algorithm This option selects the cryptographic algorithm. The value of algorithm must be one of RSASHA1, NSEC3RSASHA1, RSASHA256, RSASHA512, ECDSAP256SHA256, ECDSAP384SHA384, ED25519, or ED448. These values are case-insensitive. In some cases, abbreviations are supported, such as ECDSA256 for ECDSAP256SHA256 and ECDSA384 for ECDSAP384SHA384. If RSASHA1 is specified along with the \%-3 option, then NSEC3RSASHA1 is used instead. This option is mandatory except when using the \%-S option, which copies the algorithm from the predecessory key. Changed in version 9.12.0: The default value RSASHA1 for newly generated keys was removed. NINDENT NDENT 0.0
-3 This option uses an NSEC3-capable algorithm to generate a DNSSEC key. If this option is used with an algorithm that has both NSEC and NSEC3 versions, then the NSEC3 version is used; for example, dnssec-keygen -3a RSASHA1 specifies the NSEC3RSASHA1 algorithm. NINDENT NDENT 0.0
-E engine This option specifies the cryptographic hardware to use. When BIND 9 is built with OpenSSL, this needs to be set to the OpenSSL engine identifier that drives the cryptographic accelerator or hardware service module (usually pkcs11). NINDENT NDENT 0.0
-l label This option specifies the label for a key pair in the crypto hardware. When BIND 9 is built with OpenSSL-based PKCS#11 support, the label is an arbitrary string that identifies a particular key. It may be preceded by an optional OpenSSL engine name, followed by a colon, as in pkcs11:keylabel. NINDENT NDENT 0.0
-n nametype This option specifies the owner type of the key. The value of nametype must either be ZONE (for a DNSSEC zone key (KEY/DNSKEY)), HOST or ENTITY (for a key associated with a host (KEY)), USER (for a key associated with a user (KEY)), or OTHER (DNSKEY). These values are case-insensitive. NINDENT NDENT 0.0
-C This option enables compatibility mode, which generates an old-style key, without any metadata. By default, dnssec-keyfromlabel includes the key\(aqs creation date in the metadata stored with the private key; other dates may be set there as well, including publication date, activation date, etc. Keys that include this data may be incompatible with older versions of BIND; the \%-C option suppresses them. NINDENT NDENT 0.0
-c class This option indicates that the DNS record containing the key should have the specified class. If not specified, class IN is used. NINDENT NDENT 0.0
-f flag This option sets the specified flag in the flag field of the KEY/DNSKEY record. The only recognized flags are KSK (Key-Signing Key) and REVOKE. NINDENT NDENT 0.0
-G This option generates a key, but does not publish it or sign with it. This option is incompatible with \%-P and \%-A. NINDENT NDENT 0.0
-h This option prints a short summary of the options and arguments to dnssec-keyfromlabel. NINDENT NDENT 0.0
-K directory This option sets the directory in which the key files are to be written. NINDENT NDENT 0.0
-k This option generates KEY records rather than DNSKEY records. NINDENT NDENT 0.0
-L ttl This option sets the default TTL to use for this key when it is converted into a DNSKEY RR. This is the TTL used when the key is imported into a zone, unless there was already a DNSKEY RRset in place, in which case the existing TTL would take precedence. Setting the default TTL to 0 or none removes it. NINDENT NDENT 0.0
-p protocol This option sets the protocol value for the key. The protocol is a number between 0 and 255. The default is 3 (DNSSEC). Other possible values for this argument are listed in \%RFC 2535 and its successors. NINDENT NDENT 0.0
-S key This option generates a key as an explicit successor to an existing key. The name, algorithm, size, and type of the key are set to match the predecessor. The activation date of the new key is set to the inactivation date of the existing one. The publication date is set to the activation date minus the prepublication interval, which defaults to 30 days. NINDENT NDENT 0.0
-t type This option indicates the type of the key. type must be one of AUTHCONF, NOAUTHCONF, NOAUTH, or NOCONF. The default is AUTHCONF. AUTH refers to the ability to authenticate data, and CONF to the ability to encrypt data. NINDENT NDENT 0.0
-v level This option sets the debugging level. NINDENT NDENT 0.0
-V This option prints version information. NINDENT NDENT 0.0
-y This option allows DNSSEC key files to be generated even if the key ID would collide with that of an existing key, in the event of either key being revoked. (This is only safe to enable if \%RFC 5011 trust anchor maintenance is not used with either of the keys involved.) NINDENT
-P date/offset This option sets the date on which a key is to be published to the zone. After that date, the key is included in the zone but is not used to sign it. If not set, and if the \%-G option has not been used, the default is the current date. NDENT 7.0
sync date/offset This option sets the date on which CDS and CDNSKEY records that match this key are to be published to the zone. NINDENT NINDENT NDENT 0.0
-A date/offset This option sets the date on which the key is to be activated. After that date, the key is included in the zone and used to sign it. If not set, and if the \%-G option has not been used, the default is the current date. NINDENT NDENT 0.0
-R date/offset This option sets the date on which the key is to be revoked. After that date, the key is flagged as revoked. It is included in the zone and is used to sign it. NINDENT NDENT 0.0
-I date/offset This option sets the date on which the key is to be retired. After that date, the key is still included in the zone, but it is not used to sign it. NINDENT NDENT 0.0
-D date/offset This option sets the date on which the key is to be deleted. After that date, the key is no longer included in the zone. (However, it may remain in the key repository.) NDENT 7.0
sync date/offset This option sets the date on which the CDS and CDNSKEY records that match this key are to be deleted. NINDENT NINDENT NDENT 0.0
-i interval This option sets the prepublication interval for a key. If set, then the publication and activation dates must be separated by at least this much time. If the activation date is specified but the publication date is not, the publication date defaults to this much time before the activation date; conversely, if the publication date is specified but not the activation date, activation is set to this much time after publication. If the key is being created as an explicit successor to another key, then the default prepublication interval is 30 days; otherwise it is zero. As with date offsets, if the argument is followed by one of the suffixes y, mo, w, d, h, or mi, the interval is measured in years, months, weeks, days, hours, or minutes, respectively. Without a suffix, the interval is measured in seconds. NINDENT
.