Bv9ARM.ch02.html revision 38a5df33f461f2379639ef95d282d3658f68ed04
2N/A<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
2N/A<!--
2N/A - Copyright (C) 2000-2017 Internet Systems Consortium, Inc. ("ISC")
2N/A -
2N/A - This Source Code Form is subject to the terms of the Mozilla Public
2N/A - License, v. 2.0. If a copy of the MPL was not distributed with this
2N/A - file, You can obtain one at http://mozilla.org/MPL/2.0/.
2N/A-->
2N/A<html lang="en">
2N/A<head>
2N/A<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
2N/A<title>Chapter�2.�BIND Resource Requirements</title>
2N/A<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
2N/A<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
2N/A<link rel="up" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
2N/A<link rel="prev" href="Bv9ARM.ch01.html" title="Chapter�1.�Introduction">
2N/A<link rel="next" href="Bv9ARM.ch03.html" title="Chapter�3.�Name Server Configuration">
2N/A</head>
2N/A<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
2N/A<div class="navheader">
58N/A<table width="100%" summary="Navigation header">
2N/A<tr><th colspan="3" align="center">Chapter�2.�<acronym class="acronym">BIND</acronym> Resource Requirements</th></tr>
2N/A<tr>
2N/A<td width="20%" align="left">
2N/A<a accesskey="p" href="Bv9ARM.ch01.html">Prev</a>�</td>
23N/A<th width="60%" align="center">�</th>
23N/A<td width="20%" align="right">�<a accesskey="n" href="Bv9ARM.ch03.html">Next</a>
23N/A</td>
23N/A</tr>
23N/A</table>
32N/A<hr>
32N/A</div>
32N/A<div class="chapter">
34N/A<div class="titlepage"><div><div><h1 class="title">
32N/A<a name="Bv9ARM.ch02"></a>Chapter�2.�<acronym class="acronym">BIND</acronym> Resource Requirements</h1></div></div></div>
34N/A<div class="toc">
32N/A<p><b>Table of Contents</b></p>
32N/A<dl class="toc">
58N/A<dt><span class="section"><a href="Bv9ARM.ch02.html#hw_req">Hardware requirements</a></span></dt>
32N/A<dt><span class="section"><a href="Bv9ARM.ch02.html#cpu_req">CPU Requirements</a></span></dt>
2N/A<dt><span class="section"><a href="Bv9ARM.ch02.html#mem_req">Memory Requirements</a></span></dt>
38N/A<dt><span class="section"><a href="Bv9ARM.ch02.html#intensive_env">Name Server Intensive Environment Issues</a></span></dt>
38N/A<dt><span class="section"><a href="Bv9ARM.ch02.html#supported_os">Supported Operating Systems</a></span></dt>
38N/A</dl>
38N/A</div>
38N/A
38N/A <div class="section">
38N/A<div class="titlepage"><div><div><h2 class="title" style="clear: both">
38N/A<a name="hw_req"></a>Hardware requirements</h2></div></div></div>
38N/A <p>
83N/A <acronym class="acronym">DNS</acronym> hardware requirements have
83N/A traditionally been quite modest.
83N/A For many installations, servers that have been pensioned off from
2N/A active duty have performed admirably as <acronym class="acronym">DNS</acronym> servers.
92N/A </p>
92N/A <p>
92N/A The DNSSEC features of <acronym class="acronym">BIND</acronym> 9
2N/A may prove to be quite
2N/A CPU intensive however, so organizations that make heavy use of these
83N/A features may wish to consider larger systems for these applications.
83N/A <acronym class="acronym">BIND</acronym> 9 is fully multithreaded, allowing
2N/A full utilization of
34N/A multiprocessor systems for installations that need it.
2N/A </p>
34N/A </div>
34N/A <div class="section">
2N/A<div class="titlepage"><div><div><h2 class="title" style="clear: both">
34N/A<a name="cpu_req"></a>CPU Requirements</h2></div></div></div>
53N/A <p>
34N/A CPU requirements for <acronym class="acronym">BIND</acronym> 9 range from
70N/A i486-class machines
2N/A for serving of static zones without caching, to enterprise-class
2N/A machines if you intend to process many dynamic updates and DNSSEC
2N/A signed zones, serving many thousands of queries per second.
2N/A </p>
70N/A </div>
2N/A <div class="section">
2N/A<div class="titlepage"><div><div><h2 class="title" style="clear: both">
2N/A<a name="mem_req"></a>Memory Requirements</h2></div></div></div>
70N/A <p>
70N/A The memory of the server has to be large enough to fit the
70N/A cache and zones loaded off disk. The <span class="command"><strong>max-cache-size</strong></span>
70N/A option can be used to limit the amount of memory used by the cache,
70N/A at the expense of reducing cache hit rates and causing more <acronym class="acronym">DNS</acronym>
70N/A traffic.
70N/A Additionally, if additional section caching
70N/A (<a class="xref" href="Bv9ARM.ch06.html#acache" title="Additional Section Caching">the section called &#8220;Additional Section Caching&#8221;</a>) is enabled,
70N/A the <span class="command"><strong>max-acache-size</strong></span> option can be used to
70N/A limit the amount
6N/A of memory used by the mechanism.
6N/A It is still good practice to have enough memory to load
6N/A all zone and cache data into memory &#8212; unfortunately, the best
34N/A way
34N/A to determine this for a given installation is to watch the name server
34N/A in operation. After a few weeks the server process should reach
34N/A a relatively stable size where entries are expiring from the cache as
34N/A fast as they are being inserted.
34N/A </p>
34N/A
32N/A </div>
38N/A
34N/A <div class="section">
38N/A<div class="titlepage"><div><div><h2 class="title" style="clear: both">
34N/A<a name="intensive_env"></a>Name Server Intensive Environment Issues</h2></div></div></div>
92N/A
92N/A <p>
92N/A For name server intensive environments, there are two alternative
92N/A configurations that may be used. The first is where clients and
92N/A any second-level internal name servers query a main name server, which
92N/A has enough memory to build a large cache. This approach minimizes
92N/A the bandwidth used by external name lookups. The second alternative
92N/A is to set up second-level internal name servers to make queries
92N/A independently.
34N/A In this configuration, none of the individual machines needs to
38N/A have as much memory or CPU power as in the first alternative, but
34N/A this has the disadvantage of making many more external queries,
38N/A as none of the name servers share their cached data.
32N/A </p>
32N/A </div>
32N/A
32N/A <div class="section">
34N/A<div class="titlepage"><div><div><h2 class="title" style="clear: both">
32N/A<a name="supported_os"></a>Supported Operating Systems</h2></div></div></div>
32N/A
58N/A <p>
2N/A ISC <acronym class="acronym">BIND</acronym> 9 compiles and runs on a large
2N/A 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>
<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.2rc1</p>
</body>
</html>