And, someone that joined, reported that
www.berkeleylug.com wasn't
working, but
berkeleylug.com was working fine.
Poked into it a bit and ... egad, we were missing the IPv4 address
on
www.berkeleylug.com. So, for folks lacking IPv6 it would outright
fail - anyway, added the missing - and all the authoritative
nameservers picked it up in short order.
Negative caching 'n all that - could take up to 24 to 48 hours
to be 100% effective Internet-wide.
$ dig +noall +answer +nottl
www.berkeleylug.com. A
www.berkeleylug.com. AAAA
www.berkeleylug.com. IN A 96.86.170.229
www.berkeleylug.com. IN AAAA 2001:470:1f05:19e::4
$ dig +noall +answer +multiline
berkeleylug.com. SOA
berkeleylug.com. 172800 IN SOA
ns0.berkeleylug.com.
Michael\.
Paoli.cal.berkeley.edu. (
1614188746 ; serial
10800 ; refresh (3 hours)
3600 ; retry (1 hour)
3600000 ; expire (5 weeks 6 days 16 hours)
86400 ; minimum (1 day)
)
$ dig +trace
www.berkeleylug.com.
...
www.berkeleylug.com. 172800 IN A 96.86.170.229
...
;; Received 967 bytes from
2001:470:1f05:19e::4#53(
ns0.berkeleylug.com) in 26 ms
...
$
In any case, for the web,
berkeleylug.com is the canonical,
so http[s]://
www.berkeleylug.com/ will redirect to
https://berkeleylug.com/
(and preserving any path portion)
$ curl -I
http://www.berkeleylug.com/whatever...
HTTP/1.1 301 Moved Permanently
Date: Mon, 01 Mar 2021 00:09:05 GMT
Server: Apache/2.4.38 (Debian)
Location:
https://berkeleylug.com/whatever...
Content-Type: text/html; charset=iso-8859-1
$ curl -I
https://www.berkeleylug.com/whatever...
HTTP/1.1 301 Moved Permanently
Date: Mon, 01 Mar 2021 00:09:07 GMT
Server: Apache/2.4.38 (Debian)
Location:
https://berkeleylug.com/whatever...
Content-Type: text/html; charset=iso-8859-1
$
And, peeking over history (RCS) and such - looks like that was missing for a
long time. Likely got dropped at time of DNS migration off of
Google's DNS. Checking over RCS history, it's
missing back at least as far as 2019-05-07T08:23:45+0000.