pulled up recent documentation changes

diff --git a/README b/README
index 70feb24bd503c04b808da8fad11c1decf84370e7..5a641586d9fa977d264159886a403695b8bc8bcd 100644 (file)
--- a/README
+++ b/README
@@ -134,7 +134,10 @@ BIND 9.1.3rc1
 
                --with-libtool does not work on AIX.
 
-
+       A bug in the Windows 2000 DNS server can cause zone transfers
+       from a BIND 9 server to a W2K server to fail.  For details,
+       see the "Zone Transfers" section in doc/misc/migration.
+ 
        For a detailed list of user-visible changes from
        previous releases, see the CHANGES file.
 

diff --git a/doc/misc/migration b/doc/misc/migration
index 5009b6617e86fa4b70525e17d9d49540e8fcfe0f..f5bebf83acddfe3dfd2a3304d1833df2490232c1 100644 (file)
--- a/doc/misc/migration
+++ b/doc/misc/migration
@@ -164,7 +164,7 @@ transmitted as a single UDP datagram which is subject to fragmentation
 at the IP level.  If a firewall incorrectly drops IP fragments, it can
 cause resolution to slow down dramatically or fail.
 
-3.2. Zone transfers
+3.2. Zone Transfers
 
 Outgoing zone transfers now use the "many-answers" format by default.
 This format is not understood by certain old versions of BIND 4.  
@@ -172,10 +172,12 @@ You can work around this problem using the option "transfer-format
 one-answer;", but since these old versions all have known security
 problems, the correct fix is to upgrade the slave servers.
 
-Some BIND 9 users have reported interoperability problems with zone
-transfers to Microsoft DNS servers that were solved by specifying
-"transfer-format one-answer;", but we are still lacking detailed
-information about this issue.
+Zone transfers to Windows 2000 DNS servers sometimes fail due to a bug
+in the Windows 2000 DNS server where DNS messages larger than 16K are
+not handled properly.  There will be a hot fix available from
+Microsoft to address this issue.  In the meantime, the problem can
+be worked around by setting "transfer-format one-answer;".
+[As of May 4 2001 the hotfix was still being prepared]
 
 
 4. Unrestricted Character Set
@@ -236,4 +238,4 @@ directing queries for a given domain to a particular set of name
 servers.
 
 
-$Id: migration,v 1.17.2.8 2001/05/08 21:46:24 gson Exp $
+$Id: migration,v 1.17.2.9 2001/05/19 01:34:23 gson Exp $

diff --git a/doc/misc/migration-4to9 b/doc/misc/migration-4to9
index 96eeb1f0e5890a703edd6e43bda4aea5e9803697..349687b4a414d31ce8b1eb078068a73b58d1f40d 100644 (file)
--- a/doc/misc/migration-4to9
+++ b/doc/misc/migration-4to9
@@ -46,3 +46,9 @@ ignoring the DNSSEC records (SIG, NXT, KEY) that BIND 4 did not support.
 BIND 9 is less tolerant of errors in master files, so check your logs and
 fix any errors reported.  The named-checkzone program can also be to check
 master files.
+
+Outgoing zone transfers now use the "many-answers" format by default.
+This format is not understood by certain old versions of BIND 4.  
+You can work around this problem using the option "transfer-format
+one-answer;", but since these old versions all have known security
+problems, the correct fix is to upgrade the slave servers.