DNSSEC-SIGNZONE(1)

📦
version 9.20.30 · 36 versions
, in alpine 3.22, alpine 3.23, alpine 3.24, nixos 26.05, nixpkgs unstable

💅 DNSSEC-SIGNZONE(1) 💅

okay bestie, this is the BIND 9 manual page for dnssec-signzone, and we’re covering it in two parts. This half is the intro plus the option list through -o origin ✨.

✨ NAME ✨

dnssec-signzone — DNSSEC zone signing tool. That’s the whole assignment: it signs your zone and produces a signed version. iconic behavior, honestly 💖.

🎀 SYNOPSIS 🎀

here’s the full flag parade, exactly as written:

dnssec-signzone [-a] [-c class] [-d directory] [-D] [-E engine] [-e
end-time] [-f output-file] [-F] [-g] [-G sync-records] [-h] [-i
interval] [-I input-format] [-j jitter] [-J filename] [-K directory] [-k
key] [-L serial] [-M maxttl] [-N soa-serial-format] [-o origin] [-O
output-format] [-P] [-Q] [-q] [-R] [-S] [-s start-time] [-T ttl] [-t]
[-u] [-v level] [-V] [-X extended end-time] [-x] [-z] [-3 salt] [-H
iterations] [-A] {zonefile} [key...]

🦋 DESCRIPTION 🦋

dnssec-signzone 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) is determined by the presence or absence of a keyset file for each child zone. no cap, that keyset file is basically the vibe check for child-zone security 💖.

🌈 OPTIONS 🌈

okay, flag by flag, let’s go 💅:

  • -a — this option verifies all generated signatures. all of them, bestie — no skipping.
  • -c class — this option specifies the DNS class of the zone.
  • -C — this option sets compatibility mode, in which a keyset-zonename file is generated in addition to dsset-zonename when signing a zone, for use by older versions of dnssec-signzone. legacy support said “hey” 💜
  • -d directory — this option indicates the directory where BIND 9 should look for dsset- or keyset- files.
  • -D — this option indicates that only those record types automatically managed by dnssec-signzone, i.e., RRSIG, NSEC, NSEC3 and NSEC3PARAM records, should be included in the output. If smart signing (-S) is used, DNSKEY records are also included. The resulting file can be included in the original zone file with $INCLUDE. This option cannot be combined with -O raw or serial-number updating. so do not try it, bestie 💀
  • -E engine — this option specifies the hardware to use for cryptographic operations, such as a secure key store used for signing, when applicable.

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).

  • -F — this option turns on FIPS (US Federal Information Processing Standards) mode if the underlying cryptographic library supports running in FIPS mode.
  • -g — this option indicates that DS records for child zones should be generated from a dsset- or keyset- file. Existing DS records are removed. clean slate energy ✨
  • -G sync-records — this option indicates which CDS and CDNSKEY records should be generated. sync-records is a comma-separated string with the following allowed items: cdnskey, and cds:<digest-type>, where digest-type is an allowed algorithm such as SHA-256 (2), or SHA-384 (4). Only works in combination with smart signing (-S). iykyk 🔥
  • -J filename — this option tells dnssec-signzone to read the journal from the given file when loading the zone file.
  • -K directory — this option specifies the directory to search for DNSSEC keys. If not specified, it defaults to the current directory.
  • -k key — this option tells BIND 9 to treat the specified key as a key-signing key, ignoring any key flags. This option may be specified multiple times. stack ’em if you got ’em 🫶
  • -M maxttl — this option sets the maximum TTL for the signed zone. Any TTL higher than maxttl in the input zone is reduced to maxttl in the output. This provides certainty as to the largest possible TTL in the signed zone, which is useful to know when rolling keys. The maxttl is the longest possible time before signatures that have been retrieved by resolvers expire from resolver caches. Zones that are signed with this option should be configured to use a matching max-zone-ttl in named.conf. (Note: this option is incompatible with -D, because it modifies non-DNSSEC data in the output zone.) periodt 💅
  • -s start-time — this option specifies 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 1 hour (to allow for clock skew) is used. clock skew said “not today” ⏰
  • -e end-time — this option specifies 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 the default. end-time must be later than start-time. no time-travel nonsense, bestie 🍑
  • -X extended end-time — this option specifies the date and time when the generated RRSIG records for the DNSKEY RRset expire. This is to be used in cases when the DNSKEY signatures need to persist longer than signatures on other records; e.g., when the private component of the KSK is kept offline and the KSK signature is to be refreshed manually.

