[sf-lug] Domain administration (broken WHOIS)
Michael Paoli
Michael.Paoli at cal.berkeley.edu
Mon Apr 8 12:54:32 PDT 2019
Yep, ... I'd be okay with that (what Rick suggests/outlines below).
Would also be good to have a "dump" of any existing sflug.org DNS data
(could make transition slightly smoother ... not that it matters all that
much in this case).
GoDaddy ... I'd guestimate by default they might'a set it up with a
"parking" page or the like? In any case, whatever's in DNS might be
slightly (or more?) useful to have dump of that data (e.g. could avoid
an RFC violating serial # jump on zone, or avoid "mystery" issues over
longer TTLs that are/were in effect but subsequently "unknown" - yet
cached elsewhere in DNS).
Note also, *some* registrars won't let one point to new nameservers,
until they're operational ... but for GoDaddy & .org, I doubt they
care/check (among my experience de. is about the most persnickety of
registrars ... that exacting German engineering :-) (if everybody's
DNS adhered to what de. requires, DNS would be a lot cleaner and
more robust).
> From: "Rick Moen" <rick at linuxmafia.com>
> Subject: Re: [sf-lug] Domain administration (broken WHOIS)
> Date: Sun, 7 Apr 2019 22:44:09 -0700
> Quoting Al (awsflug at sunnyside.com):
>
>> sflug.org - Rick mentioned that it was available so I grabbed it.
>> I've learned not to wait on those things - it often doesn't end
>> well. Now I'll just sit back and listen to the conversation and wait and
>> see if anyone actually wants to use it. I don't need to own it.
>> I can also "point" it somewhere.
>
> (I see from the current WHOIS that you're Al Whaley of Palo Alto, and on
> reflection I remember we've spoken before. Hullo again.)
>
>
> Al, here's what I recommend to move this along:
>
> Go into Web-based administration for your new domain at GoDaddy, and
> redefine what DNS nameservers are authoritative. Currently, those are
> four of your nameservers:
>
> $ whois sflug.org | grep 'Name Server'
> Name Server: NS0.SUNNYSIDE.COM
> Name Server: NS1.SUNNYSIDE.COM
> Name Server: NS2.SUNNYSIDE.COM
> Name Server: NS3.SUNNYSIDE.COM
> $
>
> Please change that to this set:
>
> $ whois sf-lug.org | grep 'Name Server'
> Name Server: NS1.LINUXMAFIA.COM
> Name Server: NS.PRIMATE.NET
> Name Server: NS1.SVLUG.ORG
> Name Server: NS1.SF-LUG.ORG
> $
>
> To explain: NS1.SF-LUG.ORG is the master nameserver for domains
> sf-lug.org and sf-lug.com, and is thus where Michael and (IIRC) Grant
> Bowman maintain the DNS contents. NS1.LINUXMAFIA.COM and NS1.SVLUG.ORG
> are slave nameservers for those two domains, both administered by me.
> NS.PRIMATE.NET is a third slave nameserver, administered by a friend of
> mine, Aaron T. Porter, who does secondary nameservice for a number of
> LUG domains.
>
> In addition to you declaring that set of four domains authoritative,
> it will be necessary for Michael/Grant to construct and load an
> appropriate master DNS zonefile for sflug.org at NS1.SF-LUG.ORG, and
> also Aaron and I would need to enable secondary nameservice for the new
> domain at our nameservers to flesh out the set of four. Fortunately,
> nobody's presently relying on namservice from sflug.org, so a day or so
> of setup delay is not a problem.
>
> You and Michael/Grant/Jim will need to talk eventually about where to
> re-register the domain (assuming they are not hot on GoDaddy), and who
> should be Registrant (owner) in the long term and who should have
> administrative access to the registrar account. I'm not part of that
> picture at this time (but may be, later).
>
> Anyway, if you agree with my suggestion, please let the mailing list
> know when you've changed the authoritative server list.
>
> Thanks again for your on-the-spot saction and public spiritedness.
More information about the sf-lug
mailing list