From: Andreas Gustafsson Date: Wed, 27 Jun 2001 17:46:32 +0000 (+0000) Subject: clarified that the transfer-format option is used on the master, not the slave X-Git-Tag: v9.1.3rc3~3 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=46484167fe37146eef9deafa42dd4aaf2c10639e;p=thirdparty%2Fbind9.git clarified that the transfer-format option is used on the master, not the slave --- diff --git a/doc/arm/Bv9ARM-book.xml b/doc/arm/Bv9ARM-book.xml index fbb01b14217..0b458424c72 100644 --- a/doc/arm/Bv9ARM-book.xml +++ b/doc/arm/Bv9ARM-book.xml @@ -2,7 +2,7 @@ - + @@ -3155,12 +3155,25 @@ per second but may become configurable in a future release. transfer-format -The server supports two zone transfer methods. one-answer uses -one DNS message per resource record transferred. many-answers packs -as many resource records as possible into a message. many-answers is -more efficient, but is only known to be understood by BIND 9, BIND -8.x and patched versions of BIND 4.9.5. The default is many-answers. transfer-format may -be overridden on a per-server basis by using the server statement. + + + +Zone transfers can be sent using two different formats, +one-answer and many-answers. +The transfer-format option is used +on the master server to determine which format it sends. +one-answer uses one DNS message per +resource record transferred. +many-answers packs as many resource records as +possible into a message. many-answers is more +efficient, but is only supported by relatively new slave servers, +such as BIND 9, BIND 8.x and patched +versions of BIND 4.9.5. The default is +many-answers. transfer-format +may be overridden on a per-server basis by using the +server statement. + + transfers-in