[sf-lug] Bye-bye sf-lug.info., sf-lug.org remains canonical (and sf-lug.com non-canonical alternate)

[Michael Paoli]

And, looks like Network Solutions / Web.com has pulled the plug
on sf-lug.info, so I'll rip out those related infrastructure
bits rather soon.

references/excerpts:
$ dig -t NS sf-lug.info. +trace | grep -i '^sf-lug\.info\.'
sf-lug.info.            86400   IN      NS       
ns1.pendingrenewaldeletion.com.
sf-lug.info.            86400   IN      NS       
ns2.pendingrenewaldeletion.com.
$

> From: "Michael Paoli" <Michael.Paoli at cal.berkeley.edu>
> Subject: Re: Bye-bye sf-lug.info., sf-lug.org remains canonical (and  
> sf-lug.com non-canonical alternate)
> Date: Thu, 29 Sep 2016 08:35:05 -0700

> So ... auto-renew grace period, etc.
> Looks like for .com, it probably goes
> 30 30 5
> Auto-Renew/Expired Grace Period
> Redemption Grace Period
> Pending Delete
> respectively, in days.
> Icann show 0-45 days for Auto-Renew Grace Period ... but looks
> (from what I see of quick searches on .com) that it's probably
> exactly 30 days for com TLD.
> So ... sf-lug.info. ... we watch it wither away in about 30 (35 to 80) days.
> I'll probably rip out SF-LUG's related infrastructure bits a
> little bit after registrar is no longer delegating that DNS
> to us - at which point it's pretty well on its way to being
> fully dead for us.
>
>> From: "Michael Paoli" <Michael.Paoli at cal.berkeley.edu>
>> Subject: Bye-bye sf-lug.info., sf-lug.org remains canonical (and  
>> sf-lug.com non-canonical alternate)
>> Date: Wed, 28 Sep 2016 23:39:21 -0700
>
>> So, yes, per earlier communications, we say bye-bye to
>> sf-lug.info. - something Web.Com / Network Solutions gave us that we didn't
>> ask for and didn't particularly want anyway.  From my calendar:
>> 2016-09-28 sf-lug.info domain expires 2016-09-28T20:01:47Z
>> $ (for ns in $(dig -t NS info. +short); do dig +noall +norecurse  
>> +authority @"$ns" -t ANY sf-lug.info.; done) | sort -u
>> sf-lug.info.            86400   IN      NS      ns1.sf-lug.info.
>> sf-lug.info.            86400   IN      NS      ns2.he.net.
>> sf-lug.info.            86400   IN      NS      ns3.he.net.
>> sf-lug.info.            86400   IN      NS      ns4.he.net.
>> sf-lug.info.            86400   IN      NS      ns5.he.net.
>> $
>> Okay, so it's not been fully killed yet, but ...
>> and peeking at whois(1) - it's the regular registrar auto-renew
>> shenanigans ... they do that effectively upstream, and can
>> revocably do it ... for a while, ... so they do, ... then they hope,
>> while they have a (strangle)hold on the domain for a bit, they try to
>> extort money out of "old" customer, or sell it off at a premium to new ...
>> but they can only do that for so long ... then they have to either pay up,
>> or give it up - and they generally do the latter (unless someone else is
>> beating their doors down for the domain).
>> And checking the web.com/networksolutions.com account, it shows as
>> expired, and not set to auto-renew ... so we'll just wait 'em out
>> and let that one wither on the vine ... then I'll rip out it's bit
>> of infrastructure (DNS slaves and master, web virtual name hosting,
>> SSL certs I'll just (not) deal with for [*.]sf-lug.info as those come
>> up for renewal ... and that'll be 'bout it.
>> So, ... since it's not (quite) dead yet ... I'll just wait bit longer
>> and rip out those infrastructure bits a little later (and doesn't hurt
>> much if they're cleaned up a bit after the domain does it's final  
>> bye-bye ...
>> but do want to clean that out and not leave that cruft around too long).
>>
>> references/excerpts:
>> http://linuxmafia.com/pipermail/sf-lug/
>> http://linuxmafia.com/pipermail/sf-lug/2016q1/011617.html
>> http://linuxmafia.com/pipermail/sf-lug/2016q1/011612.html
>>
>>> From: "Michael Paoli" <Michael.Paoli at cal.berkeley.edu>
>>> To: "Jim Stockford" <jim at well.com>
>>> Cc: sf-lug at linuxmafia.com
>>> Subject: Re: after I get the domain names over to Joker
>>> Date: Sat, 02 Jan 2016 11:03:32 -0800
>>
>>> Jim,
>>>
>>> and as for sf-lug.info - I think we can quite safely just let that  
>>> one expire
>>> 2016-09-28T20:01:47Z, unless you and/or other(s) want to pay to  
>>> hang onto it to
>>> merely prevent anyone else from snagging the sf-lug.info domain.