[sf-lug] 2020-04 sflug.{org,com,net} expirations
Michael Paoli
Michael.Paoli at cal.berkeley.edu
Fri Mar 27 20:57:51 PDT 2020
Well, sorry, I probably could've worded that better.
Let's see if this helps make it sufficiently clear.
Most of the work is change. Notably dropping domain(s),
or adding domain(s) ... or the especially frustrating annoyance of
dropping and readding.
So, the non-canonicals, I don't really care if you keep 'em or
not ... not my $$. But if they get dropped, I have to do the work
of dropping 'em from the infrastructure. And if I end up needing to
do that, I'm probably going to be unwilling to do the work to
readd them (e.g as sf-lug.com was earlier dropped ... then readded).
So, ... if it drops, I drop it ... but I'm probably not willing to
readd a domain that's dropped - that's a whole lot 'o
drop/add work that's not worth my time/resources/energy for a whole
LUG that can't manage to spend like about ~$14.00 USD or so per year
per domain to avoid having me do all that otherwise unnecessary work.
So ... hopefully that's more clear. It's the drop and/or add that's
most of the work (and especially if it's both). I.e. the change -
that's the work.
http://linuxmafia.com/pipermail/sf-lug/2020q1/014640.html
> From: jim <jim at well.com>
> Subject: Re: [sf-lug] 2020-04 sflug.{org,com,net} expirations
> Date: Fri, 27 Mar 2020 13:35:39 -0700
> anybody got opinions?
> Keep or drop? Michael suggests either way
> means work for him.
> If I recall rightly, sf-lug.org is the
> canonical domain name. sflug.org (and
> sflug.com and sflug.net) are there as
> a matter of convenience for possible
> spelling confusion (e.g. someone looking
> for a lug in san francisco).
>
>
> On 3/27/20 6:12 AM, Michael Paoli wrote:
>> 2020-04 sflug.{org,com,net} expirations
>> My calendar and whois(1) tells me:
>> 2020-04-06 sflug.org domain expires 2020-04-06T14:09:16Z
>> 2020-04-11 sflug.com domain expires 2020-04-11T18:20:31Z
>> 2020-04-11 sflug.net domain expires 2020-04-11T18:20:33Z
>> $ (for d in sflug.{org,com,net}; do echo "$d:"; whois "$d" 2>&1 |
>> grep -i 'expir.*20[0-9][0-9]-'; done)
>> sflug.org:
>> Registry Expiry Date: 2020-04-06T14:09:16Z
>> sflug.com:
>> Registry Expiry Date: 2020-04-11T18:20:31Z
>> Registrar Registration Expiration Date: 2020-04-11T18:20:31Z
>> sflug.net:
>> Registry Expiry Date: 2020-04-11T18:20:33Z
>> Registrar Registration Expiration Date: 2020-04-11T18:20:33Z
>> $
>>
>> So ... these are non-canonical. Doesn't particularly matter to me if
>> they're kept or dropped, but each such action ends up involving a fair
>> bit 'o work on my end. So ... don't be willy-nilly doing drops/adds.
>> If I drop 'em from "my" infrastructure (and DNS slaves, etc.) - a fair
>> bit 'o work, I may not be willing to readd them (which would be yet
>> again a fair bit 'o work). And when would I drop 'em from "my"
>> infrastructure? Anytime after registrar DNS delegation is no longer
>> functioning - at that point the domains become non-functional and much
>> more of a liability and pain than anything else.
More information about the sf-lug
mailing list