8 Čen
2018
8 Čen
'18
16:16
Am 08.06.2018 um 15:21 schrieb Daniel Stirnimann:
Maybe not. Is Knot trying NOTIFYs endlessly? If not, then it just gives
you the knowledge on the master that the NOTIFY did not arrive on the slave.
We also worked around by using eg: max-refresh-time on the slave
regards
Klaus
Every outgoing
DNS message from Knot is over TCP. We didn't want to wait
or deduce whether a slave got the message.
I like this approach a lot. We had problems in the past that notifies
got lost in a network which was not on our control. We had to work
around it by lowering the SOA refresh interval. I guess using TCP avoids
this problem completely.