BIND 9.2.0 Release Notes for HP-UX 11i v1

Installation Information
Compatibility with Previous Versions of BIND
Chapter 226
• Outgoing zone transfers now use the "many-answers" format by default.This
format is not understood by certain old versions of BIND 4.9.7.This problem
can be resolved by using the option "transfer-format one-answer;", but
HP recommends upgrading the slave servers.
BIND 8.1.2 Compatibility
This section discusses the BIND 9.2.0-BIND 8.1.2 compatibility.
• Configuration file compatibility
— BIND 9.2.0 supports most of the options in named.conf file of BIND
8.1.2. BIND 9.2.0 issues a log message if the specified option is not
implemented. It also logs the information if the default value is changed.
— In BIND 9.2.0, named refuses to start if it detects an error in
named.conf. Earlier versions would start despite errors, causing the
server to run with a partial configuration.
— In BIND 9.2.0, the "logging" statement only takes effect after the entire
named.conf file has been read. In BIND 8.1.2, the new logging
configuration took effect immediately after a "logging" statement was
read.
— The source address and port for notify messages and refresh queries is now
controlled by "notify-source" and "transfer-source",
respectively, as against query-source in BIND 8.1.2.
• Zone file compatibility
— BIND 9.2.0 does not support serial numbers of SOA record with an
embedded period, like "3.002". Serial numbers should be integers.
— TXT records with unbalanced quotes, like ‘host TXT "foo’, were not
treated as errors in previous versions of BIND. If the zone files contain
such records, then error messages like "unexpected end of file"will be
displayed because BIND 9.2.0 will interpret everything up to the next
quote character as a literal string.
— Previous versions of BIND accept RRs containing line breaks that are not
properly quoted with parentheses. This is not legal master file syntax and
will be treated as an error by BIND 9.2.0.