[dns-operations] Recommended zone serial number format for over 100 changes / day

[Mark Andrews]

Or you can just use it as a serial number.  Encoding date / time
since epoch only works if the freqency of updates is low.

YYYYMMDDNN is useful for humans editing a zone file which usually
has less than one update a day.  You can look at the serial and see
if you have updated it while still in the editor. The NN are for
the rare occasions when you want to do multiple updates in a day.

It can also help you realise that you forgot to update the serial.

For busier zones and signed zones it is better to do all the changes
with UPDATE and let the server manage the serial and signing/re-signing.

Mark


In message <D3219C10.3DE04%michoski at cisco.com>, "Mike Hoskins (michoski)" writes:
>
> Moved from YYYYMMDDNN to mtime of zone file years ago, no problems.
>
>
> From: dns-operations
> <dns-operations-bounces at dns-oarc.net<mailto:dns-operations-bounces at dns-oar
> c.net>> on behalf of Jonathan Tuliani
> <Jonathan.Tuliani at microsoft.com<mailto:Jonathan.Tuliani at microsoft.com>>
> Date: Wednesday, March 30, 2016 at 2:56 PM
> To:
> "dns-operations at lists.dns-oarc.net<mailto:dns-operations at lists.dns-oarc.ne
> t>" <dns-operations at dns-oarc.net<mailto:dns-operations at dns-oarc.net>>
> Subject: [dns-operations] Recommended zone serial number format for over
> 100 changes / day
>
> Hi DNS Gurus,
>
> RFC1912 recommends the following SOA serial number format: YYYYMMDDnn
>
> However, this does not support more than 100 updates per day (whilst this
> sounds like a lot, the fluidity of the Cloud means there are some
> applications where large numbers of changes are commonplace).
>
> Is there a recommended serial format that supports large numbers of
> changes?
>
> Thanks in advance,
>
> Jonathan Tuliani

-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka at isc.org