/usr/share/doc/bind
NameSizeModeActions
sample/-0755rm
Bv9ARM.ch01.html271680644editdlrm
Bv9ARM.ch02.html71600644editdlrm
Bv9ARM.ch03.html286990644editdlrm
Bv9ARM.ch04.html1293840644editdlrm
Bv9ARM.ch05.html61650644editdlrm
Bv9ARM.ch06.html6676440644editdlrm
Bv9ARM.ch07.html194930644editdlrm
Bv9ARM.ch08.html61400644editdlrm
Bv9ARM.ch09.html1198350644editdlrm
Bv9ARM.ch10.html71510644editdlrm
Bv9ARM.ch11.html452770644editdlrm
Bv9ARM.ch12.html201360644editdlrm
Bv9ARM.ch13.html98990644editdlrm
Bv9ARM.html338550644editdlrm
Bv9ARM.pdf11278330644editdlrm
CHANGES5737570644editdlrm
isc-logo.pdf171890644editdlrm
man.arpaname.html29540644editdlrm
man.ddns-confgen.html93640644editdlrm
man.delv.html238080644editdlrm
man.dig.html422780644editdlrm
man.dnssec-checkds.html51590644editdlrm
man.dnssec-coverage.html111420644editdlrm
man.dnssec-dsfromkey.html120910644editdlrm
man.dnssec-importkey.html94460644editdlrm
man.dnssec-keyfromlabel.html188600644editdlrm
man.dnssec-keygen.html224630644editdlrm
man.dnssec-keymgr.html164680644editdlrm
man.dnssec-revoke.html54490644editdlrm
man.dnssec-settime.html142440644editdlrm
man.dnssec-signzone.html298780644editdlrm
man.dnssec-verify.html73020644editdlrm
man.dnstap-read.html43160644editdlrm
man.genrandom.html39530644editdlrm
man.host.html130520644editdlrm
man.isc-hmac-fixup.html45310644editdlrm
man.lwresd.html120500644editdlrm
man.mdig.html227890644editdlrm
man.named-checkconf.html65860644editdlrm
man.named-checkzone.html197100644editdlrm
man.named-journalprint.html41750644editdlrm
man.named-nzd2nzf.html38180644editdlrm
man.named-rrchecker.html41610644editdlrm
man.named.conf.html748020644editdlrm
man.named.html184450644editdlrm
man.nsec3hash.html39740644editdlrm
man.nslookup.html148920644editdlrm
man.nsupdate.html280580644editdlrm
man.pkcs11-destroy.html53920644editdlrm
man.pkcs11-keygen.html68840644editdlrm
man.pkcs11-list.html52950644editdlrm
man.pkcs11-tokens.html38510644editdlrm
man.rndc-confgen.html112860644editdlrm
man.rndc.conf.html101980644editdlrm
man.rndc.html404090644editdlrm
named.conf.default17050644editdlrm
notes.html1133130644editdlrm
notes.pdf1623470644editdlrm
README284950644editdlrm
Edit: /usr/share/doc/bind/Bv9ARM.ch02.html (7160B)
Chapter 2. BIND Resource Requirements

Chapter 2. BIND Resource Requirements

Hardware requirements

DNS hardware requirements have traditionally been quite modest. For many installations, servers that have been retired from active duty have performed admirably as DNS servers.

However, the DNSSEC features of BIND 9 may be quite CPU-intensive, so organizations that make heavy use of these features may wish to consider larger systems for these applications. BIND 9 is fully multithreaded, allowing full utilization of multiprocessor systems for installations that need it.

CPU Requirements

CPU requirements for BIND 9 range from i386-class machines, for serving static zones without caching, to enterprise-class machines to process many dynamic updates and DNSSEC-signed zones, serving many thousands of queries per second.

Memory Requirements

Server memory must be sufficient to hold both the cache and the zones loaded from disk. The max-cache-size option can limit the amount of memory used by the cache, at the expense of reducing cache hit rates and causing more DNS traffic. If additional section caching (the section called “Additional Section Caching”) is enabled, the max-acache-size 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; 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.

Name Server-Intensive Environment Issues

For name server-intensive environments, there are two configurations that may be used. The first is one 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 need 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.

Supported Operating Systems

ISC BIND 9 compiles and runs on many Unix-like operating systems and on Microsoft Windows Server 2012 R2, 2016 and Windows 10. For an up-to-date list of supported systems, see the PLATFORMS.md file in the top-level directory of the BIND 9 source distribution.

BIND 9.11.36 (Extended Support Version)