Re: more flexible serial number handling in dnssec-signzone

2010-10-15 Thread Niobos
On 2010-10-15 20:23, Jukka Pakkanen wrote: > 15.10.2010 20:54, Niobos kirjoitti: >> What's the advantage of using a date anyway? I too can see when a zone >> was last edited, even down to the second, by watching the RRSIG(SOA) >> timing. > > Time usually goes to one direction only, forward... so

Re: more flexible serial number handling in dnssec-signzone

2010-10-15 Thread Jukka Pakkanen
15.10.2010 20:54, Niobos kirjoitti: What's the advantage of using a date anyway? I too can see when a zone was last edited, even down to the second, by watching the RRSIG(SOA) timing. Time usually goes to one direction only, forward... so using date/time makes sure you are always incrementing

Re: more flexible serial number handling in dnssec-signzone

2010-10-15 Thread Ben McGinnes
On 16/10/10 4:54 AM, Niobos wrote: > > What's the advantage of using a date anyway? I too can see when a zone > was last edited, even down to the second, by watching the RRSIG(SOA) timing. Python 2.6.5 (r265:79359, Mar 24 2010, 01:32:55) [GCC 4.0.1 (Apple Inc. build 5493)] on darwin Type "help",

Re: more flexible serial number handling in dnssec-signzone

2010-10-15 Thread Niobos
On 2010-10-15 19:38, Jay Ford wrote: > I found myself in need of more flexibility in the way dnssec-signzone > handled SOA serial numbers, so I hacked in a way to have the new serial > number generated by calling strftime(3) with a user-specified time > format. I was on the verge of doing something

more flexible serial number handling in dnssec-signzone

2010-10-15 Thread Jay Ford
I found myself in need of more flexibility in the way dnssec-signzone handled SOA serial numbers, so I hacked in a way to have the new serial number generated by calling strftime(3) with a user-specified time format. For example dnssec-signzone -N '%Y%m%d1' ... will generate a serial number