migration revision 69b641bf31d95fd79a50dcea2cdb0fcb23fe22c6
d6fa26d0adaec6c910115be34fe7a5a5f402c14fMark AndrewsCopyright (C) 2000 Internet Software Consortium.
0c91911b4d1e872b87eaf6431ed47fe24d18dd43Mark AndrewsSee COPYRIGHT in the source root or http://www.isc.org/copyright for terms.
663272199096ed57917f2bfb1d748a0a622b7b24Tinderbox User BIND 8 to BIND 9 Migration Notes
5347c0fcb04eaea19d9f39795646239f487c6207Tinderbox UserBIND 9 is designed to be mostly upwards compatible with BIND 8, but
5347c0fcb04eaea19d9f39795646239f487c6207Tinderbox Userthere is still a number of caveats you should be aware of when
0c91911b4d1e872b87eaf6431ed47fe24d18dd43Mark Andrewsupgrading an existing BIND 8 installation to use BIND 9.
0c91911b4d1e872b87eaf6431ed47fe24d18dd43Mark Andrews1. Configuration File Compatibility
fd2597f75693a2279fdf588bd40dfe2407c42028Tinderbox User1.1. Unimplemented Options and Changed Defaults
fd2597f75693a2279fdf588bd40dfe2407c42028Tinderbox UserBIND 9.0.0 supports most, but not all but not of the named.conf
0c91911b4d1e872b87eaf6431ed47fe24d18dd43Mark Andrewsoptions of BIND 8. Unimplemented options include those for selective
7911e6f9de303bca5a3d8b34f4330c8f7cecffaeTinderbox User(per-domain) forwarding, sortlists, statistics, and process limits;
7911e6f9de303bca5a3d8b34f4330c8f7cecffaeTinderbox Userfor a complete list, see doc/misc/options. We plan to implement most
7911e6f9de303bca5a3d8b34f4330c8f7cecffaeTinderbox Userof these in in BIND 9.1.
7911e6f9de303bca5a3d8b34f4330c8f7cecffaeTinderbox UserIf your named.conf file uses an unimplemented option, named will log a
7911e6f9de303bca5a3d8b34f4330c8f7cecffaeTinderbox Userwarning message. A message is also logged about each option whose
0c91911b4d1e872b87eaf6431ed47fe24d18dd43Mark Andrewsdefault has changed unless the option is set explicitly in named.conf.
0c91911b4d1e872b87eaf6431ed47fe24d18dd43Mark AndrewsThe set of logging categories in BIND 9 is different from that
7911e6f9de303bca5a3d8b34f4330c8f7cecffaeTinderbox Userin BIND 8. If you have customized your logging on a per-category
7911e6f9de303bca5a3d8b34f4330c8f7cecffaeTinderbox Userbasis, you need to modify your logging statement to use the
7911e6f9de303bca5a3d8b34f4330c8f7cecffaeTinderbox Usernew categories.
0c91911b4d1e872b87eaf6431ed47fe24d18dd43Mark AndrewsAnother difference is that the "logging" statement only takes effect
7911e6f9de303bca5a3d8b34f4330c8f7cecffaeTinderbox Userafter the entire named.conf file has been read. This means that when
7911e6f9de303bca5a3d8b34f4330c8f7cecffaeTinderbox Userthe server starts up, any messages about errors in the configuration
7911e6f9de303bca5a3d8b34f4330c8f7cecffaeTinderbox Userfile are always logged to the default destination (syslog) when the
7911e6f9de303bca5a3d8b34f4330c8f7cecffaeTinderbox Userserver first starts up, regardless of the contents of the "logging"
7911e6f9de303bca5a3d8b34f4330c8f7cecffaeTinderbox Userstatement. In BIND 8, the new logging configuration took effect
7911e6f9de303bca5a3d8b34f4330c8f7cecffaeTinderbox Userimmediately after the "logging" statement was read.
7911e6f9de303bca5a3d8b34f4330c8f7cecffaeTinderbox User2. Zone File Compatibility
7911e6f9de303bca5a3d8b34f4330c8f7cecffaeTinderbox User2.1. Strict RFC1035 Interpretation of TTLs in Zone Files
7911e6f9de303bca5a3d8b34f4330c8f7cecffaeTinderbox UserBIND 8 allowed you to omit all TTLs from a zone file, and used the
7911e6f9de303bca5a3d8b34f4330c8f7cecffaeTinderbox Uservalue of the SOA MINTTL field as a default for missing TTL values.
7911e6f9de303bca5a3d8b34f4330c8f7cecffaeTinderbox UserBIND 9 enforces strict compliance with the RFC1035 and RFC2308 TTL
7911e6f9de303bca5a3d8b34f4330c8f7cecffaeTinderbox Userrules. The default TTL is the value specified with the $TTL
7911e6f9de303bca5a3d8b34f4330c8f7cecffaeTinderbox Userdirective, or the previous explicit TTL if there is no $TTL directive.
7911e6f9de303bca5a3d8b34f4330c8f7cecffaeTinderbox UserIf there is no $TTL directive and the first RR in the file does not
7911e6f9de303bca5a3d8b34f4330c8f7cecffaeTinderbox Userhave an explicit TTL field, the error message "no TTL specified" is
7911e6f9de303bca5a3d8b34f4330c8f7cecffaeTinderbox Userlogged and loading the zone file fails.
7911e6f9de303bca5a3d8b34f4330c8f7cecffaeTinderbox UserTo avoid problems, use a $TTL directive in each zone file.
7911e6f9de303bca5a3d8b34f4330c8f7cecffaeTinderbox User2.2. Periods in SOA Serial Numbers Deprecated
7911e6f9de303bca5a3d8b34f4330c8f7cecffaeTinderbox UserSome versions of BIND allow SOA serial numbers with an embedded
7911e6f9de303bca5a3d8b34f4330c8f7cecffaeTinderbox Userperiod, like "3.002", and convert them into integers in a rather
7911e6f9de303bca5a3d8b34f4330c8f7cecffaeTinderbox Userunintuitive way. This feature is not supported by BIND 9; serial
fd2597f75693a2279fdf588bd40dfe2407c42028Tinderbox Usernumbers must be integers.
914ed533b846624c8ba5e7a72a5e8e50c9018b0aTinderbox User2.3. Handling of Unbalanced Quotes
914ed533b846624c8ba5e7a72a5e8e50c9018b0aTinderbox UserTXT records with unbalanced quotes, like 'host TXT "foo', were not
914ed533b846624c8ba5e7a72a5e8e50c9018b0aTinderbox Usertreated as errors in some versions of BIND. If your zone files
914ed533b846624c8ba5e7a72a5e8e50c9018b0aTinderbox Usercontain such records, you will get potentially confusing error
914ed533b846624c8ba5e7a72a5e8e50c9018b0aTinderbox Usermessages like "unexpected end of file" because BIND 9 will interpret
914ed533b846624c8ba5e7a72a5e8e50c9018b0aTinderbox Usereverything up to the next quote character as a literal string.
914ed533b846624c8ba5e7a72a5e8e50c9018b0aTinderbox User3. Interoperability Impact of New Protocol Features
914ed533b846624c8ba5e7a72a5e8e50c9018b0aTinderbox UserBIND 9 uses EDNS0 (RFC2671) to advertise its receive buffer size. It
914ed533b846624c8ba5e7a72a5e8e50c9018b0aTinderbox Useralso sets the AD bit in queries to indicate that it wishes to receive
914ed533b846624c8ba5e7a72a5e8e50c9018b0aTinderbox UserDNSSEC responses (this usage of the AD bit is not yet standard, but
914ed533b846624c8ba5e7a72a5e8e50c9018b0aTinderbox Userhopefully it will be soon).
7911e6f9de303bca5a3d8b34f4330c8f7cecffaeTinderbox UserMost older servers that do not support EDNS0 and/or DNSSEC, including
7911e6f9de303bca5a3d8b34f4330c8f7cecffaeTinderbox Userall known versions of BIND, will send a FORMERR or NOTIMP response to
7911e6f9de303bca5a3d8b34f4330c8f7cecffaeTinderbox Userthese queries. When this happens, BIND 9 will automatically retry the
fd2597f75693a2279fdf588bd40dfe2407c42028Tinderbox Userquery without EDNS0 and AD.
7911e6f9de303bca5a3d8b34f4330c8f7cecffaeTinderbox UserUnfortunately, there exists at least one non-BIND name server
7911e6f9de303bca5a3d8b34f4330c8f7cecffaeTinderbox Userimplementation that silently ignores these queries instead of sending
0c91911b4d1e872b87eaf6431ed47fe24d18dd43Mark Andrewsan error response. Resolving names in zones where all or most
914ed533b846624c8ba5e7a72a5e8e50c9018b0aTinderbox Userauthoritative servers use this server will be very slow or fail
7911e6f9de303bca5a3d8b34f4330c8f7cecffaeTinderbox Usercompletely. We have contacted the manufacturer of the name server in
e62b9c9ce6413fb183c8116381e75dcd07ca5517Tinderbox Usercase and are trying to resolve the issue with them.
e62b9c9ce6413fb183c8116381e75dcd07ca5517Tinderbox User$Id: migration,v 1.4 2000/07/27 23:48:49 tale Exp $