<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <HTML ><HEAD ><TITLE >BIND Resource Requirements</TITLE ><META NAME="GENERATOR" CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK REL="HOME" TITLE="BIND 9 Administrator Reference Manual" HREF="Bv9ARM.html"><LINK REL="PREVIOUS" TITLE="Introduction " HREF="Bv9ARM.ch01.html"><LINK REL="NEXT" TITLE="Name Server Configuration" HREF="Bv9ARM.ch03.html"></HEAD ><BODY CLASS="chapter" BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#0000FF" VLINK="#840084" ALINK="#0000FF" ><DIV CLASS="NAVHEADER" ><TABLE SUMMARY="Header navigation table" WIDTH="100%" BORDER="0" CELLPADDING="0" CELLSPACING="0" ><TR ><TH COLSPAN="3" ALIGN="center" >BIND 9 Administrator Reference Manual</TH ></TR ><TR ><TD WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A HREF="Bv9ARM.ch01.html" ACCESSKEY="P" >Prev</A ></TD ><TD WIDTH="80%" ALIGN="center" VALIGN="bottom" ></TD ><TD WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A HREF="Bv9ARM.ch03.html" ACCESSKEY="N" >Next</A ></TD ></TR ></TABLE ><HR ALIGN="LEFT" WIDTH="100%"></DIV ><DIV CLASS="chapter" ><H1 ><A NAME="ch02" ></A >Chapter 2. <ACRONYM CLASS="acronym" >BIND</ACRONYM > Resource Requirements</H1 ><DIV CLASS="TOC" ><DL ><DT ><B >Table of Contents</B ></DT ><DT >2.1. <A HREF="Bv9ARM.ch02.html#AEN228" >Hardware requirements</A ></DT ><DT >2.2. <A HREF="Bv9ARM.ch02.html#AEN236" >CPU Requirements</A ></DT ><DT >2.3. <A HREF="Bv9ARM.ch02.html#AEN240" >Memory Requirements</A ></DT ><DT >2.4. <A HREF="Bv9ARM.ch02.html#AEN245" >Name Server Intensive Environment Issues</A ></DT ><DT >2.5. <A HREF="Bv9ARM.ch02.html#AEN248" >Supported Operating Systems</A ></DT ></DL ></DIV ><DIV CLASS="sect1" ><H1 CLASS="sect1" ><A NAME="AEN228" >2.1. Hardware requirements</A ></H1 ><P ><ACRONYM CLASS="acronym" >DNS</ACRONYM > hardware requirements have traditionally been quite modest. For many installations, servers that have been pensioned off from active duty have performed admirably as <ACRONYM CLASS="acronym" >DNS</ACRONYM > servers.</P ><P >The DNSSEC and IPv6 features of <ACRONYM CLASS="acronym" >BIND</ACRONYM > 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. <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" ><H1 CLASS="sect1" ><A NAME="AEN236" >2.2. CPU Requirements</A ></H1 ><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" ><H1 CLASS="sect1" ><A NAME="AEN240" >2.3. Memory Requirements</A ></H1 ><P >The memory of the server has to be large enough to fit the cache and zones loaded off disk. The <B CLASS="command" >max-cache-size</B > 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. 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 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" ><H1 CLASS="sect1" ><A NAME="AEN245" >2.4. Name Server Intensive Environment Issues</A ></H1 ><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" ><H1 CLASS="sect1" ><A NAME="AEN248" >2.5. Supported Operating Systems</A ></H1 ><P >ISC <ACRONYM CLASS="acronym" >BIND</ACRONYM > 9 compiles and runs on a large number of Unix-like operating system and on Windows NT / 2000. 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 ALIGN="LEFT" WIDTH="100%"><TABLE SUMMARY="Footer navigation table" WIDTH="100%" BORDER="0" CELLPADDING="0" CELLSPACING="0" ><TR ><TD WIDTH="33%" ALIGN="left" VALIGN="top" ><A HREF="Bv9ARM.ch01.html" ACCESSKEY="P" >Prev</A ></TD ><TD WIDTH="34%" ALIGN="center" VALIGN="top" ><A HREF="Bv9ARM.html" ACCESSKEY="H" >Home</A ></TD ><TD WIDTH="33%" ALIGN="right" VALIGN="top" ><A HREF="Bv9ARM.ch03.html" ACCESSKEY="N" >Next</A ></TD ></TR ><TR ><TD WIDTH="33%" ALIGN="left" VALIGN="top" >Introduction</TD ><TD WIDTH="34%" ALIGN="center" VALIGN="top" > </TD ><TD WIDTH="33%" ALIGN="right" VALIGN="top" >Name Server Configuration</TD ></TR ></TABLE ></DIV ></BODY ></HTML >
