diff options
author | Jakob Schlyter <jakob@cvs.openbsd.org> | 2003-11-18 14:14:09 +0000 |
---|---|---|
committer | Jakob Schlyter <jakob@cvs.openbsd.org> | 2003-11-18 14:14:09 +0000 |
commit | a3684c7a7fae3c0a0ad3d9641d29affc2b8aed03 (patch) | |
tree | bd1bf1ed050890b02d624a1468c39c2822f5ce45 /usr.sbin/bind/doc/misc | |
parent | 2177e8980dbcbd0b8006b290bb9de8e8565df3ba (diff) |
update to BIND v9.2.3. ok todd@
Diffstat (limited to 'usr.sbin/bind/doc/misc')
-rw-r--r-- | usr.sbin/bind/doc/misc/dnssec | 2 | ||||
-rw-r--r-- | usr.sbin/bind/doc/misc/migration | 31 |
2 files changed, 16 insertions, 17 deletions
diff --git a/usr.sbin/bind/doc/misc/dnssec b/usr.sbin/bind/doc/misc/dnssec index d05b7e5ed65..1800d027ea6 100644 --- a/usr.sbin/bind/doc/misc/dnssec +++ b/usr.sbin/bind/doc/misc/dnssec @@ -89,4 +89,4 @@ future as we consider them inferior to the use of TSIG or SIG(0) to ensure the integrity of zone transfers. -$ISC: dnssec,v 1.14.2.3.4.2 2003/02/17 07:05:07 marka Exp $ +$ISC: dnssec,v 1.14.2.6 2003/03/06 04:38:20 marka Exp $ diff --git a/usr.sbin/bind/doc/misc/migration b/usr.sbin/bind/doc/misc/migration index 916cde19b88..dfe991d599c 100644 --- a/usr.sbin/bind/doc/misc/migration +++ b/usr.sbin/bind/doc/misc/migration @@ -1,4 +1,4 @@ -Copyright (C) 2000, 2001 Internet Software Consortium. +Copyright (C) 2000, 2001, 2003 Internet Software Consortium. See COPYRIGHT in the source root or http://isc.org/copyright.html for terms. BIND 8 to BIND 9 Migration Notes @@ -38,7 +38,7 @@ do cause the zone not to load. 1.3. Logging The set of logging categories in BIND 9 is different from that -in BIND 8. If you have customized your logging on a per-category +in BIND 8. If you have customised your logging on a per-category basis, you need to modify your logging statement to use the new categories. @@ -50,7 +50,7 @@ server first starts up, regardless of the contents of the "logging" statement. In BIND 8, the new logging configuration took effect immediately after the "logging" statement was read. -1.4. Notify messages and Refesh queries +1.4. Notify messages and Refresh queries The source address and port for these is now controlled by "notify-source" and "transfer-source", respectively, rather that @@ -78,10 +78,10 @@ and use the value of the SOA MINTTL field as a default for missing TTL values. BIND 9.0 and 9.1 completely refused to load such files. BIND 9.2 -emulates the nonstandard BIND 4/8 SOA MINTTL behavior and loads the +emulates the nonstandard BIND 4/8 SOA MINTTL behaviour and loads the files anyway (provided the SOA is the first record in the file), but will issue the warning message "no TTL specified; using SOA MINTTL -instad". +instead". To avoid problems, we recommend that you use a $TTL directive in each zone file. @@ -125,7 +125,7 @@ name is deprecated. Use \$ instead. BIND 9 uses EDNS0 (RFC2671) to advertise its receive buffer size. It also sets an EDNS flag bit in queries to indicate that it wishes to -receive DNSSEC responses; this flag bit usage is not yet standardized, +receive DNSSEC responses; this flag bit usage is not yet standardised, but we hope it will be. Most older servers that do not support EDNS0, including prior versions @@ -154,13 +154,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. -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] - +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. Obtain the latest service pack for +Windows 2000 from Microsoft to address this issue. In the meantime, +the problem can be worked around by setting "transfer-format one-answer;". +http://support.microsoft.com/default.aspx?scid=kb;en-us;297936 4. Unrestricted Character Set @@ -219,11 +218,11 @@ records and would "leak" the child's NS records into the parent, effectively causing the parent zone to be silently modified: responses and zone transfers from the parent contained the child's NS records rather than the glue configured into the parent (if any). In the case -of children of type "stub", this behavior was documented as a feature, +of children of type "stub", this behaviour was documented as a feature, allowing the glue NS records to be omitted from the parent configuration. -Sites that were relying on this BIND 8 behavior need to add any +Sites that were relying on this BIND 8 behaviour need to add any omitted glue NS records, and any necessary glue A records, to the parent zone. @@ -243,4 +242,4 @@ necessary, the umask should be set explicitly in the script used to start the named process. -$ISC: migration,v 1.37.2.1 2001/09/21 17:49:58 gson Exp $ +$ISC: migration,v 1.37.2.4 2003/09/02 02:20:15 marka Exp $ |