
Migrating from Solaris 9 Enterprise Edition on Sun Fire V440 with BIND 8.3.3
to Solaris 10 Enterprise Edition on Dell PowerEdge R900 with BIND 9.3.5-P1
9
o Line breaks not within parentheses will cause a
syntax error.
o BIND 9 now deprecates $$ in favor of \$.
Interoperability impact of new protocol features
• EDNS0. Support for EDNS0 is new in BIND 9. BIND 9
assumes that servers not supporting EDNS0 will return an
error. However, some servers ignore EDNS0 requests. In
these cases, name resolution may be slow, or even fail.
• Many-answers now the default for zone transfers. As
we noted previously, this new default setting may cause
problems with older BIND 4 servers. If you cannot upgrade
these servers, you will need to specify using one-answer for
the transfer-format clause on any such servers.
Unrestricted character set
• BIND 9 implements the full 8-bit character set and does not
restrict its use. However, versions of BIND from 9.3.0 on do
implement the check-names option, allowing you to ensure
that your labels conform to RFC252
.
No information leakage between zones
• In BIND 8, the name server (NS) resource records from a
child could “leak” to the parent, modifying the parent
configuration. Some BIND 8 installations use this behavior
to avoid adding glue NS records to the parent. (Glue records
are records that a zone stores for the name servers in its
subdomains.) BIND 9 complies with RFC1035
, so you may
need to add the glue records to your configuration.
umask not modified
• BIND 8 unconditionally set the file permission mask
(umask) to 022, which caused files to have permissions of
644 (rw-r--r--) and directories to have permissions of 755
(rwxr-xr-x). In contrast, BIND 9 inherits the file permission
of its parent process. If this inheritance causes you any
problems, you can set the umask from the command line by
typing the umask command.
Kommentare zu diesen Handbüchern