<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<font face="Arial">It's not my impression that anyone in the actual
sf-lug meeting group care all that much, so I suppose we could set
these<br>
other domains up or we could for now just ignore them.<br>
I'm certainly willing to slave DNS for them or other domains.<br>
</font><br>
<div class="moz-cite-prefix">On 9/8/2019 17:47, Michael Paoli wrote:<br>
</div>
<blockquote
cite="mid:20190908174701.11653qj13yk0bbwg@webmail.rawbw.com"
type="cite">Well, ... suppose I could set up DNS master &
http[s] redirects ...
<br>
"again" in the case of sf-lug.com ... and
<br>
"new" in the case of sf-lug.net
<br>
Wanna offer DNS slaves for such?
<br>
<br>
... or someone(s) else could do all that and set up suitable
<br>
redirects, ... sf-lug.org thus far still being the canonical 'n
<br>
all that.
<br>
<br>
Let me know how you'd like to proceed.
<br>
<br>
Also, while I'm thinking about DNS slaves, ... looking/hoping for
<br>
some that are more responsive to NOTIFY events than
puck.nether.net.
<br>
Great that puck.nether.net is free and quite available, and
basically
<br>
self-serve to set up, but becomes rather annoying when I'm doing
<br>
DNS verifications for SSL certs, and I'm trying to get all the
relevant
<br>
records into authoritative DNS in sufficiently timely manner.
Also a
<br>
pain when the back-ends of it are effectively "hidden", and I may
see
<br>
most current S/N from its public IPs one moment, and somewhat
older
<br>
zone serial #s and data later from same IP(s) ... so makes it
harder
<br>
to know when it's fully "given up" the older data (short of any
<br>
guarantees on DNS TTLs themselves ... but I've got rather long
<br>
time on the negative caching, so I don't want a "miss" when things
first
<br>
check for those (unique random) DNS entries).
<br>
<br>
<blockquote type="cite">From: "Al Whaley"
<a class="moz-txt-link-rfc2396E" href="mailto:awsflug@sunnyside.com"><awsflug@sunnyside.com></a>
<br>
Subject: Re: Got domains? (sf-lug.{net,com} ...?)
<br>
Date: Sun, 8 Sep 2019 08:17:16 -0700
<br>
</blockquote>
<br>
<blockquote type="cite">Michael,
<br>
Guilty.
<br>
Probably unnecessary, but what the heck.
<br>
Let me know if you have any DNSSEC entries.
<br>
Al
<br>
<br>
On 9/7/2019 21:39, Michael Paoli wrote:
<br>
<blockquote type="cite">Hmmm, got domains?
<br>
<br>
I notice (and somebody else had noticed) ...
<br>
$ whois sf-lug.net | fgrep Date:
<br>
Updated Date: 2019-09-03T23:38:29Z
<br>
Creation Date: 2019-09-03T23:38:28Z
<br>
Registry Expiry Date: 2020-09-03T23:38:28Z
<br>
Updated Date: 2019-09-03T23:38:29Z
<br>
Creation Date: 2019-09-03T23:38:28Z
<br>
Registrar Registration Expiration Date: 2020-09-03T23:38:28Z
<br>
$
<br>
<br>
$ whois sf-lug.com | fgrep Date:
<br>
Updated Date: 2019-09-07T21:52:41Z
<br>
Creation Date: 2019-09-07T18:09:17Z
<br>
Registry Expiry Date: 2020-09-07T18:09:17Z
<br>
Updated Date: 2019-09-07T21:52:40Z
<br>
Creation Date: 2019-09-07T18:09:17Z
<br>
Registrar Registration Expiration Date: 2020-09-07T18:09:17Z
<br>
$
<br>
<br>
references/excerpts:
<br>
whois(1)
<br>
<a class="moz-txt-link-freetext" href="https://www.balug.org/wiki/doku.php?id=sf-lug:resources_etc">https://www.balug.org/wiki/doku.php?id=sf-lug:resources_etc</a>
<br>
</blockquote>
</blockquote>
<br>
</blockquote>
<br>
</body>
</html>