----- Forwarded message from logcheck system account <logcheck(a)linuxmafia.com> -----
Date: Thu, 25 Aug 2016 00:02:02 -0700
From: logcheck system account <logcheck(a)linuxmafia.com>
To: root(a)linuxmafia.com
Subject: linuxmafia.com 2016-08-25 00:02 System Events
System Events
=-=-=-=-=-=-=
Aug 24 23:12:07 linuxmafia named[1064]: zone balug.org/IN: refresh: retry limit for master 198.144.194.238#53 exceeded (source 0.0.0.0#0)
Aug 24 23:12:07 linuxmafia named[1064]: zone balug.org/IN: Transfer started.
Aug 24 23:12:28 linuxmafia named[1064]: transfer of 'balug.org/IN' from 198.144.194.238#53: failed to connect: timed out
Aug 24 23:12:28 linuxmafia named[1064]: transfer of 'balug.org/IN' from 198.144.194.238#53: Transfer completed: 0 messages, 0 records, 0 bytes, 21.000 secs (0 bytes/sec)
Aug 24 23:14:03 linuxmafia named[1064]: zone sf-lug.com/IN: refresh: retry limit for master 198.144.194.238#53 exceeded (source 0.0.0.0#0)
Aug 24 23:16:12 linuxmafia named[1064]: zone sf-lug.org/IN: refresh: retry limit for master 198.144.194.238#53 exceeded (source 0.0.0.0#0)
Aug 24 23:39:12 linuxmafia named[1064]: zone e.9.1.0.5.0.f.1.0.7.4.0.1.0.0.2.ip6.arpa/IN: refresh: retry limit for master 198.144.194.238#53 exceeded (source 0.0.0.0#0)
Aug 24 23:39:12 linuxmafia named[1064]: zone e.9.1.0.5.0.f.1.0.7.4.0.1.0.0.2.ip6.arpa/IN: Transfer started.
Aug 24 23:39:33 linuxmafia named[1064]: transfer of 'e.9.1.0.5.0.f.1.0.7.4.0.1.0.0.2.ip6.arpa/IN' from 198.144.194.238#53: failed to connect: timed out
Aug 24 23:39:33 linuxmafia named[1064]: transfer of 'e.9.1.0.5.0.f.1.0.7.4.0.1.0.0.2.ip6.arpa/IN' from 198.144.194.238#53: Transfer completed: 0 messages, 0 records, 0 bytes, 21.000 secs (0 bytes/sec)
Aug 24 23:39:41 linuxmafia named[1064]: zone balug.org/IN: refresh: retry limit for master 198.144.194.238#53 exceeded (source 0.0.0.0#0)
----- End forwarded message -----
(Greetings from MidAmeriCon II in Kansas City.)
IP address 198.144.194.238 appears to be (or have been) the master
nameserver for several domains...
zone balug.org
zone e.9.1.0.5.0.f.1.0.7.4.0.1.0.0.2.ip6.arpa
zone sf-lug.org
...for which ns1.linuxmafia.com has been doing slave nameservice at your
request. Today, I notice I'm getting AXFR problems:
Aug 22 11:15:19 linuxmafia named[11693]: zone balug.org/IN: refresh: retry limit for master 198.144.194.238#53 exceeded (source 0.0.0.0#0)
Aug 22 11:15:19 linuxmafia named[11693]: zone balug.org/IN: Transfer started.
Aug 22 11:15:40 linuxmafia named[11693]: transfer of 'balug.org/IN' from 198.144.194.238#53: failed to connect: timed out
Aug 22 11:15:40 linuxmafia named[11693]: transfer of 'balug.org/IN' from 198.144.194.238#53: Transfer completed: 0 messages, 0 records, 0 bytes, 21.000 secs (0 bytes/sec)
Aug 22 11:21:30 linuxmafia named[11693]: zone e.9.1.0.5.0.f.1.0.7.4.0.1.0.0.2.ip6.arpa/IN: refresh: retry limit for master 198.144.194.238#53 exceeded (source 0.0.0.0#0)
Aug 22 11:40:34 linuxmafia named[11693]: zone balug.org/IN: refresh: retry limit for master 198.144.194.238#53 exceeded (source 0.0.0.0#0)
Aug 22 11:40:34 linuxmafia named[11693]: zone balug.org/IN: Transfer started.
Aug 22 11:40:55 linuxmafia named[11693]: transfer of 'balug.org/IN' from 198.144.194.238#53: failed to connect: timed out
Aug 22 11:40:55 linuxmafia named[11693]: transfer of 'balug.org/IN' from 198.144.194.238#53: Transfer completed: 0 messages, 0 records, 0 bytes, 20.999 secs (0 bytes/sec)
Aug 22 11:45:53 linuxmafia named[11693]: zone sf-lug.org/IN: refresh: retry limit for master 198.144.194.238#53 exceeded (source 0.0.0.0#0)
I notice that 198.144.194.238 no longer responds to ping.
I notice that auth namservers for the three domains no longer include
one that resolves to IP 198.144.194.238.
I notice ns1.linuxmafia.com is still in the authoritative roster for
domain balug.org.
I notice ns1.linuxmafia.com is NOT any longer in the authoritative
roster for domain sf-lug.org.
Accordingly, I am switching off slave nameservice for the three cited
domains at this time. Please advise if you'd like me to resume slave
nameservice for any of them, and from what master nameserver IP for
each.
Thanks. :-)
And ... passing it to on-list here, as it pro'lly is (slightly) overdue
for at least a trace of mention here (I probably last mentioned it on
this list some year(s) ago or so).
It basically came about from typical general practice of sysadmin /
listadmin, of being "lazy" ... a.k.a. efficient. :-) Basically,
automate (or semi-automate) that which can be (semi-)automated (so one
can move onto the more "interesting" tasks, and let the comptuers do
what they're good at and is boring/tedious for humans).
Not surprisingly, I'd gotten rather tied of the various "unsubscribe
me" requests that were typically sent to me, or sending or Reply-To
address I'd used, or to the list, or to one of the BALUG contact
addresses, etc. Most specifically the bone-headed, naive, ignorant,
lazy, and/or "demanding" emails of that nature. And, I also got rather
tired and annoyed with having to actually think about it, assemble the
information, reply, include relevant links and information, etc.
Really thought handling it ought be a script, or ... quite close to it.
And certainly didn't want to mistrain users to ask listadmins to do
for them what they ought be doing for themselves and should be fully
capable of ... and to reasonably explain the situation, information,
etc. And also cover the "what if" - in case they were actually trying
and somehow failing to unsubscribe - so they'd be pre-armed to
potentially at least come back with useful information, should that
ever happen to occur.
So ... thinking over the script possibility - in different context, I'd
probably do that, but with various BALUG folks, at least potentially
responding, etc, and trying to also share the information where it
might be a bit handier to reference and use - and also thinking of how
I was typically doing it when I replied (often not at mere bare CLI,
but some GUI email client thingy/interface) ... so there'd likely be at
least some trace of copy/paste anyway. So ... decided I'd set up simple
wiki page with boilerplate text that could be copied and pasted, and
would pretty much cover the matter.
I'd also done, I think fair bit earlier, similar to handle responses to
the fairly common "can I post a job to the BALUG list?" type questions -
or rather to highly similar - which also works pretty darn well. And
likewise, any BALUG folk can leverage it - no need to track down a
script - just copy/paste, and it's handled.
For reference also, the one regarding "jobs", is located here:
https://www.wiki.balug.org/wiki/doku.php?id=balug:can_i_post_a_job_-_and_bo…
> From: "Rick Moen" <rick(a)linuxmafia.com>
> To: Michael Paoli <Michael.Paoli(a)cal.berkeley.edu>
> Cc: balug-contact(a)balug.org
> Subject: Re: Our "boiler plate" seems to work pretty well [Re: BALUG
> list(s) unsubscribe (Re: About email subscription)]
> Date: Mon, 18 Apr 2016 11:05:29 -0700
> Quoting Michael Paoli (Michael.Paoli(a)cal.berkeley.edu):
>
>> Well, our "boiler plate":
>> https://www.wiki.balug.org/wiki/doku.php?id=balug:unsubscribe
>> seems to work fairly well.
>>
>> *Sometimes* (though rarely) folks even say "thanks" - though once I
>> email 'em the boiler plate, I typically never hear from 'em again.
>> I don't think I've yet had anyone I've sent the boiler plate to that
>> ever came back with a response indicating that they weren't able
>> to unsubscribe after they were sent the boiler plate
>> information / instructions.
> That's a remarkable achievemnet, seriously. Well done.
DO NOT REPLY ALL (unless you're subscribed to BOTH lists)
FYI, I noticed short bit ago (they were up and online
earlier today), that offline are:
SF-LUG:
([www.]sf-lug.{org,com,info}), etc.
but lists remain up and on-line
also
BALUG
on-line: [www.]balug.org & lists,
all other balug bits (e.g. wiki, archive other than list archive, etc.)
still presently off-line.
I expect to have more information (and hopefully have whatever is the issue
corrected) by later this evening or so.
(POTS line appears operational, but not reaching the subnet via
DSL - I'll know more when I'm on-site again).
Rick,
If you could please, and would be willing,
could you cover DNS slave services for BALUG,
notably these zones:
e.9.1.0.5.0.f.1.0.7.4.0.1.0.0.2.ip6.arpa
balug.org
master(s) (all for each of the above):
198.144.194.238
2001:470:1f04:19e::2
Do note, however, that at present time,
balug.org is NOT (yet) Internet delegated to those IPs - I don't expect
that to happen until we extricate ourselves from DreamHost.com - however
in the meantime it is maintained quite highly alike to the balug.org.
DNS data on DreamHost.com - I check periodically, and only differences
I'm aware of are SOA MNAME, RNAME, and often the REFRESH (I don't know
where they get their REFRESH number from - it seems to vary some fair
bit, with no particular discernible pattern) and I tend to keep the
serial # one ahead of DreamHost.com (at least most of the time when I
check/notice it). If you'd prefer, for balug.org, could also
just set up as "warm standby" - verify (to-be) slaves can do
AXFR pull, and put most of the configuration in place, but just
don't actually activate it until DNS is fully and properly Internet
delegated (or we're free from DreamHost.com and about to so delegate).
I'm presuming you could do/offer this on both ns1.linuxmafia.com. and
also ns1.svlug.org.? That would be great, if you're able to.
I'm also presuming the various IP information and out-of-band
communication information is still the same as when we set up
slaves for sf-lug.org (plus any relevant updates received since then).
Just let me know, thanks (can also email just me directly for any bits
that ought not get publicly archived, etc.).