From: Andreas Gustafsson Date: Wed, 27 Jun 2001 17:47:20 +0000 (+0000) Subject: regenerated X-Git-Tag: v9.1.3rc3~2 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=b57f903e58a6e788d4a0688994b0b05f57030686;p=thirdparty%2Fbind9.git regenerated --- diff --git a/doc/arm/Bv9ARM.ch06.html b/doc/arm/Bv9ARM.ch06.html index 68f8291a37b..2499a3be68e 100644 --- a/doc/arm/Bv9ARM.ch06.html +++ b/doc/arm/Bv9ARM.ch06.html @@ -90,7 +90,7 @@ HREF="Bv9ARM.ch06.html#Configuration_File_Grammar" >
6.3. Zone File

These options control the server's behavior when answering queries -which have additional data, or when following CNAME and DNAME -chains to provide additional data. +> +

These options control the behavior of an authoritative server when +answering queries which have additional data, or when following CNAME +and DNAME chains.

+ +

When both of these options are set to (the default) and a -query is being answered from authoratitive data (a zone +query is being answered from authoritative data (a zone configured into the server), the additional data section of the -reply will be filled in using data from other authoratitive zones +reply will be filled in using data from other authoritative zones and from the cache. In some situations this is undesirable, such -as when there is concern over the correctness of the cache, or in +as when there is concern over the correctness of the cache, or in servers where slave zones may be added and modified by untrusted third parties. Also, avoiding the search for this additional data will speed up server operations at the possible expense of additional queries to resolve what would otherwise be provided in the additional section.

+ +

For example, if a query asks for an MX record for host foo.example.commail.example.net will be provided as well, -if known. These options disable this behavior. +if known. Setting these options to no disables this behavior. +

+ +

These options are intended for use in authoritative-only +servers, or in authoritative-only views. +In other words, they should only be set to +no if the option recursion no; +has also been specified. Setting them to no in a +recursive server will have unexpected side effects such as causing +recursion to not function. +

+ +

Specifying additional-from-cache no actually +disables the use of the cache not only for additional data lookups +but also when looking up the answer. This is usually the desired +behavior in an authoritative-only server where the correctness of +the cached data is an issue. +

+ +

When a name server is non-recursively queried for a name that is not +below the apex of any served zone, it normally answers with an +"upwards referral" to the root servers or the servers of some other +known parent of the query name. Since the data in an upwards referral +comes from the cache, the server will not be able to provide upwards +referrals when additional-from-cache no +has been specified. Instead, it will respond to such queries +with REFUSED. This should not cause any problems since +upwards referrals are not required for the resolution process.

+ +

6.2.14.2. Forwarding

6.2.14.4. Interfaces

6.2.14.5. Query Address

The server supports two zone transfer methods. +

Zone transfers can be sent using two different formats, +one-answer uses -one DNS message per resource record transferred. and many-answers packs -as many resource records as possible into a message. . +The transfer-format option is used +on the master server to determine which format it sends. +one-answer uses one DNS message per +resource record transferred. +many-answers is -more efficient, but is only known to be understood by packs as many resource records as +possible into a message. many-answers is more +efficient, but is only supported by relatively new slave servers, +such as BIND 9, BIND -8.x and patched versions of 8.x and patched +versions of BIND 4.9.5. The default is 4.9.5. The default is +many-answers. transfer-format may -be overridden on a per-server basis by using the +may be overridden on a per-server basis by using the +server statement.

statement. +

+

6.2.14.7. Resource Limits

6.2.14.8. 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