If you are looking for a recursive resolver, I would highly recommend unbound.
If you are looking for an authoritative DNS server, I would highly recommend NSD.
I run both and find both extremely easy to configure and maintain.
Both are available from the EPEL repositories.
I stopped using bind years ago and never looked back.
On 04/11/2017 10:05 AM, Nicolas Kovacs wrote:
Hi,
I just installed CentOS 7 on a public server. I'd like to setup BIND as a primary DNS server for a few domains.
Until now, all my public machines were running Slackware Linux, and setting up BIND on a Slackware machine is relatively easy. In its out of the box configuration, it has a bone-headed caching nameserver role, which is quite easy to expand to a primary nameserver. Here's my documentation. It's in French, but the *nix bits are universal.
http://blog.microlinux.fr/bind-slackware/
On my server running CentOS, I notice things are more complicated in the default configuration. The problem here is not so much documentation, but more like the wealth of information on the subject of BIND on CentOS, with often contradicting information.
Is there a *reliable* more or less quick & dirty tutorial on how to get BIND up and running as a primary public nameserver, with the default configuration as a starting point? Think "recipe for pasta" and not "degree in food chemistry". :o)
Cheers,
Niki