Petr Bena wrote:
>
> So when someone changes zone on A via nsupdate, NOTIFY and subsequent IXFR
> goes like this: A -> B -> C instead of:
>
> A -> B
> -> C
Chaining NOTIFY like A -> B -> C is very common - I would guess most TLDs
do it. In many cases, A is a secure hidden primary, B are zone tr
On 21/04/2020 17:05, Petr Bena wrote:
Hi Petr,
> So when someone changes zone on A via nsupdate, NOTIFY and subsequent
> IXFR goes like this: A -> B -> C instead of:
This is just fine. There are many DNs setups organised like this. Your
configuration isn't unique or strange.
> What confuses me
Hello,
In our massive corporate setup with hundreds BIND servers all around
planet, we have some "funny" configurations (please don't ask why :)),
that seem to be actually working just fine, but I would like to
understand if this is actually supported setup, or they just work by
accident or d
3 matches
Mail list logo
