On 18.03.21 15:25, stefan.bec...@t-systems.com wrote:
> Does that mean TeeAction is an additional action that is processed
additionally to the "normal" distribution of a query? Say dnsdist is
configured with one pool of servers. When using TeeAction does that mean
an incoming Notify is send to
Hello Stefan,
You could choose to configure your master with the 2 real IP's of the
slaves; Adding a second slave (or third) is relatively easy in most (if
not all) authoritative dns software.
Regards
Kai
On 18-03-2021 14:42, Stefan via dnsdist wrote:
Hi there,
I’ve got the following setup
Hello Stefan,
It's a bit of a hack, because not meant for that. But TeeAction
(https://www.dnsdist.org/rules-actions.html#TeeAction) could work maybe.
Example:
addAction(OpcodeRule(DNSOpcode.Notify),TeeAction("192.168.2.1"))
addAction(OpcodeRule(DNSOpcode.Notify),TeeAction("192.168.2.2"))
add
Hi there,
I've got the following setup: I am running dnsdist in front of two slaves. My
master nameserver sends notify messages to the (service) IP of the dnsdist, not
directly two the slaves (for several reasons). As I know so far dnsdist does
not distribute notify messages to all servers behi
