From: João Damas <joao@isc.org>
Date: Fri, 21 Sep 2007 10:47:34 +0000 (+0000)
Subject: Added Mark's text on the usage of memory by BIND 9 (multiple instances of the zone... 
X-Git-Tag: v9.3.5b1~34^2~4
X-Git-Url: http://git.ipfire.org/gitweb/?a=commitdiff_plain;h=49c8cf9ee9947b7aaa6e93631033a31508ae6a85;p=thirdparty%2Fbind9.git

Added Mark's text on the usage of memory by BIND 9 (multiple instances of the zone in memory)
---

diff --git a/FAQ.xml b/FAQ.xml
index 05393919e63..aae0d142ba3 100644
--- a/FAQ.xml
+++ b/FAQ.xml
@@ -17,7 +17,7 @@
  - PERFORMANCE OF THIS SOFTWARE.
 -->
 
-<!-- $Id: FAQ.xml,v 1.24 2007/09/05 06:47:33 marka Exp $ -->
+<!-- $Id: FAQ.xml,v 1.25 2007/09/21 10:47:34 joao Exp $ -->
 
 <article class="faq">
   <title>Frequently Asked Questions about BIND 9</title>
@@ -620,6 +620,49 @@ zone "list.dsbl.org" {
       </answer>
     </qandaentry>
     
+        <qandaentry>
+          <question>
+    	<para>
+    	  Can you help me understand how BIND 9 uses memory to store DNS zones?
+    	</para>
+    	<para>
+    	  Some times it seems to take several times the amount of memory it needs to store the zone.
+    	</para>
+          </question>
+          <answer>
+            <para>
+          	When reloading a zone named my have multiple copies of the
+          	zone in memory at one time.  The zone it is serving and the
+          	one it is loading.  If reloads are ultra fast it can have more
+          	still.
+          	</para>
+            <para>
+          	e.g.
+          		Ones that are transferring out, the one that it is serving
+          	and the one that is loading.
+        	</para>
+          <para>
+          	BIND 8 destroyed the zone before loading and also killed
+          	off outgoing transfers of the zone.
+        	</para>
+          <para>
+          	The new strategy allows slaves to get copies of the new
+          	zone regardless of how often the master is loaded compared
+          	to the transfer time.  The slave might skip some intermediate
+          	versions but the transfers will complete and it will
+          	keep reasonably in sync with the master.
+        	</para>
+          <para>
+          	The new strategy also allows the master to recover from
+          	syntax and other errors in the master file as it still has
+          	an in-core copy of the old contents.
+        	</para>
+          </answer>
+        </qandaentry>
+    
+    
+    
+    
     </qandadiv> <!-- Configuration and Setup Questions -->
     
     <qandadiv><title>General Questions</title>