hi,
Am 02.05.2016 um 23:19 schrieb Darcy Kevin (FCA):
Right. also-notify (on a master) versus allow-notify (on a slave). Different
use cases.
the problem would not in the notify config.
the notify and transfer works fine with the zone config. until i add the
dynamic update option on the
hi,
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.
thats exactrly how i want to use it...
jonny
___
Please visit
hi,
> 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 notifies are sent by the only master, which is noted in the
Margolin
Sent: Monday, May 02, 2016 5:08 PM
To: comp-protocols-dns-b...@isc.org
Subject: Re: also-notify and nsupdate doesnt work
In article <mailman.688.1462221733.73610.bind-us...@lists.isc.org>,
"Darcy Kevin (FCA)" <kevin.da...@fcagroup.com> wrote:
> Apologies if th
In article ,
"Darcy Kevin (FCA)" 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
ot;allow-notify"...
- Kevin
-Original Message-
From: bind-users-boun...@lists.isc.org
[mailto:bind-users-boun...@lists.isc.org] On Behalf Of jo...@hasig.de
Sent: Monday, May 02, 2016 10:31 AM
To: Alan Clegg; Matthew Pounsett
Cc: bind-users@lists.isc.org
Subject: Re: also-notify and nsup
Aye... I'm sitting here looking for zone transfer use of TSIG...
It's too early in the morning.
*sigh*
On 5/2/16, 10:30 AM, "jo...@hasig.de" wrote:
>hi,
>
> > There's nothing in this part of the configuration that links key usage
>to
> > the zone.
>
>sure. the * is.
>and the
hi,
> There's nothing in this part of the configuration that links key usage to
> the zone.
sure. the * is.
and the update works great.
the serial counts up,
the update is taken,
the slave is motified and updated.
the only thing is, that the "also-notify" servers get no notify.
(if i do an
On 5/2/16, 10:09 AM, "bind-users-boun...@lists.isc.org on behalf of
jo...@hasig.de" wrote:
>
>1.
>zone "abc.net" {
> notify yes;
> type master;
> file "abc.net";
> allow-transfer { any; };
>
hi,
> Can you share your whole config? It's possible there are options outside
> the zone stanzas that could affect the behaviour of notifies.
no, the whole config covers about 600 zones with different configs.
and why should the notify work with stanza 1 but not with 2?
the notify 1 works
hi,
What you're describing sounds wrong. It shouldn't work that way.
what do you mean by "wrong" and which "it" should not work? :-)
Can you share your configuration so that we can see what's actually
happening?
sure :-)
samples:
1.
zone "abc.net" {
notify yes;
type
On 2 May 2016 at 10:09, wrote:
> hi,
>
> What you're describing sounds wrong. It shouldn't work that way.
>>
> what do you mean by "wrong" and which "it" should not work? :-)
>
>
What I mean is, given a typical configuration, the brokenness you're
observing shouldn't be broken.
On 1 May 2016 at 23:57, wrote:
> hi,
> i have a setup with one normal and some hidden slaves.
> i set up a zone with also-notify and all worked fine.
> all slaves got notifies and updates.
> now i added a key and policy to remote update the zone.
> the updates with nsupdate woks
hi,
i have a setup with one normal and some hidden slaves.
i set up a zone with also-notify and all worked fine.
all slaves got notifies and updates.
now i added a key and policy to remote update the zone.
the updates with nsupdate woks fine.
but the notify is only sent to the slave, but not to
14 matches
Mail list logo