[dns-operations] Recommended zone serial number format for over 100 changes / day
roy at rightside.rocks
Thu Mar 31 01:49:30 UTC 2016
Even with thousands of updates a day, and 86400 seconds per day, there's
plenty of headroom to handle same-second updates when they do happen...
One approach is to use this pseudocode:
if time() > current_serial:
new_serial = time()
new_serial = serial + 1
This handles both clock rewind scenarios (that never happens in the real
world...) as well as multiple updates in the same second.
It also simply becomes a counter if you have over 86400 updates/day,
although in that case the suggestion to just use a counter makes more sense
so you can start at 1.
On Wed, Mar 30, 2016 at 4:32 PM, Dave Warren <davew at hireahit.com> wrote:
> On 2016-03-30 12:35, Mark Andrews wrote:
>> Or you can just use it as a serial number. Encoding date / time
>> since epoch only works if the freqency of updates is low.
> Even if you have more than one update per second, isn't incrementing the
> serial number and rebuilding the zone once per second going to be
> sufficient for real world purposes?
> Or am I misunderstanding?
> Dave Warren
> dns-operations mailing list
> dns-operations at lists.dns-oarc.net
> dns-jobs mailing list
Sr. Software Architect[image: Rightside] <http://www.rightside.co/>*Mobile* |
roy at rightside.rocks <roy at rightside.ninja>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the dns-operations