[sf-lug] sf-lug domain expirations 2014-07-02 (& [www.]sf-lug.balug.org)

Michael Paoli Michael.Paoli at cal.berkeley.edu
Tue Jul 8 00:00:41 PDT 2014


Hmmmm...

$ TZ=GMT0 date --rfc-3339=seconds; (for tld in org com; do  
d=sf-lug."$tld"; echo "$d:"; 2>&1 whois -H "$d" | grep -i -e  
'^reg.*expir.*date:' -e '^registrant name' -e ' *name server: *[^ ]';  
done)
2014-07-08 06:45:26+00:00
sf-lug.org:
Registry Expiry Date: 2015-07-02T21:17:47Z
Registrant Name:Pending Renewal or Deletion
Name Server:NS1.PENDINGRENEWALDELETION.COM
Name Server:NS2.PENDINGRENEWALDELETION.COM
sf-lug.com:
    Name Server: NS1.PENDINGRENEWALDELETION.COM
    Name Server: NS2.PENDINGRENEWALDELETION.COM
Registrar Registration Expiration Date: 2014-07-02T00:00:00Z
Registrant Name: Pending Renewal or Deletion
Name Server: NS1.PENDINGRENEWALDELETION.COM
Name Server: NS2.PENDINGRENEWALDELETION.COM
$

At first when I saw the updated Registry Expiry Date I was thinking it
had been handled, but alas, not all squared away yet as far as I can
tell.

And in case anyone may find it useful, I did, prior to expiration of
sf-lug.{org,com} create DNS entries for [www.]sf-lug.balug.org. for sf-lug,
uh "just in case"*, so, one can use as work-around, e.g.:
http://www.sf-lug.balug.org/
http://sf-lug.balug.org/
And of course webmaster and/or sysadmin of sf-lug can always
redirect (e.g. HTTP 301) from any potentially non-canonical to,
e.g. http://www.sf-lug.org/
... but that might be much more useful later, when DNS for
www.sf-lug.org. goes somewhere that's quite to one's liking.

*was earlier going to be in the midst of some upgrades:
http://linuxmafia.com/pipermail/sf-lug/2014q3/010562.html
and didn't want some domain expiration(s) to potentially make that
significantly more inconvenient/complex, so, dropped in some
"just in case" DNS entries - and have thus far left them there.

> From: "Michael Paoli" <Michael.Paoli at cal.berkeley.edu>
> Subject: Fwd: sf-lug domain expirations 2014-07-02
> Date: Sat, 28 Jun 2014 23:20:30 -0700

> Hopefully this will be getting taken care of "soon enough",
> but I can't help but notice.
>
> May depend somewhat upon registrar, but in general letting a domain
> expire that one wishes to keep active is not a good thing.
> Also, not sure if domains renewed necessarily reflect the renewal
> "immediately" in the whois data, but I'd think that would show in
> relatively short order in any case.
>
> $ TZ=GMT0 date --rfc-3339=seconds; (for tld in org com; do  
> d=sf-lug."$tld"; echo "$d:"; 2>&1 whois -H "$d" | grep -i  
> '^reg.*expir.*date:'; done)
> 2014-06-29 06:13:53+00:00
> sf-lug.org:
> Registry Expiry Date: 2014-07-02T21:17:47Z
> sf-lug.com:
> Registrar Registration Expiration Date: 2014-07-02T00:00:00Z
> $
>
> ----- Forwarded message from Michael.Paoli at cal.berkeley.edu -----
>     Date: Fri, 27 Jun 2014 03:23:46 -0700
>     From: "Michael Paoli" <Michael.Paoli at cal.berkeley.edu>
>  Subject: sf-lug domain expirations 2014-07-02
>       To: "Jim Stockford" <jim at well.com>
>
> Jim,
>
> FYI, don't forget, these should be taken care of soon:
>
> sf-lug domain expirations 2014-07-02:
> $ (for tld in org com; do d=sf-lug."$tld"; echo "$d:"; 2>&1 whois -H  
> "$d" | grep -i 'expir.*date:'; done)
> sf-lug.org:
> Registry Expiry Date: 2014-07-02T21:17:47Z
> sf-lug.com:
>    Expiration Date: 02-jul-2014
> Registrar Registration Expiration Date: 2014-07-02T00:00:00Z
> $
>
>
> ----- End forwarded message -----





More information about the sf-lug mailing list