<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
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.<br>
<font face="Arial"><br>
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! :) )<br>
</font><br>
I check BIND status every 10 minutes but haven't seen any transfers
hung, because of course I'm not transferring from svlug.<br>
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.<br>
<br>
<div class="moz-cite-prefix">On 11/13/2021 01:30, Michael Paoli
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:20211113013053.861251kinsck3irx@webmail.rawbw.com">Thanks,
noted, also:
<br>
$ dig +noall +answer +nottl ns1.svlug.org. AAAA <a class="moz-txt-link-abbreviated" href="http://www.svlug.org">www.svlug.org</a>.
AAAA
<br>
ns1.svlug.org. IN AAAA
2600:3c01::f03c:91ff:fe96:e78e
<br>
<a class="moz-txt-link-abbreviated" href="http://www.svlug.org">www.svlug.org</a>. IN AAAA
2600:3c01::f03c:91ff:fe96:e78e
<br>
<br>
(trimmed for relevance/brevity):
<br>
<a class="moz-txt-link-freetext" href="https://www.mpaoli.net/~michael/bin/DNS_CK">https://www.mpaoli.net/~michael/bin/DNS_CK</a>
<br>
$ DNS_CK
<br>
FQDN: balug.org.:
<br>
authority:
<br>
balug.org. 86400 IN NS ns1.svlug.org.
<br>
;; connection timed out; no servers could be reached @64.62.190.98
(ns1.svlug.org.)
<br>
;; connection timed out; no servers could be reached
@2600:3c01::f03c:91ff:fe96:e78e (ns1.svlug.org.)
<br>
FQDN: e.9.1.0.5.0.f.1.0.7.4.0.1.0.0.2.ip6.arpa.:
<br>
authority:
<br>
e.9.1.0.5.0.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS
ns1.svlug.org.
<br>
;; connection timed out; no servers could be reached @64.62.190.98
(ns1.svlug.org.)
<br>
;; connection timed out; no servers could be reached
@2600:3c01::f03c:91ff:fe96:e78e (ns1.svlug.org.)
<br>
FQDN: sf-lug.org.:
<br>
authority:
<br>
sf-lug.org. 86400 IN NS ns1.svlug.org.
<br>
;; connection timed out; no servers could be reached @64.62.190.98
(ns1.svlug.org.)
<br>
;; connection timed out; no servers could be reached
@2600:3c01::f03c:91ff:fe96:e78e (ns1.svlug.org.)
<br>
FQDN: sf-lug.com.:
<br>
authority:
<br>
sf-lug.com. 172800 IN NS ns1.svlug.org.
<br>
;; connection timed out; no servers could be reached @64.62.190.98
(ns1.svlug.org.)
<br>
;; connection timed out; no servers could be reached
@2600:3c01::f03c:91ff:fe96:e78e (ns1.svlug.org.)
<br>
FQDN: sflug.org.:
<br>
authority:
<br>
sflug.org. 86400 IN NS ns1.svlug.org.
<br>
;; connection timed out; no servers could be reached @64.62.190.98
(ns1.svlug.org.)
<br>
;; connection timed out; no servers could be reached
@2600:3c01::f03c:91ff:fe96:e78e (ns1.svlug.org.)
<br>
FQDN: sflug.com.:
<br>
authority:
<br>
sflug.com. 172800 IN NS ns1.svlug.org.
<br>
;; connection timed out; no servers could be reached @64.62.190.98
(ns1.svlug.org.)
<br>
;; connection timed out; no servers could be reached
@2600:3c01::f03c:91ff:fe96:e78e (ns1.svlug.org.)
<br>
FQDN: sflug.net.:
<br>
authority:
<br>
sflug.net. 172800 IN NS ns1.svlug.org.
<br>
;; connection timed out; no servers could be reached @64.62.190.98
(ns1.svlug.org.)
<br>
;; connection timed out; no servers could be reached
@2600:3c01::f03c:91ff:fe96:e78e (ns1.svlug.org.)
<br>
FQDN: sf-lug.net.:
<br>
authority:
<br>
sf-lug.net. 172800 IN NS ns1.svlug.org.
<br>
;; connection timed out; no servers could be reached @64.62.190.98
(ns1.svlug.org.)
<br>
;; connection timed out; no servers could be reached
@2600:3c01::f03c:91ff:fe96:e78e (ns1.svlug.org.)
<br>
FQDN: berkeleylug.com.:
<br>
authority:
<br>
berkeleylug.com. 172800 IN NS ns1.svlug.org.
<br>
;; connection timed out; no servers could be reached @64.62.190.98
(ns1.svlug.org.)
<br>
;; connection timed out; no servers could be reached
@2600:3c01::f03c:91ff:fe96:e78e (ns1.svlug.org.)
<br>
$
<br>
<br>
And removed from masters/primaries:
<br>
balug.org. 86400 IN NS ns1.svlug.org.
<br>
e.9.1.0.5.0.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS
ns1.svlug.org.
<br>
sf-lug.org. 86400 IN NS ns1.svlug.org.
<br>
sf-lug.com. 172800 IN NS ns1.svlug.org.
<br>
sflug.org. 86400 IN NS ns1.svlug.org.
<br>
sflug.com. 172800 IN NS ns1.svlug.org.
<br>
sflug.net. 172800 IN NS ns1.svlug.org.
<br>
sf-lug.net. 172800 IN NS ns1.svlug.org.
<br>
berkeleylug.com. 172800 IN NS ns1.svlug.org.
<br>
# (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)
<br>
#
<br>
<br>
And delegating authority records ...
<br>
removed from:
<br>
balug.org.
<br>
sf-lug.org.
<br>
berkeleylug.com.
<br>
e.9.1.0.5.0.f.1.0.7.4.0.1.0.0.2.ip6.arpa.
<br>
DNS_CK now comes back clean, notwithstanding pending delegating
<br>
authority record deletion:
<br>
<br>
And Al, I presume you will likewise handle the needed for:
<br>
sf-lug.com.
<br>
sflug.org.
<br>
sflug.com.
<br>
sflug.net.
<br>
sf-lug.net.
<br>
<br>
references/excerpts:
<br>
<br>
<blockquote type="cite">Date: Fri, 12 Nov 2021 17:24:51 -0800
<br>
From: Rick Moen <a class="moz-txt-link-rfc2396E" href="mailto:rick@linuxmafia.com"><rick@linuxmafia.com></a>
<br>
To: <a class="moz-txt-link-abbreviated" href="mailto:Michael.Paoli@cal.berkeley.edu">Michael.Paoli@cal.berkeley.edu</a>, [TRIMMED]
<br>
Subject: Notice: ns1.svlug.org downtime, DNS secondary
<br>
<br>
Starting late this morning (2021-11-12), SVLUG was obliged to
<br>
take down for rearchitecting and rebuild its Linode virthost
<br>
<a class="moz-txt-link-abbreviated" href="http://www.svlug.org">www.svlug.org</a> AKA ns1.svlug.org, IP address 64.62.190.98 .
<br>
Downtime will persist for some time. There is no current ETA.
<br>
<br>
_You_ are receiving this (form) e-mail because you are, or have
been a
<br>
DNS admin for one or more of the following domains:
<br>
<br>
balug.org
<br>
berkeleylug.com
<br>
sf-lug.org
<br>
sf-lug.net
<br>
sf-lug.com
<br>
sflug.org
<br>
sflug.net
<br>
sflug.com
<br>
<br>
(Please forward this notice to any DNS sysadmin I've missed.)
<br>
<br>
Please be advised that ns1.svlug.org is NOT, for the time being,
<br>
doing secondary (or any) DNS, so should be removed from rotation
<br>
at the DNS master, effective immediate. (I'd recommend also
<br>
taking it out of the parent zone records at your registrar.)
<br>
<br>
SVLUG will advise when ns1.svlug.org service resumes. We expect
the IP
<br>
to be unchanged.
<br>
<br>
-- Rick Moen
<br>
<a class="moz-txt-link-abbreviated" href="mailto:rick@linuxmafia.com">rick@linuxmafia.com</a>
<br>
(650) 283-7902
<br>
For Silicon Valley Linux User Group
<br>
</blockquote>
<br>
</blockquote>
<br>
</body>
</html>