diff --git a/doc/arm/Bv9ARM-book.xml b/doc/arm/Bv9ARM-book.xml index 92f76f74db..d21f7b68a6 100644 --- a/doc/arm/Bv9ARM-book.xml +++ b/doc/arm/Bv9ARM-book.xml @@ -2,7 +2,7 @@ - + BIND 9 Administrator Reference Manual @@ -825,33 +825,42 @@ of a server. be shared. The order of statements is not significant. -The options statement has two clauses: default-server and default-key. default-server takes a +The options statement has three clauses: +default-server, default-key, +and default-port. +default-server takes a host name or address argument and represents the server that will be contacted if no -option is provided on the command line. default-key takes +option is provided on the command line. +default-key takes the name of key as its argument, as defined by a key statement. - In the future a default-port clause will be -added to specify the port to which rndc should -connect. +default-port specifies the port to which +rndc should connect if no +port is given on the command line or in a +server statement. + The key statement names a key with its string argument. The string is required by the server to be a valid domain name, though it need not actually be hierarchical; thus, a string like "rndc_key" is a valid name. -The key statement has two clauses: algorithm and secret. - While the configuration parser will accept any string as the argument +The key statement has two clauses: +algorithm and secret. +While the configuration parser will accept any string as the argument to algorithm, currently only the string "hmac-md5" has any meaning. The secret is a base-64 encoded string, typically generated with either dnssec-keygen or mmencode. + The server statement uses the key clause to associate a key-defined key with a server. - The argument to the server statement is a +The argument to the server statement is a host name or address (addresses must be double quoted). The argument to the key clause is the name of the key as defined by the key statement. - A port clause will be added to a future release -to specify the port to which rndc should connect +The port clause can be used to +specify the port to which rndc should connect on the given server. + A sample minimal configuration file is as follows: - + key rndc_key { algorithm "hmac-md5"; secret "c3Ryb25nIGVub3VnaCBmb3IgYSBtYW4gYnV0IG1hZGUgZm9yIGEgd29tYW4K"; @@ -861,6 +870,7 @@ options { default-key rndc_key; }; + This file, if installed as /etc/rndc.conf, would allow the command: $ rndc reload diff --git a/doc/arm/Bv9ARM.ch03.html b/doc/arm/Bv9ARM.ch03.html index ec4c938f9c..85d9b08a84 100644 --- a/doc/arm/Bv9ARM.ch03.html +++ b/doc/arm/Bv9ARM.ch03.html @@ -1184,13 +1184,19 @@ CLASS="command" >The options statement has two clauses: statement has three clauses: +default-server and , default-key. , +and default-port. +default-server takes a @@ -1199,7 +1205,8 @@ be contacted if no -s -option is provided on the command line. default-key takes @@ -1207,15 +1214,19 @@ the name of key as its argument, as defined by a key statement. - In the future a default-port clause will be -added to specify the port to which specifies the port to which +rndc should -connect.

should connect if no +port is given on the command line or in a +server statement.

The key statement has two clauses: statement has two clauses: +algorithm and secret. - While the configuration parser will accept any string as the argument +While the configuration parser will accept any string as the argument to algorithm, currently only the string "key-defined key with a server. - The argument to the server statement is a @@ -1272,11 +1284,11 @@ to the key clause is the name of the key as defined by the key statement. - A port clause will be added to a future release -to specify the port to which clause can be used to +specify the port to which rndc should connect @@ -1336,7 +1348,7 @@ CLASS="sect2" >

3.4.2. Signals

4.3. Split DNS
4.5. TKEY
4.6. SIG(0)
4.8. IPv6 Support in BIND

4.3. Split DNS

4.4.1. Generate Shared Keys for Each Pair of Hosts

4.4.1.1. Automatic Generation

4.4.1.2. Manual Generation

4.4.2. Copying the Shared Secret to Both Machines

4.4.3. Informing the Servers of the Key's Existence

4.4.4. Instructing the Server to Use the Key

4.4.5. TSIG Key Based Access Control

4.4.6. Errors

4.5. TKEY

4.6. SIG(0)

4.7.1. Generating Keys

4.7.2. Creating a Keyset

4.7.3. Signing the Child's Keyset

4.7.4. Signing the Zone

4.7.5. Configuring Servers

4.8. IPv6 Support in BIND

4.8.1. Address Lookups Using AAAA Records

4.8.2. Address Lookups Using A6 Records

4.8.2.1. A6 Chains

4.8.2.2. A6 Records for DNS Servers

4.8.3. Address to Name Lookups Using Nibble Format

4.8.4. Address to Name Lookups Using Bitstring Format

4.8.5. Using DNAME for Delegation of IPv6 Reverse Addresses

5.1. The Lightweight Resolver Library

5.1. The Lightweight Resolver Library

6.3. Zone File

6.1.1.1. Syntax

6.1.1.2. Definition and Usage
6.1.2. Comment Syntax
6.1.2.1. Syntax
6.1.2.2. Definition and Usage
6.2.1. acl
6.2.3. controls
6.2.5. include
6.2.6. include
6.2.7. key
6.2.8. key
6.2.9. logging
6.2.10. logging
6.2.10.1. The channel
6.2.11. lwres
6.2.12. lwres
6.2.13. options
6.2.14. options
6.2.14.2. Forwarding
6.2.14.4. Interfaces
6.2.14.5. Query Address
6.2.14.7. Operating System Resource Limits
6.2.14.8. Server  Resource Limits
6.2.14.9. Periodic Task Intervals
6.2.17. trusted-keys
6.2.18. trusted-keys
6.2.19. view
6.2.20. view
6.2.22. zone
6.2.22.1. Zone Types
6.2.22.2. Class
6.2.22.3. Zone Options
6.3. Zone File
6.3.1.1. Resource Records
6.3.1.2. Textual expression of RRs
6.3.2. Discussion of MX Records
6.3.4. Inverse Mapping in IPv4
6.3.5. Other Zone File Directives
6.3.5.1. The $ORIGIN
6.3.5.2. The $INCLUDE
6.3.5.3. The $TTL
6.3.6. BIND
7.2. chroot
7.2. chroot
7.2.1. The chroot
7.2.2. Using the setuid
8.1. Common Problems
8.2. Incrementing and Changing the Serial Number
8.3. Where Can I Get Help?
8.1. Common Problems
8.1.1. It's not working; how can I figure out what's wrong?
8.2. Incrementing and Changing the Serial Number
8.3. Where Can I Get Help?
A.1. Acknowledgements
A.3. General DNS
A.1. Acknowledgements
A.1.1. A Brief History of the DNS
A.2.1.1. HS = hesiod
A.2.1.2. CH = chaos
A.3. General DNS
Bibliography
Standards
[RFC974] 
[RFC1034] 
[RFC1035] 
[RFC2181] 
[RFC2308] 
[RFC1995] 
[RFC1996] 
[RFC2136] 
[RFC2845] 
Proposed Standards Still Under Development
[RFC1886] 
[RFC2065] 
[RFC2137] 
Other Important RFCs About DNS
[RFC1535] 
[RFC1536] 
[RFC1982] 
Resource Record Types
[RFC1183] 
[RFC1706] 
[RFC2168] 
[RFC1876] 
[RFC2052] 
[RFC2163] 
[RFC2230] 
DNS
[RFC1101] 
[RFC1123] 
[RFC1591] 
[RFC2317] 
DNS
[RFC1537] 
[RFC1912] 
[RFC1912] 
[RFC2010] 
[RFC2219] 
Other DNS
[RFC1464] 
[RFC1713] 
[RFC1794] 
[RFC2240] 
[RFC2345] 
[RFC2352] 
Obsolete and Unimplemented Experimental RRs
[RFC1712] 
A.4.3. Other Documents About BIND
Bibliography
3.4.2. Signals
4.3. Split DNS
4.4.1. Generate Shared Keys for Each Pair of Hosts
4.4.2. Copying the Shared Secret to Both Machines
4.4.3. Informing the Servers of the Key's Existence
4.4.4. Instructing the Server to Use the Key
4.4.5. TSIG Key Based Access Control
4.4.6. Errors
4.5. TKEY
4.6. SIG(0)
4.7.1. Generating Keys
4.7.2. Creating a Keyset
4.7.3. Signing the Child's Keyset
4.7.4. Signing the Zone
4.7.5. Configuring Servers
4.8. IPv6 Support in BIND
4.8.1. Address Lookups Using AAAA Records
4.8.2. Address Lookups Using A6 Records
4.8.3. Address to Name Lookups Using Nibble Format
4.8.4. Address to Name Lookups Using Bitstring Format
4.8.5. Using DNAME for Delegation of IPv6 Reverse Addresses
5.1. The Lightweight Resolver Library
6.1.2. Comment Syntax
6.2.1. acl
6.2.3. controls
6.2.5. include
6.2.6. include
6.2.7. key
6.2.8. key
6.2.9. logging
6.2.10. logging
6.2.11. lwres
6.2.12. lwres
6.2.13. options
6.2.14. options
6.2.17. trusted-keys
6.2.18. trusted-keys
6.2.19. view
6.2.20. view
6.2.22. zone
6.3. Zone File
6.3.2. Discussion of MX Records
6.3.4. Inverse Mapping in IPv4
6.3.5. Other Zone File Directives
6.3.6. BIND
7.2. chroot
7.2.1. The chroot
7.2.2. Using the setuid
8.1. Common Problems
8.1.1. It's not working; how can I figure out what's wrong?
8.2. Incrementing and Changing the Serial Number
8.3. Where Can I Get Help?
A.1. Acknowledgements
A.1.1. A Brief History of the DNS
A.3. General DNS
A.4.3. Other Documents About BIND