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

[Jonathan Tuliani]

Thank you everyone for the feedback so far.

It seems there are two mutually-exclusive options:

1.       Stick with the YYYYMMDDnn format, which is intended more for manual edits etc but doesn't support over 100 updates/day.

2.       Use a different format, based on time or incremental serial number.

The reason I'm keen to stick with the YYYYMMDDnn format is that since it's an RFC recommendation, some of our users get confused or concerned when we do anything else.  For example, a different format may be flagged by DNS validation tools* and I'm even told that at least one ccTLD registry *requires* this format (I will follow up with them privately).

However, at the same time, I need to support large numbers of updates/day.

It seems there's no way to have the 'best of both'.

Thank you again for the useful input,

- Jonathan

* For example, www.dnssy.com/report.php<http://www.dnssy.com/report.php> gives a warning ("Your SOA serial number is 1. This does not match the recommended format of YYYYMMDDnn [RIPE-203]<http://www.ripe.net/docs/ripe-203.html>. This is not necessarily a problem as long as your DNS admin knows what they are doing.")  I also see a warning in mxtoolbox.com ("SOA Serial Number Format is Invalid")

From: Jonathan Tuliani
Sent: 30 March 2016 19:56
To: 'dns-operations at lists.dns-oarc.net' <dns-operations at lists.dns-oarc.net>
Subject: 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.dns-oarc.net/pipermail/dns-operations/attachments/20160331/fce03139/attachment.html>