On 3/11/23 10:43 AM, Fred Morris wrote:
I've found myself in situations in the past where NOTIFY has been
fetishized as "real time"
"real time" can be a VERY loaded phrase.
Some sometimes it's measured in fractions of a second. Other times it's
measured in minutes.
I've always simply c
I've found myself in situations in the past where NOTIFY has been
fetishized as "real time", and nobody ever ever asked which upstream
server was being queried as a result. So this has been an eye-opening
thread, and if I ever find myself in that situation again it'll give me
something else to
On 3/11/23 10:37 AM, Paul Stead wrote:
Sorry I should have made it clearer that the notifier should only be
shuffled to the top of the list if it is a defined primary for said zone.
Okay. The try the notifier first /if/ it's a configured primary makes
more sense to me. I guess I've not had e
Sorry I should have made it clearer that the notifier should only be
shuffled to the top of the list if it is a defined primary for said zone.
I.e An IP on the notify-from list, but not a configured primary wouldn't be
in the list of primaries for that zone so would not be shuffled to the top
of t
Hi Paul,
Thank you for explaining.
On 3/10/23 12:21 AM, Paul Stead wrote:
Imagine that 1.1.1.1 has lost network connectivity recently. A notify
comes from 2.2.2.2 - if I understand correctly Bind will try 1.1.1.1
first, time out and then try 2.2.2.2 - even though we know given the
situation t
5 matches
Mail list logo
