The basics are fine. BIND just doesn't load newly added forwarded zones,
period. It also kind of lies in the output:
Sep 20 17:57:48 host01 named: reloading configuration succeeded
Sep 20 17:57:48 host01 named: any newly configured zones are now
...except they're not. Thus far I think the only condition I've actually
seen BIND load new zones without a restart after being added to named.conf
is if it's not already authoritative for a lower level part of a domain and
you're adding an authoritative zone.
Even adding another master zone that is higher up in the hierarchy will not
load until a full restart I've found (meaning you have "domain.com"
configured as a master zone and add "subdomain.domain.com" as a master zone
On Tue, Sep 20, 2016 at 5:56 PM, Benny Pedersen <m...@junc.eu> wrote:
> On 2016-09-21 02:40, Frank Even wrote:
>> Is there a way to add forwarders for specific zones without a restart?
>> Everything I've read seems to indicate an "rndc reconfig" or an "rndc
>> reload" should take care of this, but they do not. I add forwarders
>> to "named.conf" and neither will load the new forwarded zone until I
>> do a full daemon restart.
> rndc reload
> after edit named.conf
> remember to named-checkconf first
> is your rndc key pair or acl setup ?
> what are logged ?
> rndc reload zone ?
> type rndc to see valid commands
> Please visit https://lists.isc.org/mailman/listinfo/bind-users to
> unsubscribe from this list
> bind-users mailing list
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing list