"/dev/null" <(E-Mail Removed)> writes:
> Bind looks like it will do all we need, but we've heard a number of security
> concerns with bind.
Ancient history. There may have been one security-related upgrade in the
last year or so, with Bind, at least bind-9.x which is what counts, anyway.
> Any recommendations on something that can handle a large scale (1,000+ zone
> files) deployment that is also fairly secure?
Bind will do the first part; chances are other things will. The latter is
up to you - there's a vast arsenal of things you can do to make a service
more secure:
a) specific user (-u)
b) chroot jail (-t)
c) CFLAGS="-fstack-protector" (and other random optimization things that
are unlikely to appear in a standard packaged version)
d) a good stateful iptables firewall allowing TCP access only to known
secondary NSes
d) GRSecurity kernel patch to lock-down behaviour within chroot and stop it
from making outgoing client socket connections at all
e) check for updates EVERY DAMN DAY.
f) run the whole thing with libsafe or electricfence
g) IDS and nIDS
h) hide the version-string
i) restrict zone-xfers to secondary NSen only
j) good backup strategy
See. Plenty you can do, that makes the choice of daemon pretty much
irrelevant.
~Tim
--
18:37:08 up 114 days, 3:17, 0 users, load average: 0.11, 0.07, 0.01
(E-Mail Removed) |The light of the world keeps shining,
http://spodzone.org.uk/cesspit/ |Bright in the primal glow