diff options
| author | Hugo Landau <hlandau@devever.net> | 2014-10-16 16:52:17 +0100 |
|---|---|---|
| committer | Natanael Copa <ncopa@alpinelinux.org> | 2014-10-16 19:05:10 +0000 |
| commit | 10f550c471adec9b04d66ceb81eddf88f95c7598 (patch) | |
| tree | 80cdcda501f3aff43b71636773af7c54775d86a4 /main/bind/named.initd | |
| parent | cddbf13cfdf463498f1619cb11a6e665650b3563 (diff) | |
| download | aports-10f550c471adec9b04d66ceb81eddf88f95c7598.tar.bz2 aports-10f550c471adec9b04d66ceb81eddf88f95c7598.tar.xz | |
bind: Modify default config to be more secure
By default BIND will happily serve as both an authoritative nameserver
and recursive resolver, but this is no longer a recommended or desirable
configuration. The previous default configuration did not draw attention
to this fact and the issues involved.
Users are now made to rename one of two sample configuration files,
named.conf.authoritative or named.conf.recursive. Comments inside either
file advise DNS administrators of the most prevalent security issues.
This ensures that users setting up an authoritative nameserver do not
unwittingly also operate a resolver. In the previous default
configuration, BIND would happily perform recursive resolution for
localhost, which means that the local machine may receive
non-authoritative data from what is supposed to be an authoritative
nameserver.
Both default configurations disable zone transfers by default, as BIND
defaults to enabling them for any host (!).
Diffstat (limited to 'main/bind/named.initd')
| -rw-r--r-- | main/bind/named.initd | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/main/bind/named.initd b/main/bind/named.initd index 812dfa90c..a724848c1 100644 --- a/main/bind/named.initd +++ b/main/bind/named.initd @@ -21,7 +21,7 @@ checkconfig() { ebegin "Checking named configuration" if [ ! -f "${NAMED_CONF}" ] ; then - eerror "No ${NAMED_CONF} file exists!" + eerror "No ${NAMED_CONF} file exists! See the examples in /etc/bind." return 1 fi |