[sf-lug] And then there were 5: SFLUG.NET, SFLUG.COM, SFLUG, ORG, SF-LUG.COM, SF-LUG.ORG: Re: SFLUG.COM Re: SFLUG.[...] Re: SFLUG.org

[Michael Paoli]

Uhm, are we done adding domains for a while now, or ... are we gonna pick up
yet more?  SF-LUG.NET also seems available, but I don't know that Jim
specifically suggested that ... nor up to how many domains he's willing
to be reimbursing folks for.
http://linuxmafia.com/pipermail/sf-lug/2019q2/013999.html
Sounds like we've already (slightly) more than covered the domains Jim was
specifically referencing.

Anyway, master now available for not only sflug.org.
but also now sflug.com. and sflug.net.:
ns1.sf-lug.org.:
198.144.194.238
2001:470:1f04:19e::2
Not sure where the slaves may be in the process.
Rick - if you want to coordinate with Al, you do also have access to
edit those zone masters:
balug-sf-lug-v2.balug.org
User rick may run the following commands on balug-sf-lug-v2:
     (root) sudoedit /etc/bind/master/sflug.org
     (root) /usr/sbin/rndc reload sflug.org
     (root) /usr/sbin/rndc notify sflug.org
     (root) sudoedit /etc/bind/master/sflug.com
     (root) /usr/sbin/rndc reload sflug.com
     (root) /usr/sbin/rndc notify sflug.com
     (root) sudoedit /etc/bind/master/sflug.net
     (root) /usr/sbin/rndc reload sflug.net
     (root) /usr/sbin/rndc notify sflug.net
E.g. if Al wants to provide additional slave(s) - and maybe we don't
want to "pester" Aaron to add slave(s) for yet 2 more domains.
I was also thinking we might want to (also) use puck.nether.net.
for slave services on some of these domains.

Note also: Webserver knows about sflug.org, but thus far knows nothing
about sflug.com nor sflug.net.
Also DNSSEC ... the zones are set up for that ... for the newer ones,
notably sflug.com and sflug.net - we'll want to wait a bit before
putting in the (DS) delegation data for that - notably TTLs - want any
negative caching, etc. to first expire, lest we bust DNSSEC by putting
it in "too fast".
Anyway, it's set up with BIND9's in-line signing - so serials served by
DNS may be slightly ahead of what's in master zone files,
and one should use seconds since the epoch - that's how I have bind
configured to sign 'em.  The masters also generally have handy bit 'o
comment around that: date +%s
With GNU date, that'll get 'ya seconds since the epoch.

> From: Al <awsflug at sunnyside.com>
> Subject: Re: [sf-lug] SFLUG.COM Re: SFLUG.[...] Re: SFLUG.org
> Date: Fri, 12 Apr 2019 08:00:22 -0700

> FYI I've set sflug.{org,net,com} into a group.
>
> On 4/12/2019 07:47, Michael Paoli wrote:
>> Rick - thanks on the offers.
>>
>> Added to the "queue" ... but my queue overfloweth, and it will never
>> /all/ get done.  I'll likely pick it up sometime after SFLUG.ORG
>> has actually been delegated and/or after when I've gotten some
>> higher priority BerkeleyLUG.com tasks moved further along.
>>
>> In the meantime, I don't see any particular need to rush on SFLUG.COM ...
>> it's not like something used significantly - or even at all - by
>> SF-LUG suddenly broke and needs fixin', or there's been some great
>> need to SFLUG.COM operational for SF-LUG.  Anyway, shall get around
>> to it, ... just may take a bit (later this month?  next month?).
>>
>>> From: "Rick Moen" <rick at linuxmafia.com>
>>> Subject: Re: [sf-lug] SFLUG.COM Re: SFLUG.[...] Re:  SFLUG.org
>>> Date: Thu, 11 Apr 2019 23:23:50 -0700
>>
>>> Quoting Michael Paoli (Michael.Paoli at cal.berkeley.edu):
>>>
>>>> And ... I'm guestimating Al has snapped up SFLUG.COM.
>>> [...]
>>>> Yep:
>>>> Registrant Name: Al Whaley
>>>
>>> Well, same secondary DNS offer is on the plate:  Let me know when/if
>>> ns1.linuxmafia.com and ns1.svlug.org can AXFR it, and I'll set that up
>>> in a flash.  Assuming you want.