[sf-lug] Notice: ns1.svlug.org downtime, DNS secondary

[Al]

You're right - apparently godaddy has a bug - I'm on hold now.

FYI: I don't control sf-lug.com, but I do the other ones.

On 11/13/2021 20:35, Michael Paoli wrote:
> It's the delegating authority NS records ... still there:
>
> echo 'sf-lug.com.
> sflug.org.
> sflug.com.
> sflug.net.
> sf-lug.net.' | (
>   IFS_=".$IFS";
>   while IFS="$IFS_" read subdomain TLD
>   do
>     Authority_NS="$(dig +short "$TLD". NS | head -n 1)"
>     Authority_NS_IP="$(dig +short "$Authority_NS" A "$Authority_NS" 
> AAAA | head -n 1)"
>     dig @"$Authority_NS_IP" +noall +authority +norecurse 
> "$subdomain.$TLD." | fgrep -i svlug &&
>     whois "$subdomain.$TLD" | sed -e '/^ *Registrar: /!d;s/^ *//;p' | 
> sort -u
>   done
> )
> sf-lug.com.             172800  IN      NS      ns1.svlug.org.
> Registrar: Wild West Domains, LLC
> sflug.org.              86400   IN      NS      ns1.svlug.org.
> Registrar: GoDaddy.com, LLC
> sflug.com.              172800  IN      NS      ns1.svlug.org.
> Registrar: GoDaddy.com, LLC
> sflug.net.              172800  IN      NS      ns1.svlug.org.
> Registrar: GoDaddy.com, LLC
> sf-lug.net.             172800  IN      NS      ns1.svlug.org.
> Registrar: GoDaddy.com, LLC
>
>> From: Al <awsflug at sunnyside.com>
>> Subject: Re: [sf-lug] Notice: ns1.svlug.org downtime, DNS secondary
>> Date: Sat, 13 Nov 2021 14:24:03 -0800
>
>> Hmm, yes, forgot about those.
>>
>> Probably no one uses those aliases for sf-lug but hey, when you're 
>> right, you're right.
>> the glue records are history.
>>
>>
>> On 11/13/2021 12:16, Michael Paoli wrote:
>>> http://linuxmafia.com/pipermail/sf-lug/2021q4/015438.html
>>>
>>>> From: Al <awsflug at sunnyside.com>
>>>> Date: 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.
>>>
>>> Al,
>>>
>>> SF-LUG's non-canonical names have NS delegating authority records
>>> that include ns1.svlug.org.  Perhaps not critical, but would be
>>> best to remove those records for now - would reduce DNS latency and
>>> possibly other issues, e.g. lame response before ns1.svlug.org. is
>>> slave/secondary again but after it's again a DNS server on The 
>>> Internet.
>>>
>>> Those records would be controlled via the registrar, I believe Go Daddy
>>> in this case, where I believe you have access and I don't.
>>> Notably these domains:
>>> sf-lug.com.
>>> sflug.org.
>>> sflug.com.
>>> sflug.net.
>>> sf-lug.net.
>>>
>>> echo 'sf-lug.com.
>>> sflug.org.
>>> sflug.com.
>>> sflug.net.
>>> sf-lug.net.' | (
>>>   IFS_=".$IFS";
>>>   while IFS="$IFS_" read subdomain TLD
>>>   do
>>>     Authority_NS="$(dig +short "$TLD". NS | head -n 1)"
>>>     Authority_NS_IP="$(dig +short "$Authority_NS" A "$Authority_NS" 
>>> AAAA | head -n 1)"
>>>     dig @"$Authority_NS_IP" +noall +authority +norecurse 
>>> "$subdomain.$TLD." | fgrep -i svlug &&
>>>     whois "$subdomain.$TLD" | sed -e '/^ *Registrar: /!d;s/^ *//;p' 
>>> | sort -u
>>>   done
>>> )
>>>
>>> sf-lug.com.             172800  IN      NS      ns1.svlug.org.
>>> Registrar: Wild West Domains, LLC
>>> sflug.org.              86400   IN      NS      ns1.svlug.org.
>>> Registrar: GoDaddy.com, LLC
>>> sflug.com.              172800  IN      NS      ns1.svlug.org.
>>> Registrar: GoDaddy.com, LLC
>>> sflug.net.              172800  IN      NS      ns1.svlug.org.
>>> Registrar: GoDaddy.com, LLC
>>> sf-lug.net.             172800  IN      NS      ns1.svlug.org.
>>> Registrar: GoDaddy.com, LLC
>>>
>>> Al - myself, you, and Jim* have access to sf-lug.org. at the registrar.
>>> * though Jim Stockford's access is a bit limited to avoid possibly
>>>   irreversable booboos - e.g. can change DNS, but can't transfer away
>>>   the domain or change its contacts.
>>>
>>>> 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! :) )
>>>
>>> Alas, Comcast Business isn't nearly as rock solid as Raw Bandwidth was.
>>> I typically get as much outage in 3 months from Comcast Business,
>>> typically an outage of about 3 hours once a month, plus some quite 
>>> brief
>>> outages on a more frequent basis, than I got from Raw Bandwidth in 13
>>> years - about one outage of about 8 hours, and very rarely any other
>>> outages, and those others quite rare, generally very short, typically
>>> well under 15 minutes.
>>> E.g. latest:
>>> 2021-11-09
>>> ISP: Comcast Business Outage, starting around:
>>> PING: ping 8.8.8.8 FAILED 2021-11-09T05:44:38+00:00
>>> ...
>>> connectivity back starting around:
>>> 2021-11-09T08:35:58+00:00
>>>
>>>> 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.
>>>
>>> Well, there's lots in/with DNS that can be checked, including,
>>> e.g. data consistency (like do NS authority and authoritative records
>>> match) and RFC compliance, much etc.
>>>
>>> http://linuxmafia.com/pipermail/sf-lug/2021q4/015437.html
>>>> On 11/13/2021 01:30, Michael Paoli wrote:
>>>>>
>>>>> 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.
>>>>>
>>>>> And Al, I presume you will likewise handle the needed for:
>>>>> sf-lug.com.
>>>>> sflug.org.
>>>>> sflug.com.
>>>>> sflug.net.
>>>>> sf-lug.net.
>