diff --git a/bin/nsupdate/nsupdate.docbook b/bin/nsupdate/nsupdate.docbook index 4d1939585c..c8238da5c6 100644 --- a/bin/nsupdate/nsupdate.docbook +++ b/bin/nsupdate/nsupdate.docbook @@ -16,7 +16,7 @@ - WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. --> - + @@ -81,10 +81,10 @@ made and the replies received from the name server. Transaction signatures can be used to authenticate the Dynamic DNS updates. -These use the TSIG resource record type described in RFC2845. -The signatures rely on a shared secret that should only be known to -nsupdate -and the name server. +These use the TSIG resource record type described in RFC2845 or the +SIG(0) record described in RFC3535 and RFC2931. +TSIG relies on a shared secret that should only be known to +nsupdate and the name server. Currently, the only supported encryption algorithm for TSIG is HMAC-MD5, which is defined in RFC 2104. Once other algorithms are defined for TSIG, applications will need to @@ -99,6 +99,8 @@ statements would be added to so that the name server can associate the appropriate secret key and algorithm with the IP address of the client application that will be using TSIG authentication. +SIG(0) uses public key cryptography. To use a SIG(0) key, the public +key must be stored in a KEY record in a zone served by the name server. nsupdate does not read /etc/named.conf. @@ -109,8 +111,8 @@ uses the or -option to provide the shared secret needed to generate a TSIG record -for authenticating Dynamic DNS update requests. +option (with an HMAC-MD5 key) to provide the shared secret needed to generate +a TSIG record for authenticating Dynamic DNS update requests. These options are mutually exclusive. With the @@ -144,6 +146,11 @@ This may be visible in the output from or in a history file maintained by the user's shell. +The may also be used to specify a SIG(0) key used +to authenticate Dynamic DNS update requests. In this case, the key +specified is not an HMAC-MD5 key. + + By default nsupdate uses UDP to send update requests to the name server. @@ -537,6 +544,9 @@ base-64 encoding of HMAC-MD5 key created by RFC2535 , +RFC2931 +, + named8 , diff --git a/doc/arm/Bv9ARM-book.xml b/doc/arm/Bv9ARM-book.xml index cbf81b2218..b6c66e8586 100644 --- a/doc/arm/Bv9ARM-book.xml +++ b/doc/arm/Bv9ARM-book.xml @@ -2,7 +2,7 @@ - + BIND 9 Administrator Reference Manual @@ -2622,6 +2622,7 @@ statement in the named.conf file: version version_string; hostname hostname_string; directory path_name; + key-directory path_name; named-xfer path_name; tkey-domain domainname; tkey-dhkey key_name key_tag; @@ -2710,7 +2711,7 @@ statement in the named.conf file: -<command>options</command> Statement Definition and Usage +<command>options</command> Statement Definition and Usage The options statement sets up global options to be used by BIND. This statement may appear only @@ -2752,6 +2753,13 @@ to `.', the directory from which the server was started. The directory specified should be an absolute path. +key-directory +When performing dynamic update of secure zones, the +directory where the public and private key files should be found, +if different than the current working directory. The directory specified +must be an absolute path. + + named-xfer This option is obsolete. It was used in BIND 8 to @@ -4178,6 +4186,7 @@ Statement Grammar max-refresh-time number ; min-retry-time number ; max-retry-time number ; + key-directory path_name; }; @@ -4487,6 +4496,12 @@ See the description in . ixfr-from-differences in . +key-directory +See the description of +key-directory in + + +