diff --git a/bin/dnssec/dnssec-keygen.8 b/bin/dnssec/dnssec-keygen.8 index 4882e78ca89112e3ae11592d0922903df4da9014..6e45f309345687237bf09639b5b8f9e9b0f00ea3 100644 --- a/bin/dnssec/dnssec-keygen.8 +++ b/bin/dnssec/dnssec-keygen.8 @@ -13,7 +13,7 @@ .\" OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR .\" PERFORMANCE OF THIS SOFTWARE. .\" -.\" $Id: dnssec-keygen.8,v 1.45 2009/07/19 04:27:55 tbox Exp $ +.\" $Id: dnssec-keygen.8,v 1.46 2009/08/29 01:14:37 tbox Exp $ .\" .hy 0 .ad l @@ -38,6 +38,10 @@ dnssec\-keygen \- DNSSEC key generation tool .PP \fBdnssec\-keygen\fR generates keys for DNSSEC (Secure DNS), as defined in RFC 2535 and RFC 4034. It can also generate keys for use with TSIG (Transaction Signatures) as defined in RFC 2845, or TKEY (Transaction Key) as defined in RFC 2930. +.PP +The +\fBname\fR +of the key is specified on the command line. For DNSSEC keys, this must match the name of the zone for which the key is being generated. .SH "OPTIONS" .PP \-a \fIalgorithm\fR diff --git a/bin/dnssec/dnssec-keygen.html b/bin/dnssec/dnssec-keygen.html index 8aa2981ffabcf48dd4a5f4db984699829a4bf903..bb37e443b7e9662232119beb2d2afe8107ecc5a8 100644 --- a/bin/dnssec/dnssec-keygen.html +++ b/bin/dnssec/dnssec-keygen.html @@ -14,7 +14,7 @@ - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR - PERFORMANCE OF THIS SOFTWARE. --> - +
@@ -39,9 +39,14 @@ TSIG (Transaction Signatures) as defined in RFC 2845, or TKEY (Transaction Key) as defined in RFC 2930. +
+ The name
of the key is specified on the command
+ line. For DNSSEC keys, this must match the name of the zone for
+ which the key is being generated.
+
Dates can be expressed in the format YYYYMMDD or YYYYMMDDHHMMSS. If the argument begins with a '+' or '-', it is interpreted as @@ -248,7 +253,7 @@
To generate a 768-bit DSA key for the domain
example.com
, the following command would be
@@ -315,7 +320,7 @@
dnssec-signzone(8), BIND 9 Administrator Reference Manual, RFC 2539, @@ -324,7 +329,7 @@
ddns-confgen
[-a
] [algorithm
-h
] [-k
] [keyname
-r
] [randomfile
-s name | -z zone
] [-q
] [name]
ddns-confgen generates a key for use by nsupdate and named. It simplifies configuration @@ -75,7 +75,7 @@
dnssec-keygen
[-a
] [algorithm
-b
] [keysize
-n
] [nametype
-3
] [-A
] [date/offset
-C
] [-c
] [class
-D
] [date/offset
-e
] [-f
] [flag
-g
] [generator
-h
] [-K
] [directory
-k
] [-P
] [date/offset
-p
] [protocol
-R
] [date/offset
-r
] [randomdev
-s
] [strength
-t
] [type
-U
] [date/offset
-v
] [level
-z
] {name}
dnssec-keygen generates keys for DNSSEC (Secure DNS), as defined in RFC 2535 and RFC 4034. It can also generate keys for use with TSIG (Transaction Signatures) as defined in RFC 2845, or TKEY (Transaction Key) as defined in RFC 2930.
+
+ The name
of the key is specified on the command
+ line. For DNSSEC keys, this must match the name of the zone for
+ which the key is being generated.
+
Dates can be expressed in the format YYYYMMDD or YYYYMMDDHHMMSS. If the argument begins with a '+' or '-', it is interpreted as @@ -266,7 +271,7 @@
To generate a 768-bit DSA key for the domain
example.com
, the following command would be
@@ -333,7 +338,7 @@
dnssec-signzone(8), BIND 9 Administrator Reference Manual, RFC 2539, @@ -342,7 +347,7 @@
dnssec-revoke
[-hr
] [-v
] [level
-K
] [directory
-f
] {keyfile}
dnssec-revoke reads a DNSSEC key file, sets the REVOKED bit on the key as defined in RFC 5011, and creates a new pair of key files containing the @@ -58,7 +58,7 @@
dnssec-settime
[-fr
] [-K
] [directory
-P
] [date/offset
-A
] [date/offset
-R
] [date/offset
-U
] [date/offset
-D
] [date/offset
-h
] [-v
] {keyfile}level
dnssec-settime
reads a DNSSEC private key file and sets the key timing metadata
as specified by the -P
, -A
,
@@ -75,7 +75,7 @@
Dates can be expressed in the format YYYYMMDD or YYYYMMDDHHMMSS. If the argument begins with a '+' or '-', it is interpreted as @@ -146,7 +146,7 @@
dnssec-keygen(8), dnssec-signzone(8), BIND 9 Administrator Reference Manual, @@ -154,7 +154,7 @@
dnssec-signzone
[-a
] [-c
] [class
-d
] [directory
-e
] [end-time
-f
] [output-file
-g
] [-h
] [-K
] [directory
-k
] [key
-l
] [domain
-i
] [interval
-I
] [input-format
-j
] [jitter
-N
] [soa-serial-format
-o
] [origin
-O
] [output-format
-p
] [-P
] [-r
] [randomdev
-S
] [-s
] [start-time
-T
] [ttl
-t
] [-v
] [level
-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 @@
The following command signs the example.com
zone with the DSA key generated by dnssec-keygen
@@ -373,14 +373,14 @@ db.example.com.signed
%
named-checkconf
[-h
] [-v
] [-j
] [-t
] {filename} [directory
-p
] [-z
]
named-checkconf checks the syntax, but not the semantics, of a named configuration file.
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
-i
] [mode
-k
] [mode
-m
] [mode
-n
] [mode
-o
] [filename
-s
] [style
-t
] [directory
-w
] [directory
-D
] [-W
] {zonename} {filename}mode
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
[-4
] [-6
] [-c
] [config-file
-d
] [debug-level
-f
] [-g
] [-m
] [flag
-n
] [#cpus
-p
] [port
-s
] [-S
] [#max-socks
-t
] [directory
-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 @@ -259,7 +259,7 @@
The named configuration file is too complex to describe in detail here. A complete description is provided @@ -276,7 +276,7 @@
nsupdate
[-d
] [-D
] [[-g
] | [-o
] | [-l
] | [-y
] | [[hmac:]keyname:secret
-k
]] [keyfile
-t
] [timeout
-u
] [udptimeout
-r
] [udpretries
-R
] [randomdev
-v
] [filename]
nsupdate is used to submit Dynamic DNS Update requests as defined in RFC2136 to a name server. @@ -205,7 +205,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 fc97debf54d6ab943802cefca66aca6ff26764a4..764ba4c6a89c12828aaf76ad8131b66d9dd1d315 100644 --- a/doc/arm/man.rndc-confgen.html +++ b/doc/arm/man.rndc-confgen.html @@ -14,7 +14,7 @@ - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR - PERFORMANCE OF THIS SOFTWARE. --> - +
@@ -50,7 +50,7 @@rndc-confgen
[-a
] [-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
@@ -135,7 +135,7 @@
The name server must be configured to accept rndc connections and
to recognize the key specified in the rndc.conf
@@ -219,7 +219,7 @@
rndc
[-b
] [source-address
-c
] [config-file
-k
] [key-file
-s
] [server
-p
] [port
-V
] [-y
] {command}key_id