On 7 Oct 2014 18:42, "Alan Clegg" <a...@clegg.com> wrote: > > On 10/7/2014 9:49 AM, Terry Burton wrote: > > This is especially useful in bootstrapping scenarios where the zone > > data is held under strict revision control or generated by some > > provisioning system that "owns" the serial number. > > By setting the number backwards, you are breaking all of your slave servers and causing no-end of problems getting all of THEM corrected.
You've misunderstood. I'm not attempting to decrease the serial number. With inline signing you have a hidden serial number in the unsigned zone and an exposed serial number in the signed versions which your slaves track. After redeployment (following DR, emergency relocation, elastic capacity expansion, etc.) I want to be able to bump the exposed serial number (once) back to an appropriate value without having to modify the unsigned zones. (For context, the unsigned zone serial number matches the revision number in a VCS to which the DNS infrastructure hosts and administrators have read-only access, i.e. mandatory separation of infrastructure and data access rights.)
_______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
