0N/A>BIND Resource Requirements</
TITLE 0N/ACONTENT="Modular DocBook HTML Stylesheet Version 1.54"><
LINK 0N/ATITLE="Introduction " 0N/ATITLE="Nameserver Configuration" 0N/A> Resource Requirements</
A 0N/A>Table of Contents</
B 0N/A>Hardware requirements</
A 0N/A>Memory Requirements</
A 0N/A>Nameserver Intensive Environment Issues</
A 0N/A>Supported Operating Systems</
A 0N/A>2.1. Hardware requirements</
A 0N/A> hardware requirements have traditionally been quite modest.
0N/AFor many installations, servers that have been pensioned off from
0N/Aactive duty have performed admirably as <
SPAN 0N/A>The DNSSEC and IPv6 features of <
SPAN 0N/A> 9 may prove to be quite
0N/ACPU intensive however, so organizations that make heavy use of these
0N/Afeatures may wish to consider larger systems for these applications.
0N/A> 9 is now fully multithreaded, allowing full utilization of
0N/Amultiprocessor systems for installations that need it.</
P 0N/A>2.2. CPU Requirements</
A 0N/A>CPU requirements for <
SPAN 0N/A> 9 range from i486-class machines
0N/Afor serving of static zones without caching, to enterprise-class
0N/Amachines if you intend to process many dynamic updates and DNSSEC
0N/Asigned zones, serving many thousands of queries per second.</
P 0N/A>2.3. Memory Requirements</
A 0N/A>The memory of the server has to be large enough to fit the
0N/Acache and zones loaded off disk. Future releases of <
SPAN 0N/Aprovide methods to limit the amount of memory used by the cache,
0N/Aat the expense of reducing cache hit rates and causing more <
SPAN 0N/Atraffic. It is still good practice to have enough memory to load
0N/Aall zone and cache data into memory — unfortunately, the best way
0N/Ato determine this for a given installation is to watch the nameserver
0N/Ain operation. After a few weeks the server process should reach
0N/Aa relatively stable size where entries are expiring from the cache as
0N/Afast as they are being inserted. Ideally, the resource limits should
0N/Abe set higher than this stable size.</
P 0N/A>2.4. Nameserver Intensive Environment Issues</
A 0N/A>For nameserver intensive environments, there are two alternative
0N/Aconfigurations that may be used. The first is where clients and
0N/Aany second-level internal nameservers query a main nameserver, which
0N/Ahas enough memory to build a large cache. This approach minimizes
0N/Athe bandwidth used by external name lookups. The second alternative
0N/Ais to set up second-level internal nameservers to make queries independently.
0N/AIn this configuration, none of the individual machines needs to
0N/Ahave as much memory or CPU power as in the first alternative, but
0N/Athis has the disadvantage of making many more external queries,
0N/Aas none of the nameservers share their cached data.</
P 0N/A>2.5. Supported Operating Systems</
A 0N/A> 9 compiles and runs on the following operating
0N/A>Red Hat Linux 6.0, 6.1</
P 0N/A>Sun Solaris 2.6, 7, 8 (beta)</
P 0N/A>FreeBSD 3.4-STABLE</
P 0N/A>NetBSD-current with "unproven" pthreads</
P 0N/A>Nameserver Configuration</
TD