Magic 8-ball (i.e., logcheck on ns1.linuxmafia.com) says:
System Events
=-=-=-=-=-=-=
May 30 10:05:36 linuxmafia named[11750]: zone balug.org/IN: serial number (1558725628) received from master 198.144.194.238#53 < ours (1558799284)
May 30 10:30:43 linuxmafia named[11750]: zone sf-lug.org/IN: serial number (1558622463) received from master 198.144.194.238#53 < ours (1558799278)
May 30 10:32:42 linuxmafia named[11750]: zone balug.org/IN: serial number (1558725628) received from master 198.144.194.238#53 < ours (1558799284)
May 30 10:57:43 linuxmafia named[11750]: zone balug.org/IN: serial number (1558725628) received from master 198.144.194.238#53 < ours (1558799284)
Er?
Michael, O Great Oracle of the DNS master, before I go expunging the
local cached zone on ns1.linuxmafia.com so as to converge in the master,
any thoughts or desire to act on your end? Normally, I would expect the
current situation to be _strenuously avoided_ by never taking S/Ns in a
retrograde direction on a zone's DNS master, so I infer that
investigation may be in order (or at least brief discussion).
Upon my recent "renewal" (replaced with new) TLS(/"SSL") certs for
[*.]balug.org, for the cert covering the web stuff, I also added:
*.staging.balug.org (*.balug.org itself also covers the bare
staging.balug.org).
Haven't added any [*.]staging.balug.org stuff to DNS, etc - at least yet,
other than that temporarily added for obtaining the cert itself.
And no rush to do so (time, priorities, ...).
Rationale(?):
I think [*.]staging.balug.org may be more logical/appropriate for
most of what [*.]new.balug.org gets used for these days (well, years now).
Might want to, at some point, phase out [*.]new.balug.org.
Once-upon-a-time www.new.balug.org was intended to and used as
the "go forward" of what www.balug.org itself would generally
become - and they were on separate hosts. Well, for many years now,
www.new.balug.org is on same host as [www.]balug.org,
and www.new.balug.org is typically and mostly (if not entirely)
used as essentially staging/preview of what www.balug.org will become,
typically updating content on www.new.balug.org (and checking/revising it)
before making those same content changes to www.balug.org