rndc reconfig does not work

[Phil Mayers]

On 12/29/2012 11:09 AM, Carsten Strotmann wrote:

> For some configuration changes (for example change of IP addresses to
> listen on, change of fundamental operations, new log-file entries) the
> BIND nameserver requires a full restart, esp. if BIND is running as an
> non-privileged user (not "root"), as some configuration steps require
> root access (like opening network sockets on port 53).

Just to note, this specific change (new IPs) can be done with just 
reconfig on some platforms (e.g. Linux) as bind uses underlying OS 
mechanisms to listen on ports < 1024 as an unprivileged user.

But the general point stands that "reconfig" only does a subset of tasks.