<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<font face="Arial">Hmm, yes, forgot about those.<br>
<br>
Probably no one uses those aliases for sf-lug but hey, when you're
right, you're right.<br>
the glue records are history.<br>
<br>
</font><br>
<div class="moz-cite-prefix">On 11/13/2021 12:16, Michael Paoli
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:20211113121636.13234evr5lw8moe8@webmail.rawbw.com"><a class="moz-txt-link-freetext" href="http://linuxmafia.com/pipermail/sf-lug/2021q4/015438.html">http://linuxmafia.com/pipermail/sf-lug/2021q4/015438.html</a>
<br>
<br>
<blockquote type="cite">From: Al <a class="moz-txt-link-rfc2396E" href="mailto:awsflug@sunnyside.com"><awsflug@sunnyside.com></a>
<br>
Date: Sat Nov 13 08:59:37 PST 2021
<br>
<br>
I don't think I'm directly affected by svlug being down since I
don't
<br>
AXFR from ns1.svlug, and I don't originate any records that
define svlug
<br>
to be a domain server, but good to know what's going on.
<br>
</blockquote>
<br>
Al,
<br>
<br>
SF-LUG's non-canonical names have NS delegating authority records
<br>
that include ns1.svlug.org. Perhaps not critical, but would be
<br>
best to remove those records for now - would reduce DNS latency
and
<br>
possibly other issues, e.g. lame response before ns1.svlug.org. is
<br>
slave/secondary again but after it's again a DNS server on The
Internet.
<br>
<br>
Those records would be controlled via the registrar, I believe Go
Daddy
<br>
in this case, where I believe you have access and I don't.
<br>
Notably these domains:
<br>
sf-lug.com.
<br>
sflug.org.
<br>
sflug.com.
<br>
sflug.net.
<br>
sf-lug.net.
<br>
<br>
echo 'sf-lug.com.
<br>
sflug.org.
<br>
sflug.com.
<br>
sflug.net.
<br>
sf-lug.net.' | (
<br>
IFS_=".$IFS";
<br>
while IFS="$IFS_" read subdomain TLD
<br>
do
<br>
Authority_NS="$(dig +short "$TLD". NS | head -n 1)"
<br>
Authority_NS_IP="$(dig +short "$Authority_NS" A
"$Authority_NS" AAAA | head -n 1)"
<br>
dig @"$Authority_NS_IP" +noall +authority +norecurse
"$subdomain.$TLD." | fgrep -i svlug &&
<br>
whois "$subdomain.$TLD" | sed -e '/^ *Registrar: /!d;s/^
*//;p' | sort -u
<br>
done
<br>
)
<br>
<br>
sf-lug.com. 172800 IN NS ns1.svlug.org.
<br>
Registrar: Wild West Domains, LLC
<br>
sflug.org. 86400 IN NS ns1.svlug.org.
<br>
Registrar: GoDaddy.com, LLC
<br>
sflug.com. 172800 IN NS ns1.svlug.org.
<br>
Registrar: GoDaddy.com, LLC
<br>
sflug.net. 172800 IN NS ns1.svlug.org.
<br>
Registrar: GoDaddy.com, LLC
<br>
sf-lug.net. 172800 IN NS ns1.svlug.org.
<br>
Registrar: GoDaddy.com, LLC
<br>
<br>
Al - myself, you, and Jim* have access to sf-lug.org. at the
registrar.
<br>
* though Jim Stockford's access is a bit limited to avoid possibly
<br>
irreversable booboos - e.g. can change DNS, but can't transfer
away
<br>
the domain or change its contacts.
<br>
<br>
<blockquote type="cite">I wasn't monitoring ping status for svlug
but I've added it to the
<br>
list. Historically I monitor balug and linuxmafia. (linuxmafia
stays
<br>
up just all the time! :) )
<br>
</blockquote>
<br>
Alas, Comcast Business isn't nearly as rock solid as Raw Bandwidth
was.
<br>
I typically get as much outage in 3 months from Comcast Business,
<br>
typically an outage of about 3 hours once a month, plus some quite
brief
<br>
outages on a more frequent basis, than I got from Raw Bandwidth in
13
<br>
years - about one outage of about 8 hours, and very rarely any
other
<br>
outages, and those others quite rare, generally very short,
typically
<br>
well under 15 minutes.
<br>
E.g. latest:
<br>
2021-11-09
<br>
ISP: Comcast Business Outage, starting around:
<br>
PING: ping 8.8.8.8 FAILED 2021-11-09T05:44:38+00:00
<br>
...
<br>
connectivity back starting around:
<br>
2021-11-09T08:35:58+00:00
<br>
<br>
<blockquote type="cite">I check BIND status every 10 minutes but
haven't seen any transfers
<br>
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
<br>
change in zones I was seconding but, since that's a normal
function I do
<br>
for internal zones, it was easy to add that; because I hadn't
been
<br>
checking I didn't see the list of name servers change. Next time
I will.
<br>
</blockquote>
<br>
Well, there's lots in/with DNS that can be checked, including,
<br>
e.g. data consistency (like do NS authority and authoritative
records
<br>
match) and RFC compliance, much etc.
<br>
<br>
<a class="moz-txt-link-freetext" href="http://linuxmafia.com/pipermail/sf-lug/2021q4/015437.html">http://linuxmafia.com/pipermail/sf-lug/2021q4/015437.html</a>
<br>
<blockquote type="cite">On 11/13/2021 01:30, Michael Paoli wrote:
<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>
>
<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>
</blockquote>
<br>
</blockquote>
<br>
</body>
</html>