[BALUG-Admin] BALUG.org DNS, ...

[Michael Paoli]

BALUG.org DNS,

For anyone that might notice, and might be wondering ...

$ dig +noall +answer +multiline balug.org. SOA | fgrep serial
                                 3909849755 ; serial
$
... WFT scheme is *that*?  ;->
Ah, ... the master zone file comments make that much more clear:
# fgrep -i serial balug.org
                                 3909849755; SERIAL ; DO NOT EXCEED  
4164575247 BEFORE (3W EXPIRY + 1 day) 1507640615  
2017-10-10T06:03:35-0700 2017-10-10T13:03:35+0000 ; rolling SERIAL  
from 2017091600 date +'%Y%m%d00' to date +%s (absolute max is  
4294967295 2^32-1)
#

So yes, I know, YYYYMMDDNN is "preferred" per RFC(s) (more human readable),
but it's by no means the only permissible scheme.  For various reasons,
I mostly much prefer seconds since ephoch - it's likely runner-up in
most commonly supported/used schemes, possibly excepting simple
monotonically increasing, and (by sheer volume) whatever the heck
AWS is doing (Route 53 always giving serial of 0).
Anyway, bit beyond 3 weeks from now, and should then be converged to
seconds since epoch ... in the meantime, something in the
range between 3909849755 and 4164575247.

Also, delegated subdomains - those:
{beta,ipv6,new,temp,test}.balug.org.
have now been rolled up into the balug.org. zone - possibly
notwihstanding any relevant still pending cached TTL expirations
(for the roll-up, excepting NS and SOA, and possibly some TTLs, the data
is thus far same - just has been rolled up to balug.org zone).