[sf-lug] SFLUG.org
Michael Paoli
Michael.Paoli at cal.berkeley.edu
Thu Apr 11 06:03:00 PDT 2019
Al,
You could also, at your earliest convenience ...
you can apparently extend/delegate access
https://account.godaddy.com/access#
E.g.:
Access level: Products & Domains
Delegate can:
Access your products (including product control panels) and cancel new
products, except for domains. For domains, the delegate can:
Manage DNS/nameservers and forwarding.
You could extend that to myself and/or Rick - it just wants a
name and email address to do so:
Michael Paoli <Michael.Paoli at cal.berkeley.edu>
(and I presume for Rick:) Rick Moen <rick at linuxmafia.com>
In the meantime, we are waiting for some changes:
DNS delegation:
sflug.org. IN NS ns1.linuxmafia.com.
sflug.org. IN NS ns1.svlug.org.
sflug.org. IN NS ns1.sf-lug.org.
sflug.org. IN NS ns.primate.net.
and as soon as feasibly convenient but >=86400 seconds (24 hrs.)
thereafter, for DNSSEC:
sflug.org. IN DS 55585 8 2
D50AA68F2A9A19651E46070FA0A5C504F6B396FD28A1CFD97F95D6202A703D80
Thanks
Could also do ns[0-3].sunnyside.com. as (additional) slaves, if you wish.
(to be delegated) master is presently ns1.sf-lug.org.:
198.144.194.238
2001:470:1f04:19e::2
Just let us know.
Thanks.
> From: Al <awsflug at sunnyside.com>
> Subject: Re: [sf-lug] Domain administration (broken WHOIS)
> Date: Sat, 6 Apr 2019 15:43:43 -0700
> 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. Doesn't seem yet that there's a definite
> movement to do anything with it anyway.
> For what it's worth I share Rick's opinions on Meetups. If someone
> must have RSVP, then there are open source alternatives that aren't
> invasive and controlling the way Meetup is.
>
> Al
>
> On 4/6/2019 15:26, Michael Paoli wrote:
>> Thanks. Yeah, per relevant technical standards/policies & such,
>> that certainly would be at least (semi-)broken.
>>
>> I'll poke around the Joker interface sometime soon-ish (at
>> least hopefully), and see if I can "fix" that.
>> And, yep, may be fallout from GDPR.
>>
>> I should recheck the whois & config stuff I have access to for
>> the domains I have & support (a couple of my own domains, plus
>> multiple[L]UG domains). "Worst case" I ought catch/fix that
>> around renewal times ... but hopefully I get to it well before
>> then. :-) (hmmm... 3 different registrars I currently deal with).
>>
>> Egad, ... and it's a bloody web form thingy. I think that's
>> even more annoying than those "privacy" email thingies.
>> And ... dear knows if they work - form probably just takes the
>> data and maybe tells you it took it okay. After that ... dear
>> knows.
>>
>>> From: "Rick Moen" <rick at linuxmafia.com>
>>> Subject: Domain administration (broken WHOIS)
>>> Date: Sat, 6 Apr 2019 01:38:00 -0700
>>
>>> and so I set out to remind myself who owns & administers the existing
>>> domains, by looking at the public WHOIS contacts? You're way ahead of
>>> me, right? You can probably guess what I'm about to say next.
>>>
>>>
>>> $ whois -h whois.joker.com sf-lug.com
>>> Domain Name: sf-lug.com
>>> Registry Domain ID: 123972386_DOMAIN_COM-VRSN
>>> Registrar WHOIS Server: whois.joker.com
>>> Registrar URL: https://joker.com
>>> Updated Date: 2018-05-04T14:25:58Z
>>> Creation Date: 2004-07-02T21:17:46Z
>>> Registrar Registration Expiration Date: 2019-07-02T21:17:46Z
>>> Registrar: CSL Computer Service Langenbach GmbH d/b/a joker.com
>>> Registrar IANA ID: 113
>>> Registrar Abuse Contact Email: abuse at joker.com
>>> Registrar Abuse Contact Phone: +49.21186767447
>>> Domain Status: clientTransferProhibited
>>> https://icann.org/epp#clientTransferProhibited
>>> Registrant Organization: San Francisco Linux User Group
>>> Registrant Country: US
>>> Registrant Email: https://csl-registrar.com/contact/sf-lug.com/owner
>>> Admin Email: https://csl-registrar.com/contact/sf-lug.com/admin
>>> Tech Email: https://csl-registrar.com/contact/sf-lug.com/tech
>>> Name Server: ns.primate.net
>>> Name Server: ns1.linuxmafia.com
>>> Name Server: ns1.sf-lug.com
>>> DNSSEC: signedDelegation
>>> URL of the ICANN Whois Inaccuracy Complaint Form:
>>> https://www.icann.org/wicf/
>>>>>> Last update of WHOIS database: 2019-04-06T08:28:25Z <<<
>>> $
>>>
>>>
>>> $ whois -h whois.joker.com sf-lug.org
>>> Domain Name: sf-lug.org
>>> Registry Domain ID: D104593649-LROR
>>> Registrar WHOIS Server: whois.joker.com
>>> Registrar URL: https://joker.com
>>> Updated Date: 2018-05-04T05:30:34Z
>>> Creation Date: 2004-07-02T21:17:47Z
>>> Registrar Registration Expiration Date: 2019-07-02T21:17:47Z
>>> Registrar: CSL Computer Service Langenbach GmbH d/b/a joker.com
>>> Registrar IANA ID: 113
>>> Registrar Abuse Contact Email: abuse at joker.com
>>> Registrar Abuse Contact Phone: +49.21186767447
>>> Domain Status: clientTransferProhibited
>>> https://icann.org/epp#clientTransferProhibited
>>> Registrant Organization: San Francisco Linux User Group
>>> Registrant State/Province: CA
>>> Registrant Country: US
>>> Registrant Email: https://csl-registrar.com/contact/sf-lug.org/owner
>>> Admin Email: https://csl-registrar.com/contact/sf-lug.org/admin
>>> Tech Email: https://csl-registrar.com/contact/sf-lug.org/tech
>>> Name Server: ns.primate.net
>>> Name Server: ns1.svlug.org
>>> Name Server: ns1.sf-lug.org
>>> Name Server: ns1.linuxmafia.com
>>> DNSSEC: signedDelegation
>>> URL of the ICANN Whois Inaccuracy Complaint Form:
>>> https://www.icann.org/wicf/
>>>>>> Last update of WHOIS database: 2019-04-06T08:27:21Z <<<
>>> $
>>>
>>>
>>> Who's Registrant, and how does one get in contact with him/her?
>>> Who's Tech Contact, and how does one get in contact with him/her?
>>> Who's Admin Contact, and how does one get in contact with him/her?
>>>
>>> Same answer to all three questions: It's a secret. Nobody's permitted
>>> to know.
>>>
>>>
>>> Given that Joker.com aka CSL Computer Service Langenbach GmbH is in
>>> Düsseldorf, Germany, this may very well be a GDPR-driven blunder imposed
>>> on the domain owner. Irrespective of that, IMO it's important for
>>> whoever administers these domains to un-hide the WHOIS contacts, so that
>>> the WHOIS record becomes once again usable for its intended purpose.
>>> ASAP.
>>>
>>> Or follow the path of least resistance, do nothing about broken WHOIS,
>>> and be prepared to hear 'I told you so' when badness happens because the
>>> domain's principals cannot be identified and contacted.
More information about the sf-lug
mailing list