As with end-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 extended end-time is specified, the value of end-time is used as the default. (end-time, in turn, defaults to 30 days from the start time.) extended end-time must be later than start-time. offline KSK main character energy 👑

  • -f output-file — this option indicates the name of the output file containing the signed zone. The default is to append .signed to the input filename. If output-file is set to -, then the signed zone is written to the standard output, with a default output format of full. stdout slay 🌈
  • -h — this option prints a short summary of the options and arguments to dnssec-signzone.
  • -V — this option prints version information.
  • -i interval — this option indicates that, when a previously signed zone is passed as input, records may be re-signed. The interval 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 is replaced.

The default cycle interval is one quarter of the difference between the signature end and start times. So if neither end-time nor start-time is specified, dnssec-signzone 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 are replaced.

Note that the calculation of cycle interval is based upon the validity period of the replacement signatures that would be generated by dnssec-signzone, not on the valid lifetimes of the input RRSIGs being considered for pre-expiry replacement. math but make it DNSSEC 🧮

  • -I input-format — this option sets the format of the input zone file. Possible formats are text (the default), and raw. 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. This option is not useful for non-dynamic zones.
  • -j jitter — when signing a zone with a fixed signature lifetime, all RRSIG records issued at the time of signing expire simultaneously. If the zone is incrementally signed, i.e., a previously signed zone is passed as input to the signer, all expired signatures must be regenerated at approximately the same time. The jitter option specifies a jitter window that is 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 do not expire at the same time from all caches, there is less congestion than if all validators need to refetch at around the same time. spread the chaos, reduce the traffic 💖

  • -L serial — when writing a signed zone to raw format, this option sets the source serial value in the header to the specified serial number. (This is expected to be used primarily for testing purposes.)
  • -n ncpus — this option specifies the number of threads to use. By default, one thread is started for each detected CPU.
  • -N soa-serial-format — this option sets the SOA serial number format of the signed zone. Possible formats are keep (the default), increment, unixtime, and date.
    • keep — this format indicates that the SOA serial number should not be modified.
    • increment — this format increments the SOA serial number using RFC 1982 arithmetic.
    • unixtime — this format sets the SOA serial number to the number of seconds since the beginning of the Unix epoch, unless the serial number is already greater than or equal to that value, in which case it is simply incremented by one.
    • date — this format sets the SOA serial number to today’s date, in YYYYMMDDNN format, unless the serial number is already greater than or equal to that value, in which case it is simply incremented by one.
  • -o origin — this option sets the zone origin. If not specified, the name of the zone file is assumed to be the origin. default behavior said “I got you” 🫶
  • -O output-format — okay bestie, this one sets the format of the output file that contains the signed zone. The possible formats are text (the default), which is the standard textual representation of the zone; full, which is text output in a format suitable for processing by external scripts; and raw and raw=N, which store the zone in binary formats for rapid loading by named. raw=N specifies the format version of the raw zone file: if N is 0, the raw file can be read by any version of named; if N is 1, the file can be read by release 9.9.0 or higher. The default is 1. 💅
  • -P — this option disables post-sign verification tests. The post-sign verification tests ensure 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. 🫶
  • -Q — this option removes signatures from keys that are no longer active. Normally, when a previously signed zone is passed as input to the signer, and a DNSKEY record has been removed and replaced with a new one, signatures from the old key that are still within their validity period are retained. This allows the zone to continue to validate with cached copies of the old DNSKEY RRset. The -Q option forces dnssec-signzone to remove signatures from keys that are no longer active. This enables ZSK rollover using the procedure described in RFC 6781 Section 4.1.1.1 (https://datatracker.ietf.org/doc/html/rfc6781.html#section-4.1.1.1) ("Pre-Publish Zone Signing Key Rollover"). ✨
  • -q — this option enables quiet mode, which suppresses unnecessary output. Without this option, when dnssec-signzone is run it prints three pieces of information to standard output:
    1. the number of keys in use;
    2. the algorithms used to verify the zone was signed correctly and other status information;
    3. the filename containing the signed zone. With the option, that output is suppressed, leaving only the filename. 🤫
  • -R — this option removes signatures from keys that are no longer published. This option is similar to -Q, except it forces dnssec-signzone to remove signatures from keys that are no longer published. This enables ZSK rollover using the procedure described in RFC 6781 Section 4.1.1.2 (https://datatracker.ietf.org/doc/html/rfc6781.html#section-4.1.1.2) ("Double Signature Zone Signing Key Rollover"). 💀
  • -S — this option enables smart signing, which instructs dnssec-signzone 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:
    1. If no timing metadata has been set for the key, the key is published in the zone and used to sign the zone.
    2. If the key's publication date is set and is in the past, the key is published in the zone.
    3. If the key's activation date is set and is in the past, the key is published (regardless of publication date) and used to sign the zone.
    4. If the key's revocation date is set and is in the past, and the key is published, then the key is revoked, and the revoked key is used to sign the zone.
    5. If either the key's unpublication or deletion date is set and in the past, the key is NOT published or used to sign the zone, regardless of any other metadata.
    6. If the key's sync publication date is set and is in the past, synchronization records (type CDS and/or CDNSKEY) are created.
    7. If the key's sync deletion date is set and is in the past, synchronization records (type CDS and/or CDNSKEY) are removed.
  • -T ttl — this option specifies a TTL to be used for new DNSKEY records imported into the zone from the key repository. If not specified, the default is the TTL value from the zone's SOA record. This option is ignored when signing without -S, 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 are set to match them, or if any of the imported DNSKEY records had a default TTL value. In the event of a conflict between TTL values in imported keys, the shortest one is used. 🎀
  • -t — this option prints statistics at completion. ⭐
  • -u — this option updates the 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 switched to NSEC or to NSEC3 with different parameters. Without this option, dnssec-signzone retains the existing chain when re-signing. 🦋
  • -v level — this option sets the debugging level. 🔍
  • -x — this option indicates that BIND 9 should only sign the DNSKEY, CDNSKEY, and CDS RRsets with key-signing keys, and should omit signatures from zone-signing keys. 👑
  • -z — this option indicates that BIND 9 should ignore the KSK flag on keys when determining what to sign. This causes KSK-flagged keys to sign all records, not just the DNSKEY RRset. 🌀
  • -3 salt — this option generates an NSEC3 chain with the given hex-encoded salt. A dash (-) can be used to indicate that no salt is to be used when generating the NSEC3 chain.
Note: -3 - is the recommended configuration. Adding salt provides no practical benefits. See RFC 9276 (https://datatracker.ietf.org/doc/html/rfc9276.html). 🌸
  • -H iterations — this option indicates that, when generating an NSEC3 chain, BIND 9 should use this many iterations. The default is 0.
Warning: Values greater than 0 cause interoperability issues and also increase the risk of CPU-exhausting DoS attacks. See RFC 9276 (https://datatracker.ietf.org/doc/html/rfc9276.html). 😭
  • -A — this option indicates that, when generating an NSEC3 chain, BIND 9 should set the OPTOUT flag on all NSEC3 records and should not generate NSEC3 records for insecure delegations.
Warning: Do not use this option unless all its implications are fully understood. This option is intended only for extremely large zones (comparable to com.) with sparse secure delegations. See RFC 9276 (https://datatracker.ietf.org/doc/html/rfc9276.html). 🔥
  • -AA — this option turns the OPTOUT flag off for all records. This is useful when using the -u option to modify an NSEC3 chain which previously had OPTOUT set. 🌈
  • zonefile — this option sets the file containing the zone to be signed. 📁
  • key — this option specifies which keys should be used to sign the zone. If no keys are specified, the zone is examined for DNSKEY records at the zone apex. If these records are found and there are matching private keys in the current directory, they are used for signing. 🔑

✨ EXAMPLE ✨

The following command signs the example.com zone with the ECDSAP256SHA256 key generated by dnssec-keygen (Kexample.com.+013+17247). Because the -S option is not being used, the zone's keys must be in the master file (db.example.com). This invocation looks for dsset files in the current directory, so that DS records can be imported from them (-g).

% dnssec-signzone -g -o example.com db.example.com \
Kexample.com.+013+17247
db.example.com.signed
%

In the above example, dnssec-signzone creates the file db.example.com.signed. This file should be referenced in a zone statement in the named.conf 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
%

👀 SEE ALSO 👀

💖 Author 💖

Internet Systems Consortium

2026, Internet Systems Consortium

This page is serving BIND 9.20.30, dated 2026-10-12 — periodt. 💅✨

📦 where this page comes from