From: Tinderbox User
- Remove signatures from keys that no longer exist. + Remove signatures from keys that are no longer active.
Normally, when a previously-signed zone is passed as input
@@ -301,9 +301,24 @@
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 -R forces
- dnssec-signzone to remove all orphaned
- signatures.
+ copies of the old DNSKEY RRset. The -Q
+ forces dnssec-signzone to remove
+ signatures from keys that are no longer active. This
+ enables ZSK rollover using the procedure described in
+ RFC 4641, section 4.2.1.1 ("Pre-Publish Key Rollover").
+
+ Remove signatures from keys that are no longer published. +
+
+ This option is similar to -Q, except it
+ forces dnssec-signzone to signatures from
+ keys that are no longer published. This enables ZSK rollover
+ using the procedure described in RFC 4641, section 4.2.1.2
+ ("Double Signature Zone Signing Key Rollover").
randomdev
The following command signs the example.com
zone with the DSA key generated by dnssec-keygen
@@ -478,14 +493,14 @@ db.example.com.signed
%
dnssec-keygen(8), BIND 9 Administrator Reference Manual, - RFC 4033. + RFC 4033, RFC 4641.
arpaname {ipaddress ...}
arpaname translates IP addresses (IPv4 and IPv6) to the corresponding IN-ADDR.ARPA or IP6.ARPA names.
ddns-confgen [-a ] [algorithm-h] [-k ] [keyname-r ] [ -s randomfilename | -z zone ] [-q] [name]
ddns-confgen generates a key for use by nsupdate and named. It simplifies configuration @@ -77,7 +77,7 @@
dnssec-signzone [-a] [-c ] [class-d ] [directory-D] [-E ] [engine-e ] [end-time-f ] [output-file-g] [-h] [-K ] [directory-k ] [key-L ] [serial-l ] [domain-i ] [interval-I ] [input-format-j ] [jitter-N ] [soa-serial-format-o ] [origin-O ] [output-format-P] [-p] [-R] [-r ] [randomdev-S] [-s ] [start-time-T ] [ttl-t] [-u] [-v ] [level-X ] [extended end-time-x] [-z] [-3 ] [salt-H ] [iterations-A] {zonefile} [key...]
dnssec-signzone signs a zone. It generates NSEC and RRSIG records and produces a signed version of the @@ -61,7 +61,7 @@
@@ -308,10 +308,10 @@ This option skips these tests.
- Remove signatures from keys that no longer exist. + Remove signatures from keys that are no longer active.
Normally, when a previously-signed zone is passed as input
@@ -319,9 +319,24 @@
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 -R forces
- dnssec-signzone to remove all orphaned
- signatures.
+ copies of the old DNSKEY RRset. The -Q
+ forces dnssec-signzone to remove
+ signatures from keys that are no longer active. This
+ enables ZSK rollover using the procedure described in
+ RFC 4641, section 4.2.1.1 ("Pre-Publish Key Rollover").
+
+ Remove signatures from keys that are no longer published. +
+
+ This option is similar to -Q, except it
+ forces dnssec-signzone to signatures from
+ keys that are no longer published. This enables ZSK rollover
+ using the procedure described in RFC 4641, section 4.2.1.2
+ ("Double Signature Zone Signing Key Rollover").
randomdev
The following command signs the example.com
zone with the DSA key generated by dnssec-keygen
@@ -496,14 +511,14 @@ db.example.com.signed
%
dnssec-keygen(8), BIND 9 Administrator Reference Manual, - RFC 4033. + RFC 4033, RFC 4641.
dnssec-verify [-c ] [class-E ] [engine-I ] [input-format-o ] [origin-v ] [level-x] [-z] {zonefile}
dnssec-verify verifies that a zone is fully signed for each algorithm found in the DNSKEY RRset for the zone, and that the NSEC / NSEC3 @@ -58,7 +58,7 @@
genrandom [-n ] {numbersize} {filename}
genrandom generates a file or a set of files containing a specified quantity @@ -59,7 +59,7 @@
isc-hmac-fixup {algorithm} {secret}
Versions of BIND 9 up to and including BIND 9.6 had a bug causing HMAC-SHA* TSIG keys which were longer than the digest length of the @@ -76,7 +76,7 @@
Secrets that have been converted by isc-hmac-fixup are shortened, but as this is how the HMAC protocol works in @@ -87,14 +87,14 @@
named-checkconf [-h] [-v] [-j] [-t ] {filename} [directory-p] [-z]
named-checkconf checks the syntax, but not the semantics, of a named configuration file. The file is parsed @@ -70,7 +70,7 @@
named-checkconf returns an exit status of 1 if errors were detected and 0 otherwise.
named-compilezone [-d] [-j] [-q] [-v] [-c ] [class-C ] [mode-f ] [format-F ] [format-J ] [filename-i ] [mode-k ] [mode-m ] [mode-n ] [mode-L ] [serial-r ] [mode-s ] [style-t ] [directory-T ] [mode-w ] [directory-D] [-W ] {mode-o } {zonename} {filename}filename
named-checkzone checks the syntax and integrity of a zone file. It performs the same checks as named does when loading a @@ -71,7 +71,7 @@
named-checkzone returns an exit status of 1 if errors were detected and 0 otherwise.
named-journalprint {journal}
named-journalprint prints the contents of a zone journal file in a human-readable @@ -76,7 +76,7 @@
named [-4] [-6] [-c ] [config-file-d ] [debug-level-D ] [string-E ] [engine-name-f] [-g] [-m ] [flag-n ] [#cpus-p ] [port-s] [-S ] [#max-socks-t ] [directory-U ] [#listeners-u ] [user-v] [-V] [-x ]cache-file
named is a Domain Name System (DNS) server, part of the BIND 9 distribution from ISC. For more @@ -65,7 +65,7 @@
In routine operation, signals should not be used to control the nameserver; rndc should be used @@ -284,7 +284,7 @@
The named configuration file is too complex to describe in detail here. A complete description is provided @@ -301,7 +301,7 @@
nsec3hash {salt} {algorithm} {iterations} {domain}
nsec3hash generates an NSEC3 hash based on a set of NSEC3 parameters. This can be used to check the validity @@ -56,7 +56,7 @@
nsupdate [-d] [-D] [[-g] | [-o] | [-l] | [-y ] | [[hmac:]keyname:secret-k ]] [keyfile-t ] [timeout-u ] [udptimeout-r ] [udpretries-R ] [randomdev-v] [-T] [-P] [filename]
nsupdate is used to submit Dynamic DNS Update requests as defined in RFC 2136 to a name server. @@ -226,7 +226,7 @@
The TSIG key is redundantly stored in two separate files. This is a consequence of nsupdate using the DST library diff --git a/doc/arm/man.rndc-confgen.html b/doc/arm/man.rndc-confgen.html index 31f639f3ed7..3b1e6ff88d1 100644 --- a/doc/arm/man.rndc-confgen.html +++ b/doc/arm/man.rndc-confgen.html @@ -50,7 +50,7 @@
rndc-confgen [-a] [-A ] [algorithm-b ] [keysize-c ] [keyfile-h] [-k ] [keyname-p ] [port-r ] [randomfile-s ] [address-t ] [chrootdir-u ]user
rndc-confgen generates configuration files for rndc. It can be used as a @@ -66,7 +66,7 @@
rndc.conf
rndc.conf is the configuration file
for rndc, the BIND 9 name server control
utility. This file has a similar structure and syntax to
@@ -136,7 +136,7 @@
The name server must be configured to accept rndc connections and
to recognize the key specified in the rndc.conf
@@ -220,7 +220,7 @@
rndc [-b ] [source-address-c ] [config-file-k ] [key-file-s ] [server-p ] [port-V] [-y ] {command}key_id
rndc controls the operation of a name server. It supersedes the ndc utility @@ -81,7 +81,7 @@
A list of commands supported by rndc can be seen by running rndc without arguments. @@ -523,7 +523,7 @@