1<!--
2 - Copyright (C) 2004-2015 Internet Systems Consortium, Inc. ("ISC")
3 - Copyright (C) 2000-2003 Internet Software Consortium.
4 -
5 - Permission to use, copy, modify, and/or distribute this software for any
6 - purpose with or without fee is hereby granted, provided that the above
7 - copyright notice and this permission notice appear in all copies.
8 -
9 - THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
10 - REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
11 - AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
12 - INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
13 - LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
14 - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
15 - PERFORMANCE OF THIS SOFTWARE.
16-->
17<!-- Id -->
18<html>
19<head>
20<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
21<title>Chapter�2.�BIND Resource Requirements</title>
22<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
23<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
24<link rel="up" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
25<link rel="prev" href="Bv9ARM.ch01.html" title="Chapter�1.�Introduction">
26<link rel="next" href="Bv9ARM.ch03.html" title="Chapter�3.�Name Server Configuration">
27</head>
28<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
29<div class="navheader">
30<table width="100%" summary="Navigation header">
31<tr><th colspan="3" align="center">Chapter�2.�<acronym class="acronym">BIND</acronym> Resource Requirements</th></tr>
32<tr>
33<td width="20%" align="left">
34<a accesskey="p" href="Bv9ARM.ch01.html">Prev</a>�</td>
35<th width="60%" align="center">�</th>
36<td width="20%" align="right">�<a accesskey="n" href="Bv9ARM.ch03.html">Next</a>
37</td>
38</tr>
39</table>
40<hr>
41</div>
42<div class="chapter" lang="en">
43<div class="titlepage"><div><div><h2 class="title">
44<a name="Bv9ARM.ch02"></a>Chapter�2.�<acronym class="acronym">BIND</acronym> Resource Requirements</h2></div></div></div>
45<div class="toc">
46<p><b>Table of Contents</b></p>
47<dl>
48<dt><span class="sect1"><a href="Bv9ARM.ch02.html#id2567685">Hardware requirements</a></span></dt>
49<dt><span class="sect1"><a href="Bv9ARM.ch02.html#id2567712">CPU Requirements</a></span></dt>
50<dt><span class="sect1"><a href="Bv9ARM.ch02.html#id2567793">Memory Requirements</a></span></dt>
51<dt><span class="sect1"><a href="Bv9ARM.ch02.html#id2567819">Name Server Intensive Environment Issues</a></span></dt>
52<dt><span class="sect1"><a href="Bv9ARM.ch02.html#id2567830">Supported Operating Systems</a></span></dt>
53</dl>
54</div>
55<div class="sect1" lang="en">
56<div class="titlepage"><div><div><h2 class="title" style="clear: both">
57<a name="id2567685"></a>Hardware requirements</h2></div></div></div>
58<p>
59        <acronym class="acronym">DNS</acronym> hardware requirements have
60        traditionally been quite modest.
61        For many installations, servers that have been pensioned off from
62        active duty have performed admirably as <acronym class="acronym">DNS</acronym> servers.
63      </p>
64<p>
65        The DNSSEC features of <acronym class="acronym">BIND</acronym> 9
66        may prove to be quite
67        CPU intensive however, so organizations that make heavy use of these
68        features may wish to consider larger systems for these applications.
69        <acronym class="acronym">BIND</acronym> 9 is fully multithreaded, allowing
70        full utilization of
71        multiprocessor systems for installations that need it.
72      </p>
73</div>
74<div class="sect1" lang="en">
75<div class="titlepage"><div><div><h2 class="title" style="clear: both">
76<a name="id2567712"></a>CPU Requirements</h2></div></div></div>
77<p>
78        CPU requirements for <acronym class="acronym">BIND</acronym> 9 range from
79        i486-class machines
80        for serving of static zones without caching, to enterprise-class
81        machines if you intend to process many dynamic updates and DNSSEC
82        signed zones, serving many thousands of queries per second.
83      </p>
84</div>
85<div class="sect1" lang="en">
86<div class="titlepage"><div><div><h2 class="title" style="clear: both">
87<a name="id2567793"></a>Memory Requirements</h2></div></div></div>
88<p>
89        The memory of the server has to be large enough to fit the
90        cache and zones loaded off disk.  The <span><strong class="command">max-cache-size</strong></span>
91        option can be used to limit the amount of memory used by the cache,
92        at the expense of reducing cache hit rates and causing more <acronym class="acronym">DNS</acronym>
93        traffic.
94        Additionally, if additional section caching
95        (<a href="Bv9ARM.ch06.html#acache" title="Additional Section Caching">the section called &#8220;Additional Section Caching&#8221;</a>) is enabled,
96        the <span><strong class="command">max-acache-size</strong></span> option can be used to
97        limit the amount
98        of memory used by the mechanism.
99        It is still good practice to have enough memory to load
100        all zone and cache data into memory &#8212; unfortunately, the best
101        way
102        to determine this for a given installation is to watch the name server
103        in operation. After a few weeks the server process should reach
104        a relatively stable size where entries are expiring from the cache as
105        fast as they are being inserted.
106      </p>
107</div>
108<div class="sect1" lang="en">
109<div class="titlepage"><div><div><h2 class="title" style="clear: both">
110<a name="id2567819"></a>Name Server Intensive Environment Issues</h2></div></div></div>
111<p>
112        For name server intensive environments, there are two alternative
113        configurations that may be used. The first is where clients and
114        any second-level internal name servers query a main name server, which
115        has enough memory to build a large cache. This approach minimizes
116        the bandwidth used by external name lookups. The second alternative
117        is to set up second-level internal name servers to make queries
118        independently.
119        In this configuration, none of the individual machines needs to
120        have as much memory or CPU power as in the first alternative, but
121        this has the disadvantage of making many more external queries,
122        as none of the name servers share their cached data.
123      </p>
124</div>
125<div class="sect1" lang="en">
126<div class="titlepage"><div><div><h2 class="title" style="clear: both">
127<a name="id2567830"></a>Supported Operating Systems</h2></div></div></div>
128<p>
129        ISC <acronym class="acronym">BIND</acronym> 9 compiles and runs on a large
130        number
131        of Unix-like operating systems and on
132        Microsoft Windows Server 2003 and 2008, and Windows XP and Vista.
133        For an up-to-date
134        list of supported systems, see the README file in the top level
135        directory
136        of the BIND 9 source distribution.
137      </p>
138</div>
139</div>
140<div class="navfooter">
141<hr>
142<table width="100%" summary="Navigation footer">
143<tr>
144<td width="40%" align="left">
145<a accesskey="p" href="Bv9ARM.ch01.html">Prev</a>�</td>
146<td width="20%" align="center">�</td>
147<td width="40%" align="right">�<a accesskey="n" href="Bv9ARM.ch03.html">Next</a>
148</td>
149</tr>
150<tr>
151<td width="40%" align="left" valign="top">Chapter�1.�Introduction�</td>
152<td width="20%" align="center"><a accesskey="h" href="Bv9ARM.html">Home</a></td>
153<td width="40%" align="right" valign="top">�Chapter�3.�Name Server Configuration</td>
154</tr>
155</table>
156</div>
157<p style="text-align: center;">BIND 9.10.2-P4</p>
158</body>
159</html>
160