BIND 9.2.0 Release Notes
Table Of Contents
- 1 New Features
- BIND 8.1.2 Features Supported on HP-UX 11.0
- New BIND 9.2.0 Features
- Incremental Zone Transfer
- DNS Security
- Dynamic DNS Update
- TSIG-Based Security
- Lightweight Resolver Library and Daemon
- Improved Logging Mechanism
- Extended Configuration Syntax and Options
- New Options in options Statement
- New Option in “server” Statement
- New Options in “zone” Statement
- named-checkconf
- named-checkzone
- rndc
- Generating rndc.conf File
- New Command Line Options
- Changed Features
- Unsupported Features
- 2 Installation Information
- 3 Documentation
- 4 Known Problems, Limitation and Defect Fixes
New Features
Unsupported Features
Chapter 132
• rfc2308-type1 yes_or_no
If this option is set to yes, the server sends NS records along with
the SOA record for negative answers. The default is no.
• min-roots
This option specifies the minimum number of root servers that is
required for a request for the root servers to be accepted. Default is 2.
• unix
This option in controls statement is not supported in BIND 9.2.0.
Options not Supported in “view” and “zone”
Statements
The following lists the options in “view” and “zone” statements that
are not supported in BIND 9.2.0:
• ixfr-base
This option was used in BIND 8.1.2 to specify the name of the
transaction log (journal) file for dynamic update and IXFR. BIND
9.2.0 ignores the option and constructs the name of the journal file by
appending .jnl to the name of the zone file.
• pubkey
This option was used in BIND 8.1.2 to specify a public zone key for
verification of signatures in DNSSEC signed zones when they are
loaded from disk. BIND 9.2.0 does not verify signatures on loading
and ignores the option.
• max-ixfr-log-size
This option was used in BIND 8.1.2 to set limits on server’s resource
consumption. This option is obsolete; it is accepted and ignored for
BIND 8.1.2 compatibility.