[dnsdist] dnsdist NOTIFY distribution

[Remi Gacogne]

Hi,

On 12/4/19 4:03 PM, Martin wrote:
> can you explain why you don’t advise using TeeAction for NOTIFY-ing backend slave pool?

In theory, if all you want is for the NOTIFY to be sent to all your
slaves, that should work. The obvious drawback is that only one of your
slave will be able to reply to the master so if anything goes wrong for
at least one of the other slaves, they will not get another NOTIFY from
the master.
Please also note that I'm not sure you won't run into the same issue
than the one you had with nproxy.

Best regards,

Remi

>> On 26 Feb 2019, at 16:59, Remi Gacogne <remi.gacogne at powerdns.com> wrote:
>>
>> Hi Martin,
>>
>> On 2/26/19 3:58 PM, Martin Toth wrote:
>>> I just want to ensure myself how NOTIFY distribution in DNSDIST
>>> exactly works. My setup looks like this - MASTER -> DNSDIST -> SLAVE
>>> PDNSs (pool of 4 nodes)
>>>
>>> My Question is if MASTER will send NOTIFY to DNSDIST, will DNSDIST
>>> redistribute these NOTIFY to all SLAVES in DNSDIST backend? How to I
>>> achieve situation that all slaves in dnsdist backend will be notified
>>> of zone change on MASTER?
>>
>> I'm afraid you can't, dnsdist can route a query only to a single
>> backend, with the exception of the TeeAction, but I would advise against
>> trying to use it for that case.
>> Is there a reason your master doesn't speak to the slaves directly?
>>
>> Best regards,
>> -- 
>> Remi Gacogne
>> PowerDNS.COM BV - https://www.powerdns.com/
>>
>> _______________________________________________
>> dnsdist mailing list
>> dnsdist at mailman.powerdns.com
>> https://mailman.powerdns.com/mailman/listinfo/dnsdist
> 


-- 
Remi Gacogne
PowerDNS.COM BV - https://www.powerdns.com/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://mailman.powerdns.com/pipermail/dnsdist/attachments/20191204/434ee531/attachment.sig>