From 5dccc8b2a55f0222ffda0ff0a981bad4eb0563be Mon Sep 17 00:00:00 2001 From: Andreas Gustafsson Date: Mon, 18 Jun 2001 22:35:02 +0000 Subject: [PATCH] cache size limiting is no longer a 'future' feature; misc other cleanup --- doc/arm/Bv9ARM-book.xml | 30 +++++++++++++++++------------- doc/arm/Bv9ARM.ch02.html | 10 +++++----- doc/arm/Bv9ARM.ch06.html | 11 +++++------ doc/arm/Bv9ARM.html | 3 +-- 4 files changed, 28 insertions(+), 26 deletions(-) diff --git a/doc/arm/Bv9ARM-book.xml b/doc/arm/Bv9ARM-book.xml index d21f7b68a6..5ef2af0250 100644 --- a/doc/arm/Bv9ARM-book.xml +++ b/doc/arm/Bv9ARM-book.xml @@ -2,7 +2,7 @@ - + BIND 9 Administrator Reference Manual @@ -363,8 +363,11 @@ be placed inside a firewall. - <acronym>BIND</acronym> Resource Requirements -Hardware requirements +<acronym>BIND</acronym> Resource Requirements + + +Hardware requirements + DNS hardware requirements have traditionally been quite modest. For many installations, servers that have been pensioned off from active duty have performed admirably as DNS servers. @@ -378,10 +381,11 @@ multiprocessor systems for installations that need it. for serving of static zones without caching, to enterprise-class machines if you intend to process many dynamic updates and DNSSEC signed zones, serving many thousands of queries per second. -Memory Requirements + +Memory Requirements The memory of the server has to be large enough to fit the -cache and zones loaded off disk. Future releases of BIND 9 will -provide methods to limit the amount of memory used by the cache, +cache and zones loaded off disk. The max-cache-size +option can be used to limit the amount of memory used by the cache, at the expense of reducing cache hit rates and causing more DNS traffic. It is still good practice to have enough memory to load all zone and cache data into memory — unfortunately, the best way @@ -390,6 +394,7 @@ in operation. After a few weeks the server process should reach a relatively stable size where entries are expiring from the cache as fast as they are being inserted. Ideally, the resource limits should be set higher than this stable size. + Nameserver Intensive Environment Issues For nameserver intensive environments, there are two alternative configurations that may be used. The first is where clients and @@ -2237,10 +2242,10 @@ Usage that contains the users who should have access. The UNIX control channel type of BIND 8 is not supported - in BIND 9.0.0, and is not expected to be added in future + in BIND 9, and is not expected to be added in future releases. If it is present in the controls statement from a - BIND 8 configuration file, a non-fatal warning will be - logged. + BIND 8 configuration file, it is ignored + and a warning is logged. @@ -2248,8 +2253,7 @@ Usage include filename; - <command>include</command> Statement Definition and -Usage + <command>include</command> Statement Definition and Usage The include statement inserts the specified file at the point that the include @@ -2262,7 +2266,7 @@ Usage <command>key</command> Statement Grammar - key key_id { +key key_id { algorithm string; secret string; }; @@ -2991,7 +2995,7 @@ The default is no. multiple-cnames This option was used in BIND 8 to allow a domain name to allow multiple CNAME records in violation of the -DNS standards. BIND 9.1 always strictly +DNS standards. BIND 9.2 always strictly enforces the CNAME rules both in master files and dynamic updates. diff --git a/doc/arm/Bv9ARM.ch02.html b/doc/arm/Bv9ARM.ch02.html index 44c98e3fd3..17c954c9fb 100644 --- a/doc/arm/Bv9ARM.ch02.html +++ b/doc/arm/Bv9ARM.ch02.html @@ -164,11 +164,11 @@ NAME="AEN235" >

The memory of the server has to be large enough to fit the -cache and zones loaded off disk. Future releases of BIND 9 will -provide methods to limit the amount of memory used by the cache, +cache and zones loaded off disk. The max-cache-size +option can be used to limit the amount of memory used by the cache, at the expense of reducing cache hit rates and causing more DNSBIND 9.0.0, and is not expected to be added in future +> 9, and is not expected to be added in future releases. If it is present in the controls statement from a BIND 8 configuration file, a non-fatal warning will be - logged.

8 configuration file, it is ignored + and a warning is logged.

6.2.6. include Statement Definition and -Usage Statement Definition and Usage

The BIND 9.1 always strictly +> 9.2 always strictly enforces the CNAME rules both in master files and dynamic updates.

include Statement Definition and -Usage Statement Definition and Usage
6.2.7.