a3263f6a34
to root server addresses, and a fix for the vulnerability mentioned here: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-0122 Users of BIND 9.3.x are strongly encouraged to upgrade to this version. Also, the 9.3.x branch is now in maintenance-only mode. Users are encouraged to investigate BIND 9.4.x or perhaps 9.5.x. http://www.isc.org/index.pl?/sw/bind/versions_and_support.php
18 lines
939 B
Text
18 lines
939 B
Text
*************************************************************************
|
|
* _ _____ _____ _____ _ _ _____ ___ ___ _ _ *
|
|
* / \|_ _|_ _| ____| \ | |_ _|_ _/ _ \| \ | | *
|
|
* / _ \ | | | | | _| | \| | | | | | | | | \| | *
|
|
* / ___ \| | | | | |___| |\ | | | | | |_| | |\ | *
|
|
* /_/ \_\_| |_| |_____|_| \_| |_| |___\___/|_| \_| *
|
|
* *
|
|
* If you are running BIND 9 in a chroot environment, make *
|
|
* sure that there is a /dev/random device in the chroot. *
|
|
* *
|
|
* BIND 9 also requires configuration of rndc, including a *
|
|
* "secret" key. The easiest, and most secure way to configure *
|
|
* rndc is to run 'rndc-confgen -a' to generate the proper conf *
|
|
* file, with a new random key, and appropriate file permissions. *
|
|
* *
|
|
* The /etc/rc.d/named script in the base will do both for you. *
|
|
* *
|
|
*************************************************************************
|