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
New BIND 9.2.0 Features
Chapter 122
NOTE Refer to the rndc(1) man page for more information.
A sample rndc.conf file is distributed with this release of BIND. This
file can be generated automatically by the rndc-confgen utility, which is
distributed with BIND 9.2.0. For more information on rndc-confgen,
read the rndc-confgen section above.
rndc has its own configuration file /etc/rndc.conf. A sample minimal
configuration file looks like:
key rndckey {
algorithm "hmac-md5";
secret "IbtRYdcP8k2mVtel6aYfbQ==";
};
options {
default-server localhost;
default-key rndckey;
};
This file, if installed as /etc/rndc.conf, would allow the $ rndc
reload command to connect to 127.0.0.1 port 953 and cause the
nameserver to reload if a nameserver on the local machine is running
with the following controls statements:
controls {
inet 127.0.0.1 allow { 127.0.0.1; } keys { rndckey;
};
};
and also if the named.conf has an identical key statement for rndckey.
NOTE Refer to the rndc.conf(4) man page for more information on the rndc
configuration file.
Generating rndc.conf File
rndc-confgen can be used to generate rndc.conf, the configuration file
for rndc. Alternatively, it can also be run with the -a option to set up a
rndc.key file thus avoiding the need for a rndc.conf file and a control
statement.