[sf-lug] sf-lug.{com,info} --> www.sf-lug.org (canonical)

[jim]

     This sf-lug.info name is bothersome. I'm reasonably
sure that I never made such a thing. I'm not sure that
some other person did not use the netsol account to
make it--I gravely doubt it, but can't say absolutely.
     There is no need for sf-lug.info.
     Your take on sf-lug.{org,com} reflects our early
discussions: use both because
* to protect the sf-lug name from someone co-opting
   a .com version
* to permit careless and ignorant people to access the
   site (assuming some people think of web sites as ending
   with .com in all cases (as one person explained to me:
   "'.com' means 'amen'".

     I agree with you and Rick
* never use auto renew
* get away from netsol asap
     The problem I had was that I tried: called netsol and
explained I wanted to move the names to consolidate all
my domain names under joker.com and could they please
unlock the names for transfer, I notified joker to get
the names. Joker (much) later replied that they could not.
Netsol very soon after sent me notice that the domains
were to expire. Somewhere in that history I paid another
bunch of money to netsol, which then informed me that my
domains were due to expire....
     I got discouraged (again).



On 01/02/2016 06:09 AM, Michael Paoli wrote:
> Jim,
>
> And at least that bit is mostly* done.
>
> These domains:
> [www.][ipv6.]sf-lug.info
> now* do 301 ("permanent") redirect to
> www.[ipv6.]sf-lug.org
> (the ipv6. portion, if present, is preserved,
> the [www.]ipv6.sf-lug.{org,com,info} being IPv6 only (no A records)).
>
> *DNS changes are still percolating through expiration of TTLs -
> should be 100% effective within a few days or less - I'll leave what 
> does/doesn't
> fully work yet, and from where, as an exercise for the curious.
>
> If after 72 hours, any of what's described above in this email appears 
> not to be
> fully operational on The Internet at large, feel free to let me know 
> (preferably on
> list), and I'll have a look (but I'm not here to troubleshoot anyone 
> and everyone's
> much more localized problems).
>
> I've also similarly set up
> [www.][ipv6.]sf-lug.com --> www.[ipv6.]sf-lug.org
>
> So canonical domain is sf-lug.org, with www.[ipv6.]sf-lug.org for web 
> site.
>
> We can simply *not* renew the sf-lug.info when it expires - not much 
> value to
> having it, but so long as it's there - well, might as well redirect it 
> somewhere
> useful.
>
> sf-lug.org presumably will be renewed in perpetuity :-) ... but after 
> moving registrars.
>
> sf-lug.com ?  Judgement call.  Doesn't hurt much to keep it, but 
> longer term, probably
> not essential (unless one really wants to prevent someone else from 
> grabbing the
> sf-lug.com domain name) - but short to medium term, probably best to 
> keep it around
> a while, as sf-lug.com and sf-lug.org have both been used alot, 
> without either
> being particularly set as canonical (though sf-lug.org, as I'd 
> mentioned earlier
> has both longer history, and is also more what folks would expect for a
> Linux User Group, as opposed to .com).
>
> Oh, and sf-lug.org will probably always get one to www.sf-lug.com, but 
> for web,
> www.sf-lug.org is the proper canonical.
>
> Also, don't have a proper SSL cert for the sf-lug.info domains yet, 
> but probably will
> also get around to that, to cover the bases.  sf-lug.org (and 
> sf-lug.com) have proper
> SSL certs - at least for the https domain names that are reasonably 
> legitimate
> https access names.
>
> references/excerpts:
>
> $ (domain=sf-lug; for www in 'www.' ''; do for ipv6 in '' 'ipv6.'; do 
> for tld in org com; do h="$www$ipv6$domain.$tld"; echo "$h" $(curl 
> --silent -I http://"$h"/ | sed -ne 's/^M$//;s/^HTTP\/[^ ]* 
> \([0-9][0-9]*\) .*/\1/p;s/^Location: \(..*\)$/\1/p'); done; done; done)
> www.sf-lug.org 200
> www.sf-lug.com 301 http://www.sf-lug.org/
> www.ipv6.sf-lug.org 200
> www.ipv6.sf-lug.com 301 http://www.ipv6.sf-lug.org/
> sf-lug.org 301 http://www.sf-lug.org/
> sf-lug.com 301 http://www.sf-lug.org/
> ipv6.sf-lug.org 301 http://www.ipv6.sf-lug.org/
> ipv6.sf-lug.com 301 http://www.ipv6.sf-lug.org/
> $ (domain=sf-lug; for www in 'www.' ''; do for ipv6 in '' 'ipv6.'; do 
> for tld in info; do h="$www$ipv6$domain.$tld"; echo "$h" $(curl 
> --insecure --silent -I http://"$h"/ | sed -ne 's/^M$//;s/^HTTP\/[^ ]* 
> \([0-9][0-9]*\) .*/\1/p;s/^Location: \(..*\)$/\1/p'); done; done; done)
> www.sf-lug.info 301 http://www.sf-lug.org/
> www.ipv6.sf-lug.info 301 http://www.ipv6.sf-lug.org/
> sf-lug.info 301 http://www.sf-lug.org/
> ipv6.sf-lug.info 301 http://www.ipv6.sf-lug.org/
> $
>
>> From: jim <jim at well.com>
>> Subject: Re: sf-lug.info
>> Date: Fri, 1 Jan 2016 18:24:55 +0000
>
>>     Thanks. I don't recall creating sf-lug.info, but
>> a lot has happened, and I've shared the work with
>> anyone who wanted to chip in and learn or teach.
>>     I agree that sf-lug.org should be the cannonical
>> referencve. Originally we agreed on sf-lug.{org,com,net}
>> so's to protect the name from malicious or confusing
>> uses by others-not-us. We stopped paying for the .net
>> name.
>>
>>
>> On 12/31/2015 06:54 AM, Michael Paoli wrote:
>>> Jim,
>>>
>>> I notice you also have sf-lug.info owned by you and on the
>>> Network Solutions / Web.com account.  Do you want to have that set 
>>> up to
>>> redirect to sf-lug.org (or .com)?  Looks like that was your intent:
>>>
>>> Web forwarding is:  On
>>> Visitors to:
>>> http://www.sf-lug.info
>>> Should be forwarded to this destination URL:
>>> http://www.SF-LUG.COM
>>>
>>> But it appears to just be an advertising parking page, apparently for
>>> lack of completion of validation step(s).
>>>
>>> I think I'd still recommend www.sf-lug.org as the canonical,
>>> as folks more generally expect .org for a LUG, rather than .com or 
>>> .info
>>> sf-lug.org has also been around longer than sf-lug.com.
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://linuxmafia.com/pipermail/sf-lug/attachments/20160102/b789ec06/attachment.html>