Bv9ARM.2.html revision f83bad6f7890281b90c9595198f88b88a1ea69f6
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML EXPERIMENTAL 970324//EN">
75c0816e8295e180f4bc7f10db3d0d880383bc1cMark Andrews - Copyright (C) 2000 Internet Software Consortium.
4a14ce5ba00ab7bc55c99ffdcf59c7a4ab902721Automatic Updater - Permission to use, copy, modify, and distribute this software for any
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein - purpose with or without fee is hereby granted, provided that the above
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein - copyright notice and this permission notice appear in all copies.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein - THE SOFTWARE IS PROVIDED "AS IS" AND INTERNET SOFTWARE CONSORTIUM DISCLAIMS
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein - ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein - OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL INTERNET SOFTWARE
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein - CONSORTIUM BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein - DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein - PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein - ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<!-- $Id: Bv9ARM.2.html,v 1.8 2000/07/12 17:54:28 gson Exp $ -->
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML EXPERIMENTAL 970324//EN">
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<META NAME="GENERATOR" CONTENT="Adobe FrameMaker 5.5/HTML Export Filter">
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<TITLE> Section 2. BIND Resource Requirements</TITLE></HEAD>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob AusteinSection 2. BIND Resource Requirements</H1>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein2.1 Hardware requirements</H3>
71c66a876ecca77923638d3f94cc0783152b2f03Mark AndrewsDNS 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>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob AusteinThe 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>
5fa6a064b8301e4f274bd132fd577def59e4fb4cTinderbox User2.2 CPU Requirements</H3>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob AusteinCPU 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>
a3ff24aaa545c45b8c581b2127d02d735aff8881Tinderbox User2.3 Memory Requirements </H3>
a3ff24aaa545c45b8c581b2127d02d735aff8881Tinderbox UserThe 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>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein2.4 Nameserver Intensive Environment Issues</H3>
a3ff24aaa545c45b8c581b2127d02d735aff8881Tinderbox UserFor 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>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein2.5 Supported Operating Systems</H3>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob AusteinISC BIND 9 compiles and runs on the following operating systems:</P>
a3ff24aaa545c45b8c581b2127d02d735aff8881Tinderbox UserIBM AIX 4.3<BR>
a3ff24aaa545c45b8c581b2127d02d735aff8881Tinderbox UserHP HP-UX 11<BR>
7208386cd37a2092c70eddf80cf29519b16c4c80Mark AndrewsIRIX64 6.5<BR>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob AusteinRed Hat Linux 6.0, 6.1<BR>
507151045be68c671ffd4e2f37e17cdfa0376fc4Automatic UpdaterSun Solaris 2.6, 7, 8 (beta)<BR>
507151045be68c671ffd4e2f37e17cdfa0376fc4Automatic UpdaterFreeBSD 3.4-STABLE<BR>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob AusteinNetBSD-current with "unproven" pthreads</P>
71c66a876ecca77923638d3f94cc0783152b2f03Mark Andrews<p>Return to <A href="Bv9ARM.html">BIND 9 Administrator Reference Manual</A> table of contents.</p>