> Wondering out loud:
> Maybe it should skip loading that particular member zone if the "coo"
> proproperty already points to different catalog? Would that be more
> resilient against race conditions when named is restarted?
That's an interesting suggestion, and I agree that it can solve the ra
On 30. 04. 23 13:04, Aram Sargsyan wrote:
Hello, Jan-Piet,
> however, when I stop and restart the consumer server, I have
sometimes (not always) seen
>
> catz: catz_addmodzone_cb: zone 'z10.aa' will not be added because
another catalog zone already contains an entry with that zone
>
>whi
Hello, Jan-Piet,
> however, when I stop and restart the consumer server, I have sometimes (not
> always) seen
>
> catz: catz_addmodzone_cb: zone 'z10.aa' will not be added because another
> catalog zone already contains an entry with that zone
>
>which is true, but it doesn't _seem_ to ca
And yes, you can automate this with nsupdate to old and new catalog,
Brilliant, Petr, thank you.
I saw some of the loviest log messages this week during coo from k-catz to
t-catz:
zone t-catz/IN: transferred serial 10: TSIG 't'
catz: t-catz: reload start
catz: updating
4 matches
Mail list logo
