diff --git a/doc/arm/Bv9ARM-book.xml b/doc/arm/Bv9ARM-book.xml index f3ea10d152..78f8da57cc 100644 --- a/doc/arm/Bv9ARM-book.xml +++ b/doc/arm/Bv9ARM-book.xml @@ -2,7 +2,7 @@ - + BIND 9 Administrator Reference Manual @@ -2168,10 +2168,10 @@ the system has an interface. inet ...; }; - - - <command>controls</command> Statement Definition and -Usage + + + +<command>controls</command> Statement Definition and Usage The controls statement declares control channels to be used by system administrators to affect the @@ -2272,26 +2272,37 @@ Usage }; - - <command>key</command> Statement Definition and Usage - The key statement defines a shared - secret key for use with TSIG, see . + +<command>key</command> Statement Definition and Usage - The key_id, also known as the - key name, is a domain name uniquely identifying the key. It can - be used in a "server" statement to cause requests sent to that - server to be signed with this key, or in address match lists to - verify that incoming requests have been signed with a key - matching this name, algorithm, and secret. +The key statement defines a shared +secret key for use with TSIG, see . - The algorithm_id is a string - that specifies a security/authentication algorithm. The only - algorithm currently supported with TSIG authentication is - hmac-md5. The - secret_string is the secret to be - used by the algorithm, and is treated as a base-64 encoded - string. + +The key statement can occur at the top level +of the configuration file or inside a view +statement. Keys defined in top-level key +statements can be used in all views. Keys intended for use in +a controls statement +(see ) +must be defined at the top level. + + +The key_id, also known as the +key name, is a domain name uniquely identifying the key. It can +be used in a "server" statement to cause requests sent to that +server to be signed with this key, or in address match lists to +verify that incoming requests have been signed with a key +matching this name, algorithm, and secret. + +The algorithm_id is a string +that specifies a security/authentication algorithm. The only +algorithm currently supported with TSIG authentication is +hmac-md5. The +secret_string is the secret to be +used by the algorithm, and is treated as a base-64 encoded +string. @@ -3927,7 +3938,8 @@ failure response other than those above. - + + <command>server</command> Statement Grammar server ip_addr { @@ -3942,12 +3954,24 @@ failure response other than those above. -<command>server</command> Statement Definition -and Usage -The server statement defines the characteristics + +<command>server</command> Statement Definition and Usage + +The server statement defines characteristics to be associated with a remote nameserver. + +The server statement can occur at the top level of the +configuration file or inside a view statement. +If a view statement contains +one or more server statements, only those +apply to the view and any top-level ones are ignored. +If a view contains no server statements, +any top-level server statements are used as +defaults. + + If you discover that a remote server is giving out bad data, marking it as bogus will prevent further queries to it. The default value of bogus is no. @@ -4004,7 +4028,10 @@ to be signed by this key. Although the grammar of the keys clause allows for multiple keys, only a single key per server is currently -supported. +supported. + + + <command>trusted-keys</command> Statement Grammar trusted-keys { string number number number string ; diff --git a/doc/arm/Bv9ARM.ch06.html b/doc/arm/Bv9ARM.ch06.html index 0c1f89c7a5..2e81c24087 100644 --- a/doc/arm/Bv9ARM.ch06.html +++ b/doc/arm/Bv9ARM.ch06.html @@ -91,7 +91,7 @@ HREF="Bv9ARM.ch06.html#Configuration_File_Grammar" >
6.3. Zone File
6.2.4. controls Statement Definition and -Usage Statement Definition and Usage

The key statement defines a shared - secret key for use with TSIG, see Section 4.4.

The key statement can occur at the top level +of the configuration file or inside a view +statement. Keys defined in top-level key +statements can be used in all views. Keys intended for use in +a controls statement +(see Section 6.2.4) +must be defined at the top level. +

The key_id, also known as the - key name, is a domain name uniquely identifying the key. It can - be used in a "server" statement to cause requests sent to that - server to be signed with this key, or in address match lists to - verify that incoming requests have been signed with a key - matching this name, algorithm, and secret.

The algorithm_id is a string - that specifies a security/authentication algorithm. The only - algorithm currently supported with TSIG authentication is - hmac-md5. The - secret_string is the secret to be - used by the algorithm, and is treated as a base-64 encoded - string.

6.2.9. logging

6.2.10. logging

6.2.10.1. The channel

The server statement defines the characteristics +> statement defines characteristics to be associated with a remote nameserver.

The server statement can occur at the top level of the +configuration file or inside a view statement. +If a view statement contains +one or more server statements, only those +apply to the view and any top-level ones are ignored. +If a view contains no server statements, +any top-level server statements are used as +defaults. +

If you discover that a remote server is giving out bad data, marking it as bogus will prevent further queries to it. The default value of

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

controls Statement Definition and -Usage Statement Definition and Usage

6.2.5.
6.2.9. logging
6.2.10. logging
6.2.11. lwres
6.2.12. lwres
6.2.13. options
6.2.14. optionsserver Statement Definition -and Usage Statement Definition and Usage
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