Compiling BIND9 on CentOS 7

Sean Son linuxmailinglistsemail at
Wed Apr 27 15:52:41 UTC 2016

Thank you for your responses guys.  Here is a n00b question: Because this
new server will be a slave DNS server, do I have to manually copy the zone
files from the current slave DNS server (The CentOS 5.11) one, or does the
new server automatically get the zones from the master DNS server?

Thanks again!

On Wed, Apr 27, 2016 at 11:50 AM, Reindl Harald <h.reindl at>

> Am 27.04.2016 um 17:45 schrieb Matthew Pounsett:
>> rndc is the command line interface to a running BIND server.  (BIND ==
>> berkeley internet name domain, rndc == remote name domain controller (or
>> something to that effect)).  The rndc.conf file must agree with the
>> named.conf file on where BIND's controller interface is (the controls{};
>> clause in named.conf) and what key to use for authentication, if any.
>> For example, named.conf might have something like this:
>> controls {
>>     inet port 953 allow {; } keys {"rndc-key"; };
>> };
>> While your rndc.conf might have:
>> options {
>>     default-key "rndc-key";
>>     default-server;
>>     default-source-address;
>>     default-port 953;
>> };
>> It sounds to me like the named.service file you mention is probably
>> generating a default rndc.conf file if one doesn't already exist
> no it don't and you don't need to setup rndc at all just for
> start/stop/reload named, systemd knows the PID and so can send a SIGHUP,
> works like a charme for many year on nameservers hosting hundrets of zones
> and running with controls { }; since nobody but the maintaining scripts
> have a business mangle with named and after that issue "systemctl reload"
> ExecStart=/usr/sbin/named -4 -f -u named
> ExecReload=/usr/bin/kill -HUP $MAINPID
> ExecStop=/usr/bin/kill -TERM $MAINPID
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the bind-users mailing list