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