> -Ursprüngliche Nachricht-
> Von: bind-users Im Auftrag von John
> Thurston
> Gesendet: Freitag, 17. Februar 2023 21:43
> An: bind-users@lists.isc.org
> Betreff: Re: Simplistic serial number roll back
>
> Agreed.
>
>
> I'm not considering rolling back to old zon
Agreed.
I'm not considering rolling back to old zone data, but considering
changing the algorithm used to generate the serial number for new zone
data. The new algorithm would result in the new data being published
with serial numbers which would be ignored as being "older" if they were
gener
Well, the serial number arithmetics is there for a reason - you usually don’t want to rollback to previous version of the zone - you can have multiple primaries with different serial numbers.I don’t really consider the two step rollover of the serial number that complicated, so something extra need
That was my first thought, but stopping the secondary would affect all
of the published zones.
If retransfer ignores serial number, then using "rndc retransfer" would
affect only the specifically-named zone in the specifically-named view.
Resolution of the other zones, in all of the other view
Why so complicated? Stop the secondary, purge the zone files and journal, and start the secondary. The zones will get retransfered as there’s no state now.--Ondřej Surý — ISC (He/Him)My working hours and your working hours may be different. Please do not feel obligated to reply outside your normal
Assumptions: A primary and several secondaries, with the secondaries
using XFR to stay up to date.
Scenario: Make a change in the serial number algorithm which will result
in newer zone-data being published on an "earlier" serial number.
The 'correct' method is to increase the serial number
6 matches
Mail list logo
