also-notify and nsupdate doesnt work
Darcy Kevin (FCA)
kevin.darcy at fcagroup.com
Mon May 2 21:19:32 UTC 2016
Right. also-notify (on a master) versus allow-notify (on a slave). Different use cases.
From: bind-users-bounces at lists.isc.org [mailto:bind-users-bounces at lists.isc.org] On Behalf Of Barry Margolin
Sent: Monday, May 02, 2016 5:08 PM
To: comp-protocols-dns-bind at isc.org
Subject: Re: also-notify and nsupdate doesnt work
In article <mailman.688.1462221733.73610.bind-users at lists.isc.org>,
"Darcy Kevin (FCA)" <kevin.darcy at fcagroup.com> wrote:
> Apologies if this has already been asked, but are you sending these
> NOTIFYs from a master which is _not_ in the "masters" clause of the
> nameserver which is receiving it? That's precisely the use case for "allow-notify"...
The use case for also-notify is when you have slave servers that aren't in the NS records of the zone. Otherwise, those slaves won't update until the Refresh timer goes off.
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list
bind-users mailing list
bind-users at lists.isc.org
More information about the bind-users