Bv9ARM.2.html revision 15a44745412679c30a6d022733925af70a38b715
012a352f4b26cfd874db8d06debc495c2303e8b2Bob Halley<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML EXPERIMENTAL 970324//EN">
33cc94f04cb44dc247f605a954e45e5adc699977Automatic Updater - Copyright (C) 2000 Internet Software Consortium.
40f53fa8d9c6a4fc38c0014495e7a42b08f52481David Lawrence - Permission to use, copy, modify, and distribute this software for any
ec5347e2c775f027573ce5648b910361aa926c01Automatic Updater - purpose with or without fee is hereby granted, provided that the above
178f6ad061e54bc5babfca3577f72058fa0797c1Bob Halley - copyright notice and this permission notice appear in all copies.
40f53fa8d9c6a4fc38c0014495e7a42b08f52481David Lawrence - THE SOFTWARE IS PROVIDED "AS IS" AND INTERNET SOFTWARE CONSORTIUM
dafcb997e390efa4423883dafd100c975c4095d6Mark Andrews - DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL
dafcb997e390efa4423883dafd100c975c4095d6Mark Andrews - IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL
dafcb997e390efa4423883dafd100c975c4095d6Mark Andrews - INTERNET SOFTWARE CONSORTIUM BE LIABLE FOR ANY SPECIAL, DIRECT,
dafcb997e390efa4423883dafd100c975c4095d6Mark Andrews - INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING
dafcb997e390efa4423883dafd100c975c4095d6Mark Andrews - FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT,
dafcb997e390efa4423883dafd100c975c4095d6Mark Andrews - NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION
dafcb997e390efa4423883dafd100c975c4095d6Mark Andrews - WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
9c3531d72aeaad6c5f01efe6a1c82023e1379e4dDavid Lawrence<!-- $Id: Bv9ARM.2.html,v 1.9 2000/07/27 09:41:52 tale Exp $ -->
0b72c791466d0807bcf22522b5ddb7da902c2720Bob Halley<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML EXPERIMENTAL 970324//EN">
0b72c791466d0807bcf22522b5ddb7da902c2720Bob Halley<META NAME="GENERATOR" CONTENT="Adobe FrameMaker 5.5/HTML Export Filter">
0b72c791466d0807bcf22522b5ddb7da902c2720Bob Halley<TITLE> Section 2. BIND Resource Requirements</TITLE></HEAD>
0b72c791466d0807bcf22522b5ddb7da902c2720Bob HalleySection 2. BIND Resource Requirements</H1>
0b72c791466d0807bcf22522b5ddb7da902c2720Bob Halley2.1 Hardware requirements</H3>
460b427411b72da26b1836b9424e2e70d65d9394David LawrenceDNS 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.</P>
460b427411b72da26b1836b9424e2e70d65d9394David LawrenceThe DNSSEC and IPv6 features of BIND 9 may prove to be quite CPU intensive however, so organizations that make heavy use of these features may wish to consider larger systems for these applications. BIND 9 is now fully multithreaded, allowing full utilization of multiprocessor systems for installations that need it.</P>
dabea86dac4c01f852b7aea728f73b4f55a89d44Mark Andrews2.2 CPU Requirements</H3>
0b72c791466d0807bcf22522b5ddb7da902c2720Bob HalleyCPU requirements for BIND 9 range from i486-class machines 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.</P>
596912ee9ca8eb14d30707ec286ab5d28bd39b3eMark Andrews2.3 Memory Requirements </H3>
460b427411b72da26b1836b9424e2e70d65d9394David LawrenceThe 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, 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 to determine this for a given installation is to watch the nameserver 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.</P>
12e63bfe1d111ccb57f482b28d56c785cccc7cf7David Lawrence2.4 Nameserver Intensive Environment Issues</H3>
0b72c791466d0807bcf22522b5ddb7da902c2720Bob HalleyFor nameserver intensive environments, there are two alternative configurations that may be used. The first is where clients and any second-level internal nameservers query a main nameserver, which has enough memory to build a large cache. This approach minimizes the bandwidth used by external name lookups. The second alternative is to set up second-level internal nameservers to make queries independently. In this configuration, none of the individual machines needs to have as much memory or CPU power as in the first alternative, but this has the disadvantage of making many more external queries, as none of the nameservers share their cached data.</P>
0b72c791466d0807bcf22522b5ddb7da902c2720Bob Halley2.5 Supported Operating Systems</H3>
0b72c791466d0807bcf22522b5ddb7da902c2720Bob HalleyISC BIND 9 compiles and runs on the following operating systems:</P>
0b72c791466d0807bcf22522b5ddb7da902c2720Bob HalleyIBM AIX 4.3<BR>
0b72c791466d0807bcf22522b5ddb7da902c2720Bob HalleyHP HP-UX 11<BR>
0b72c791466d0807bcf22522b5ddb7da902c2720Bob HalleyIRIX64 6.5<BR>
0b72c791466d0807bcf22522b5ddb7da902c2720Bob HalleyRed Hat Linux 6.0, 6.1<BR>
0b72c791466d0807bcf22522b5ddb7da902c2720Bob HalleySun Solaris 2.6, 7, 8 (beta)<BR>
0b72c791466d0807bcf22522b5ddb7da902c2720Bob HalleyFreeBSD 3.4-STABLE<BR>
0b72c791466d0807bcf22522b5ddb7da902c2720Bob HalleyNetBSD-current with "unproven" pthreads</P>
0b72c791466d0807bcf22522b5ddb7da902c2720Bob Halley<p>Return to <A href="Bv9ARM.html">BIND 9 Administrator Reference Manual</A> table of contents.</p>