diff options
| -rw-r--r-- | dns/bind94/pkg-message | 17 | ||||
| -rw-r--r-- | dns/bind95/pkg-message | 17 | ||||
| -rw-r--r-- | dns/bind96/pkg-message | 17 |
3 files changed, 24 insertions, 27 deletions
diff --git a/dns/bind94/pkg-message b/dns/bind94/pkg-message index b30fee7881e6..bb713abdd1d3 100644 --- a/dns/bind94/pkg-message +++ b/dns/bind94/pkg-message @@ -5,15 +5,14 @@ * / ___ \| | | | | |___| |\ | | | | | |_| | |\ | * * /_/ \_\_| |_| |_____|_| \_| |_| |___\___/|_| \_| * * * -* BIND 9 requires a good source of randomness to operate. * -* It also requires configuration of rndc, including a * -* "secret" key. If you are running BIND 9 in a chroot * -* environment, make sure that there is a /dev/random device * -* in the chroot. * +* If you are running BIND 9 in a chroot environment, make * +* sure that there is a /dev/random device in the chroot. * * * -* The easiest, and most secure way to configure rndc is * -* to run 'rndc-confgen -a' which will generate the proper * -* conf file, with a new random key, and appropriate file * -* permissions. * +* 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. * * * ************************************************************************* diff --git a/dns/bind95/pkg-message b/dns/bind95/pkg-message index b30fee7881e6..bb713abdd1d3 100644 --- a/dns/bind95/pkg-message +++ b/dns/bind95/pkg-message @@ -5,15 +5,14 @@ * / ___ \| | | | | |___| |\ | | | | | |_| | |\ | * * /_/ \_\_| |_| |_____|_| \_| |_| |___\___/|_| \_| * * * -* BIND 9 requires a good source of randomness to operate. * -* It also requires configuration of rndc, including a * -* "secret" key. If you are running BIND 9 in a chroot * -* environment, make sure that there is a /dev/random device * -* in the chroot. * +* If you are running BIND 9 in a chroot environment, make * +* sure that there is a /dev/random device in the chroot. * * * -* The easiest, and most secure way to configure rndc is * -* to run 'rndc-confgen -a' which will generate the proper * -* conf file, with a new random key, and appropriate file * -* permissions. * +* 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. * * * ************************************************************************* diff --git a/dns/bind96/pkg-message b/dns/bind96/pkg-message index b30fee7881e6..bb713abdd1d3 100644 --- a/dns/bind96/pkg-message +++ b/dns/bind96/pkg-message @@ -5,15 +5,14 @@ * / ___ \| | | | | |___| |\ | | | | | |_| | |\ | * * /_/ \_\_| |_| |_____|_| \_| |_| |___\___/|_| \_| * * * -* BIND 9 requires a good source of randomness to operate. * -* It also requires configuration of rndc, including a * -* "secret" key. If you are running BIND 9 in a chroot * -* environment, make sure that there is a /dev/random device * -* in the chroot. * +* If you are running BIND 9 in a chroot environment, make * +* sure that there is a /dev/random device in the chroot. * * * -* The easiest, and most secure way to configure rndc is * -* to run 'rndc-confgen -a' which will generate the proper * -* conf file, with a new random key, and appropriate file * -* permissions. * +* 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. * * * ************************************************************************* |