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 1 23
rndc-confgen is run on the command line as:
rndc-confgen [-a] [-b keysize] [-c keyfile] [-h] [-k keyname]
[-p port] [-r randomfile] [-s address] [-t chrootdir] [-u user
]
Where
“-a” option is used to configure rndc automatically. This creates a file
rndc.key in /etc which is read by both rndc and named on start-up.
“-b keysize” is used to specify the size of the authentication key in
bits. The value must range between 1 and 512. Default is 128 bits.
“-c keyfile” is used with the -a option to specify an alternate location
for the rndc.key file.
“-h” is used to print a short summary of the options and arguments to
rndc-confgen utility.
“-k keyname” is used to specify the key name of the rndc authentication
key. This must be a valid domain name. Default is rndc-key.
“-p port” is used to specify the command channel port where named
listens for connections from rndc. Default is 953.
“-r random file” is used to specify a source file of random data for
generating the authorization. Default is keyboard input.
“-s address” is used to specify the IP address where named listens for
command channel connections from rndc. Default is the loopback
address 127.0.0.1.
“-t chrootdir” is used with the -a option to specify a directory where
named will run chrooted. An additional copy of the rndc.key will be
written relative to this directory so that it will be found by the chrooted
named.
“-u user” is used with the -a option to set the owner of the generated
rndc.key file. If -t is also specified, the owner of the file in chroot area
will be changed.
NOTE Refer to the rndc-confgen(1) man page for more information.