Hi Graham,
> Has anybody on-list got a clever(er?) trick? I suppose that 9.10 with
> in-view might make the problem go away.
Instead of notifying all views at once you could just create a "notification
chain", where a view only notifies one other view:
view_1 notifies view_2.
On 19/01/2015 19:10, Evan Hunt wrote:
> On Mon, Jan 19, 2015 at 05:56:52PM +, Graham Clinch wrote:
>> I think this is down to an optimisation in lib/dns/zone.c which checks
>> whether a notification is already queued to the same 'dst' address,
>> ignoring whether the key differs (roughly line 9
On Mon, Jan 19, 2015 at 05:56:52PM +, Graham Clinch wrote:
> I think this is down to an optimisation in lib/dns/zone.c which checks
> whether a notification is already queued to the same 'dst' address,
> ignoring whether the key differs (roughly line 9990?).
>
> Is this the 'correct' behaviour
Hi List,
Using BIND 9.9, I am trying to notify two different slave views on the
same host using TSIG keys as the differentiator:
also-notify { 127.0.0.1 key slave1; 127.0.0.1 key slave2; };
It appears that only the first (slave1) receives a notify.
If I change the second address to a different
4 matches
Mail list logo
