[sf-lug] Notice: ns1.svlug.org downtime, DNS secondary
Al
awsflug at sunnyside.com
Sat Nov 13 08:59:37 PST 2021
I don't think I'm directly affected by svlug being down since I don't
AXFR from ns1.svlug, and I don't originate any records that define svlug
to be a domain server, but good to know what's going on.
I wasn't monitoring ping status for svlug but I've added it to the
list. Historically I monitor balug and linuxmafia. (linuxmafia stays
up just all the time! :) )
I check BIND status every 10 minutes but haven't seen any transfers
hung, because of course I'm not transferring from svlug.
On my 10 minute checks I haven't been comparing the contents looking for
change in zones I was seconding but, since that's a normal function I do
for internal zones, it was easy to add that; because I hadn't been
checking I didn't see the list of name servers change. Next time I will.
On 11/13/2021 01:30, Michael Paoli wrote:
> Thanks, noted, also:
> $ dig +noall +answer +nottl ns1.svlug.org. AAAA www.svlug.org. AAAA
> ns1.svlug.org. IN AAAA 2600:3c01::f03c:91ff:fe96:e78e
> www.svlug.org. IN AAAA 2600:3c01::f03c:91ff:fe96:e78e
>
> (trimmed for relevance/brevity):
> https://www.mpaoli.net/~michael/bin/DNS_CK
> $ DNS_CK
> FQDN: balug.org.:
> authority:
> balug.org. 86400 IN NS ns1.svlug.org.
> ;; connection timed out; no servers could be reached @64.62.190.98
> (ns1.svlug.org.)
> ;; connection timed out; no servers could be reached
> @2600:3c01::f03c:91ff:fe96:e78e (ns1.svlug.org.)
> FQDN: e.9.1.0.5.0.f.1.0.7.4.0.1.0.0.2.ip6.arpa.:
> authority:
> e.9.1.0.5.0.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns1.svlug.org.
> ;; connection timed out; no servers could be reached @64.62.190.98
> (ns1.svlug.org.)
> ;; connection timed out; no servers could be reached
> @2600:3c01::f03c:91ff:fe96:e78e (ns1.svlug.org.)
> FQDN: sf-lug.org.:
> authority:
> sf-lug.org. 86400 IN NS ns1.svlug.org.
> ;; connection timed out; no servers could be reached @64.62.190.98
> (ns1.svlug.org.)
> ;; connection timed out; no servers could be reached
> @2600:3c01::f03c:91ff:fe96:e78e (ns1.svlug.org.)
> FQDN: sf-lug.com.:
> authority:
> sf-lug.com. 172800 IN NS ns1.svlug.org.
> ;; connection timed out; no servers could be reached @64.62.190.98
> (ns1.svlug.org.)
> ;; connection timed out; no servers could be reached
> @2600:3c01::f03c:91ff:fe96:e78e (ns1.svlug.org.)
> FQDN: sflug.org.:
> authority:
> sflug.org. 86400 IN NS ns1.svlug.org.
> ;; connection timed out; no servers could be reached @64.62.190.98
> (ns1.svlug.org.)
> ;; connection timed out; no servers could be reached
> @2600:3c01::f03c:91ff:fe96:e78e (ns1.svlug.org.)
> FQDN: sflug.com.:
> authority:
> sflug.com. 172800 IN NS ns1.svlug.org.
> ;; connection timed out; no servers could be reached @64.62.190.98
> (ns1.svlug.org.)
> ;; connection timed out; no servers could be reached
> @2600:3c01::f03c:91ff:fe96:e78e (ns1.svlug.org.)
> FQDN: sflug.net.:
> authority:
> sflug.net. 172800 IN NS ns1.svlug.org.
> ;; connection timed out; no servers could be reached @64.62.190.98
> (ns1.svlug.org.)
> ;; connection timed out; no servers could be reached
> @2600:3c01::f03c:91ff:fe96:e78e (ns1.svlug.org.)
> FQDN: sf-lug.net.:
> authority:
> sf-lug.net. 172800 IN NS ns1.svlug.org.
> ;; connection timed out; no servers could be reached @64.62.190.98
> (ns1.svlug.org.)
> ;; connection timed out; no servers could be reached
> @2600:3c01::f03c:91ff:fe96:e78e (ns1.svlug.org.)
> FQDN: berkeleylug.com.:
> authority:
> berkeleylug.com. 172800 IN NS ns1.svlug.org.
> ;; connection timed out; no servers could be reached @64.62.190.98
> (ns1.svlug.org.)
> ;; connection timed out; no servers could be reached
> @2600:3c01::f03c:91ff:fe96:e78e (ns1.svlug.org.)
> $
>
> And removed from masters/primaries:
> balug.org. 86400 IN NS ns1.svlug.org.
> e.9.1.0.5.0.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns1.svlug.org.
> sf-lug.org. 86400 IN NS ns1.svlug.org.
> sf-lug.com. 172800 IN NS ns1.svlug.org.
> sflug.org. 86400 IN NS ns1.svlug.org.
> sflug.com. 172800 IN NS ns1.svlug.org.
> sflug.net. 172800 IN NS ns1.svlug.org.
> sf-lug.net. 172800 IN NS ns1.svlug.org.
> berkeleylug.com. 172800 IN NS ns1.svlug.org.
> # (for d in balug.org. e.9.1.0.5.0.f.1.0.7.4.0.1.0.0.2.ip6.arpa.
> sf-lug.org. sf-lug.com. sflug.org. sflug.com. sflug.net. sf-lug.net.
> berkeleylug.com.; do { echo "update delete $d IN NS ns1.svlug.org.";
> echo send; } | nsupdate -l; done)
> #
>
> And delegating authority records ...
> removed from:
> balug.org.
> sf-lug.org.
> berkeleylug.com.
> e.9.1.0.5.0.f.1.0.7.4.0.1.0.0.2.ip6.arpa.
> DNS_CK now comes back clean, notwithstanding pending delegating
> authority record deletion:
>
> And Al, I presume you will likewise handle the needed for:
> sf-lug.com.
> sflug.org.
> sflug.com.
> sflug.net.
> sf-lug.net.
>
> references/excerpts:
>
>> Date: Fri, 12 Nov 2021 17:24:51 -0800
>> From: Rick Moen <rick at linuxmafia.com>
>> To: Michael.Paoli at cal.berkeley.edu, [TRIMMED]
>> Subject: Notice: ns1.svlug.org downtime, DNS secondary
>>
>> Starting late this morning (2021-11-12), SVLUG was obliged to
>> take down for rearchitecting and rebuild its Linode virthost
>> www.svlug.org AKA ns1.svlug.org, IP address 64.62.190.98 .
>> Downtime will persist for some time. There is no current ETA.
>>
>> _You_ are receiving this (form) e-mail because you are, or have been a
>> DNS admin for one or more of the following domains:
>>
>> balug.org
>> berkeleylug.com
>> sf-lug.org
>> sf-lug.net
>> sf-lug.com
>> sflug.org
>> sflug.net
>> sflug.com
>>
>> (Please forward this notice to any DNS sysadmin I've missed.)
>>
>> Please be advised that ns1.svlug.org is NOT, for the time being,
>> doing secondary (or any) DNS, so should be removed from rotation
>> at the DNS master, effective immediate. (I'd recommend also
>> taking it out of the parent zone records at your registrar.)
>>
>> SVLUG will advise when ns1.svlug.org service resumes. We expect the IP
>> to be unchanged.
>>
>> -- Rick Moen
>> rick at linuxmafia.com
>> (650) 283-7902
>> For Silicon Valley Linux User Group
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://linuxmafia.com/pipermail/sf-lug/attachments/20211113/6bdaf333/attachment.html>
More information about the sf-lug
mailing list