[sf-lug] Domain expiration sf{-, }lug.{org, net, com} ... and renewals and ...

[Michael Paoli]

And/or one can place it on calendar(s) that are actually regularly
looked at, updated, and reviewed.

E.g.:
$ sed -ne '1,/^2020-06/d;/letsencrypt/d;/sf-*lug/p' ~/calendar
2020-07-02 sf-lug.org domain expires 2020-07-02T21:17:47Z (renewed)
2020-09-03 sf-lug.net domain expires 2020-09-03T23:38:28Z (it is  
believed this is set to autorenew at midnight of last day)  
[NON-CANONICAL!]
2020-09-07 sf-lug.com domain expires 2020-09-07T18:09:17Z (it is  
believed this is set to autorenew at midnight of last day)  
[NON-CANONICAL!]
2021-04-06 sflug.org domain expires 2021-04-06T14:09:16Z (it is  
believed this is set to autorenew at midnight of last day)  
[NON-CANONICAL!]
2021-04-11 sflug.com domain expires 2021-04-11T18:20:31Z (it is  
believed this is set to autorenew at midnight of last day)  
[NON-CANONICAL!]
2021-04-11 sflug.net domain expires 2021-04-11T18:20:33Z (it is  
believed this is set to autorenew at midnight of last day)  
[NON-CANONICAL!]
2021-07-02 sf-lug.org domain expires 2021-07-02T21:17:47Z (renewed)
2022-07-02 sf-lug.org domain expires 2022-07-02T21:17:47Z
$

And yeah, sf-lug.org is the canonical and the one we *really* care about.
The others are "nice to have", but not essential.  But regardless,
also, one thing we do NOT want to be doing is willy nilly
dropping / (re)adding domains.  That's a bunch 'o (extra) work best
to be avoided.  So ... policy has also been, uhm, "adjusted" :-)
I'm covering the sf-lug.org domain (and heck, any person or entity
on the planet can also pay for renewal before it expires - most
registrars - including the current - allow that).  Al's covering
the others.  In general though, if domain gets dropped, and that gets
cleaned out of the infrastructure and configurations, kiss it bye-bye,
ain't gonna, atop that, do the work to also add it back in yet again.
So ... essentially, contiguously maintained/renewed - stays ...
otherwise, bye-bye.

https://www.wiki.balug.org/wiki/doku.php?id=sf-lug:resources_etc

> From: "Rick Moen" <rick at linuxmafia.com>
> Subject: [sf-lug] Domain expiration (was: phishy phishy phish Re:  
> Fwd: SF-LUG.COM [PHISH])
> Date: Wed, 29 Jul 2020 21:26:53 -0700

> I wrote:
>
>> So, for example, if worried for any reason about the renewal/experation
>> status of domain sf-lug.com, the sensible thing to do is check
>> the public whois data.
>
> Come to think if it --  y'know -- you could set up a recurring cron job
> to check for you.  Example cron job below relies on an earlier Perl tool
> called domain-check, but Jesse Monroy's d-check, which is actually
> (somewhat) maintained, is a deliberately compatible replacement Perl
> script.
>
> The point is, if you use something like this to get a weekly report
> on which domains out of a set you care about are getting close to
> expiration, you'd immediately know that something like Bobbie's phishing
> fraud e-mail are bullhockey _without_ needing to manually check whois.
>
>
> https://github.com/jessemonroy650/d-check
> http://linuxmafia.com/pub/linux/network/domains-test
>
> :r /etc/cron.weekly/domain-check
>
> #! /bin/sh
>
> # domain-check	Cron script to check domain expirations.
> #
> #		This is a pitifully primitive cron script to invoke domain-check
> #		by Ben Okopnik ( ben at linuxgazette.net ) against lists
> #		of domains in /usr/local/share.  A better replacement
> #		would notify a list of appropriate persons for each
> #		domain, rather than just Rick Moen.
> #
> #		Written by Rick Moen (rick at linuxmafia.com)
> #		$Id: cron.weekly,v 1.01 2007/07/02 21:03:05 rick
>
> set -o errexit  #aka "set -e": exit if any line returns non-true value
> set -o nounset  #aka "set -u": exit upon finding an uninitialised variable
>
> test -e /usr/local/share/domains || exit 0
> test -x /usr/local/bin/domain-check || exit 0
>
>
> /usr/local/bin/domain-check -w -e=rick at linuxmafia.com  -x=90  
> -F=/usr/local/share/domains