Bv9ARM.ch02.html revision 4a14ce5ba00ab7bc55c99ffdcf59c7a4ab902721
0N/A<!--
0N/A - Copyright (C) 2004-2009 Internet Systems Consortium, Inc. ("ISC")
0N/A - Copyright (C) 2000-2003 Internet Software Consortium.
0N/A -
0N/A - Permission to use, copy, modify, and/or distribute this software for any
0N/A - purpose with or without fee is hereby granted, provided that the above
0N/A - copyright notice and this permission notice appear in all copies.
0N/A -
0N/A - THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
0N/A - REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
0N/A - AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
0N/A - INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
0N/A - LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
0N/A - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
0N/A - PERFORMANCE OF THIS SOFTWARE.
0N/A-->
0N/A<!-- $Id: Bv9ARM.ch02.html,v 1.41 2009/07/11 01:12:46 tbox Exp $ -->
0N/A<html>
0N/A<head>
0N/A<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
0N/A<title>Chapter�2.�BIND Resource Requirements</title>
0N/A<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
0N/A<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
0N/A<link rel="up" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
0N/A<link rel="prev" href="Bv9ARM.ch01.html" title="Chapter�1.�Introduction">
0N/A<link rel="next" href="Bv9ARM.ch03.html" title="Chapter�3.�Name Server Configuration">
0N/A</head>
0N/A<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
0N/A<div class="navheader">
0N/A<table width="100%" summary="Navigation header">
0N/A<tr><th colspan="3" align="center">Chapter�2.�<acronym class="acronym">BIND</acronym> Resource Requirements</th></tr>
0N/A<tr>
0N/A<td width="20%" align="left">
0N/A<a accesskey="p" href="Bv9ARM.ch01.html">Prev</a>�</td>
0N/A<th width="60%" align="center">�</th>
0N/A<td width="20%" align="right">�<a accesskey="n" href="Bv9ARM.ch03.html">Next</a>
0N/A</td>
0N/A</tr>
0N/A</table>
0N/A<hr>
0N/A</div>
0N/A<div class="chapter" lang="en">
0N/A<div class="titlepage"><div><div><h2 class="title">
0N/A<a name="Bv9ARM.ch02"></a>Chapter�2.�<acronym class="acronym">BIND</acronym> Resource Requirements</h2></div></div></div>
0N/A<div class="toc">
0N/A<p><b>Table of Contents</b></p>
0N/A<dl>
0N/A<dt><span class="sect1"><a href="Bv9ARM.ch02.html#id2567584">Hardware requirements</a></span></dt>
0N/A<dt><span class="sect1"><a href="Bv9ARM.ch02.html#id2567610">CPU Requirements</a></span></dt>
0N/A<dt><span class="sect1"><a href="Bv9ARM.ch02.html#id2567623">Memory Requirements</a></span></dt>
0N/A<dt><span class="sect1"><a href="Bv9ARM.ch02.html#id2567854">Name Server Intensive Environment Issues</a></span></dt>
0N/A<dt><span class="sect1"><a href="Bv9ARM.ch02.html#id2567865">Supported Operating Systems</a></span></dt>
0N/A</dl>
0N/A</div>
0N/A<div class="sect1" lang="en">
0N/A<div class="titlepage"><div><div><h2 class="title" style="clear: both">
0N/A<a name="id2567584"></a>Hardware requirements</h2></div></div></div>
0N/A<p>
0N/A <acronym class="acronym">DNS</acronym> hardware requirements have
0N/A traditionally been quite modest.
0N/A For many installations, servers that have been pensioned off from
0N/A active duty have performed admirably as <acronym class="acronym">DNS</acronym> servers.
0N/A </p>
0N/A<p>
0N/A The DNSSEC features of <acronym class="acronym">BIND</acronym> 9
0N/A may prove to be quite
0N/A CPU intensive however, so organizations that make heavy use of these
0N/A features may wish to consider larger systems for these applications.
0N/A <acronym class="acronym">BIND</acronym> 9 is fully multithreaded, allowing
0N/A full utilization of
0N/A multiprocessor systems for installations that need it.
0N/A </p>
0N/A</div>
0N/A<div class="sect1" lang="en">
0N/A<div class="titlepage"><div><div><h2 class="title" style="clear: both">
0N/A<a name="id2567610"></a>CPU Requirements</h2></div></div></div>
0N/A<p>
0N/A CPU requirements for <acronym class="acronym">BIND</acronym> 9 range from
0N/A i486-class machines
0N/A for serving of static zones without caching, to enterprise-class
0N/A machines if you intend to process many dynamic updates and DNSSEC
0N/A signed zones, serving many thousands of queries per second.
0N/A </p>
0N/A</div>
0N/A<div class="sect1" lang="en">
0N/A<div class="titlepage"><div><div><h2 class="title" style="clear: both">
0N/A<a name="id2567623"></a>Memory Requirements</h2></div></div></div>
0N/A<p>
0N/A The memory of the server has to be large enough to fit the
0N/A cache and zones loaded off disk. The <span><strong class="command">max-cache-size</strong></span>
0N/A option can be used to limit the amount of memory used by the cache,
0N/A at the expense of reducing cache hit rates and causing more <acronym class="acronym">DNS</acronym>
0N/A traffic.
0N/A Additionally, if additional section caching
0N/A (<a href="Bv9ARM.ch06.html#acache" title="Additional Section Caching">the section called &#8220;Additional Section Caching&#8221;</a>) is enabled,
0N/A the <span><strong class="command">max-acache-size</strong></span> option can be used to
0N/A limit the amount
0N/A of memory used by the mechanism.
0N/A It is still good practice to have enough memory to load
0N/A all zone and cache data into memory &#8212; unfortunately, the best
0N/A way
0N/A to determine this for a given installation is to watch the name server
0N/A in operation. After a few weeks the server process should reach
0N/A a relatively stable size where entries are expiring from the cache as
0N/A fast as they are being inserted.
0N/A </p>
0N/A</div>
0N/A<div class="sect1" lang="en">
82N/A<div class="titlepage"><div><div><h2 class="title" style="clear: both">
82N/A<a name="id2567854"></a>Name Server Intensive Environment Issues</h2></div></div></div>
82N/A<p>
82N/A For name server intensive environments, there are two alternative
99N/A configurations that may be used. The first is where clients and
82N/A any second-level internal name servers query a main name server, which
0N/A has enough memory to build a large cache. This approach minimizes
0N/A the bandwidth used by external name lookups. The second alternative
0N/A is to set up second-level internal name servers to make queries
0N/A independently.
0N/A In this configuration, none of the individual machines needs to
0N/A have as much memory or CPU power as in the first alternative, but
0N/A this has the disadvantage of making many more external queries,
0N/A as none of the name servers share their cached data.
0N/A </p>
0N/A</div>
0N/A<div class="sect1" lang="en">
0N/A<div class="titlepage"><div><div><h2 class="title" style="clear: both">
0N/A<a name="id2567865"></a>Supported Operating Systems</h2></div></div></div>
0N/A<p>
0N/A ISC <acronym class="acronym">BIND</acronym> 9 compiles and runs on a large
0N/A number
0N/A of Unix-like operating systems and on
0N/A Microsoft Windows Server 2003 and 2008, and Windows XP and Vista.
0N/A For an up-to-date
0N/A list of supported systems, see the README file in the top level
0N/A directory
0N/A of the BIND 9 source distribution.
0N/A </p>
0N/A</div>
0N/A</div>
0N/A<div class="navfooter">
0N/A<hr>
0N/A<table width="100%" summary="Navigation footer">
0N/A<tr>
0N/A<td width="40%" align="left">
0N/A<a accesskey="p" href="Bv9ARM.ch01.html">Prev</a>�</td>
0N/A<td width="20%" align="center">�</td>
0N/A<td width="40%" align="right">�<a accesskey="n" href="Bv9ARM.ch03.html">Next</a>
0N/A</td>
0N/A</tr>
0N/A<tr>
0N/A<td width="40%" align="left" valign="top">Chapter�1.�Introduction�</td>
0N/A<td width="20%" align="center"><a accesskey="h" href="Bv9ARM.html">Home</a></td>
0N/A<td width="40%" align="right" valign="top">�Chapter�3.�Name Server Configuration</td>
0N/A</tr>
0N/A</table>
0N/A</div>
0N/A</body>
0N/A</html>
0N/A