[sf-lug] done: proposed: sf-lug.org. change registrar from joker.com to gandi.net
Michael Paoli
Michael.Paoli at cal.berkeley.edu
Tue May 19 06:31:45 PDT 2020
And done.
sf-lug.org registration transfer completed at 2020-05-19T12:34:23Z
registration now doesn't expire until: 2022-07-02T21:17:47Z
Glue Records updated by approximately: 2020-05-19T13:10:05Z
before:
ns0.sf-lug.org. 86400 IN A 198.144.194.238
ns0.sf-lug.org. 86400 IN AAAA 2001:470:1f05:19e::3
ns1.sf-lug.org. 86400 IN A 198.144.194.238
ns1.sf-lug.org. 86400 IN AAAA 2001:470:1f05:19e::2
after:
ns1.sf-lug.org. 86400 IN A 96.86.170.229
ns1.sf-lug.org. 86400 IN AAAA 2001:470:1f05:19e::3
ns0.sf-lug.org. 86400 IN A 96.86.170.229
ns0.sf-lug.org. 86400 IN AAAA 2001:470:1f05:19e::3
Will update NS, etc. after TTL period.
Also updated:
https://www.wiki.balug.org/wiki/doku.php?id=sf-lug:resources_etc
Currently: Jim Stockford, Michael Paoli, Al Whaley
are holders of the "keys to the kingdom" (have access to update
DNS delegation from registrar, transfer domain, etc.) for the
sf-lug.org domain.
references/exceprts:
> From: "Michael Paoli" <Michael.Paoli at cal.berkeley.edu>
> Subject: proposed: sf-lug.org. change registrar from joker.com to gandi.net
> Date: Sun, 26 Apr 2020 00:33:00 -0700
> proposed: sf-lug.org. change registrar from joker.com to gandi.net
>
> I'm proposing we change registrar for multiple reasons.
> Most notably and annoyingly, joker.com is grossly unacceptable when it
> comes to glue records. For most any reasonably sane registrar on the
> planet, updating glue records is a snap. But oh no, not for joker.com
> For most any sane registrar on the planet (e.g. gandi), simply provide
> the updated IP address(es) into a web form, and boom, done
> (notwithstanding teensy bit of latency for processing and DNS TTLs).
>
> Jim, if you want to deal with these jokers at joker.com and see if you
> can get it fixed, have at it, here's what needs to be updated in the
> glue data:
> Change from:
> ns1.sf-lug.org. 86400 IN A 198.144.194.238
> ns1.sf-lug.org. 86400 IN AAAA 2001:470:1f04:19e::2
> to:
> ns1.sf-lug.org. 86400 IN A 96.86.170.229
> ns1.sf-lug.org. 86400 IN AAAA 2001:470:1f05:19e::3
> If it's not fixed within 10 days of this email/posting hitting the
> SF-LUG list, I'll presume we're to proceed with change of registrar.
> Note that it should NOT be necessary to change NS records of other
> domain(s) (nor even sf-lug.org. itself) to fix the glue records as noted
> above.
>
> Joker.com, on the other hand, seems to be completely and totally unable
> to make changes to glue records, even via email request, if anything
> whatsoever (at least per their claims) in the parent domain is still
> using the NS and glue records. So, e.g., as is our case, there are
> other domain(s) (e.g. sflug.org) even with other registrar(s)
> (e.g. godaddy.com), despite sf-lug.org being with joker.com, joker.com
> will not allow us to change A/AAAA glue records for ns1.sf-lug.org. so
> long as sflug.org (or any other <whatever>.org domain, and with whatever
> registrar) is still using ns1.sf-lug.org. as NS. I find that utterly
> unacceptable. It should NOT be necessary to do the ns1 ... ns0 ... ns00
> ... dance to work around joker.com's incompetence ... and can't even
> guarantee that such work around would be fully effective. And that's
> really quite a waste of resource (persons' time!), when it's not
> necessary with a much more sane registrar. Heck, just think, one could
> hold any person's/organization's "glue" records "hostage" with
> joker.com! Just get/have a TLD with same parent at any registrar,
> include the relevant NS as one of the NS records for said domain, and
> the "victim" person/organization then can't change their glue record!
> Way to go joker.com!
>
> I also find a lot of joker.com's services (and annoyances), and lack of
> quality to be ... well, lacking for a registrar, especially when much
> better can be had at comparable pricing - I just do not find Joker.com
> worth the hassle/annoyance/limitations.
>
> references/excerpts:
>
> Notable issues/annoyances (see also further details/references further
> below):
> o damn near impossible to update glue records
> o sucky whois/GDPR policy with no opt-out to allow to make public what
> ought generally be public
> o general comparative lack of quality (e.g. much less useful/informative
> renewal notices, web interfaces plastered with with ads looks like a
> trip back to 1997)
>
> General comparative lack of quality:
> http://linuxmafia.com/pipermail/sf-lug/2019q2/014183.html
>
> GDPR bungle on whois, etc.:
> http://linuxmafia.com/pipermail/sf-lug/2019q2/013971.html
>
> Can't fix/update glue:
> dig @$(dig +short org. NS | head -n 1) +norecurse +noall +answer
> +additional +authority +comment sflug.org NS
> ;; AUTHORITY SECTION:
> sflug.org. 86400 IN NS ns1.sf-lug.org.
> ;; ADDITIONAL SECTION:
> ns1.sf-lug.org. 86400 IN A 198.144.194.238
> ns1.sf-lug.org. 86400 IN AAAA 2001:470:1f04:19e::2
>
> dig +noall +norecurse +answer ns1.sf-lug.org. A ns1.sf-lug.org. AAAA
> ns1.sf-lug.org. 86400 IN A 96.86.170.229
> ns1.sf-lug.org. 86400 IN AAAA 2001:470:1f05:19e::3
>
>> Date: Wed, 08 Jan 2020 19:55:37 -0800
>> From: "Michael Paoli" <Michael.Paoli at cal.berkeley.edu>
>> To: "Rick Moen" <rick at linuxmafia.com>
>> Subject: Re: (forw) [volunteers] Your Joker.com Request has been
>> processed []
>
>>> From: "Rick Moen" <rick at linuxmafia.com>
>>> Subject: (forw) [volunteers] Your Joker.com Request has been processed []
>>> Date: Sun, 22 Dec 2019 03:08:20 -0800
>>
>>> Michael, I think you said you had problems getting a glue record
>>> at Joker.com repointed to a new IP, right? Turns out, the place you
>>> do that is (after login to Joker.com customer account) toolbar item 'My
>>> Joker', then 'My Nameservers'.
>>
>> Yeah, still can't get ns0.sf-lug.org. updated via Joker.
>> Had it fully out'a there for well over (more than 2 days) the TTL,
>> still can't get it out of being "registered custom nameservers" - what
>> Joker calls the "glue" records in their interface.
>> What they said earlier, was effectively it needs totally be out, before
>> it can be removed ... that doesn't work ... even tried putting it
>> back, deleting it, then updating the registered NS ... still fails:
>> "This nameserver exists already. You can make use of it by simply
>> assigning it to the domain."
>> Not a huge deal ... as the work-around is the newly implemented
>> ns00.sf-lug.org.
>> Still annoying, though.
>> Similar was no fuss no mess easy-peasy with Gandi - just put in the new
>> IP address(es) - simply paste 'em in, one per line ... done.
>> Joker lets one only put in a single IPv4 and a single IPv6 address - or
>> only one of the two. And makes it at best very difficult to change the IPs.
>> This is what they sent me earlier (and I also forwarded to you earlier):
>> ----- Forwarded message from Michael.Paoli at cal.berkeley.edu -----
>> Date: Tue, 17 Dec 2019 03:06:29 -0800
>> From: "Michael Paoli" <Michael.Paoli at cal.berkeley.edu>
>> Subject: Fwd: [INF95131067] Re: [support][premium] [sf-lug.org]
>> To: rick at linuxmafia.com
>>
>> Ugh, and here's Joker's far less than ideal response on updating glue
>> records - can't do it at all with their interface (or even them do it for
>> you!), without apparently deleting *all* references to the NS record!
>>
>> Ugh.
>>
>> Yup, we'll just keep piling up the reasons to switch from Joker.com. ;-}
>>
>> ----- Forwarded message from info at joker.com -----
>> Date: Mon, 16 Dec 2019 10:31:53 +0100
>> From: "Joachim Rolf" <info at joker.com>
>> Reply-To: info at joker.com
>> Subject: [INF95131067] Re: [support][premium] [sf-lug.org]
>> To: sflug.org at gmail.com
>>
>> Dear Sir/Madam,
>>
>> thank you for your email.
>>
>> It's only possible to delete a nameserver if it is not linked to any domain.
>> Please arrange, that the nameserver will not be used by a domain.
>>
>> If the mentioned nameserver is connected with a domain you must
>> contact the owner or admin of these domain and ask them to remove the
>> references.
>>
>> If you want to delete a nameserver please try:
>>
>> 1) Login to the Joker.com webinterface at:
>> https://joker.com/?mode=mod_nserver&do_next=list_nservers
>>
>> with the account of the domain creator, or one of the additional
>> granted domain permissions (Roles)
>>
>> 2) Please mark the selection box in front of the nameserver and use
>> the "delete" button.
>>
>> If you are looking for information about changes of a domain or
>> create/update the nameserver of a domain, please go to our FAQ at:
>> https://joker.com/f/11
>>
>> Best regards,
>>
>> your Joker.com team
>>
>> --
>> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
>> Please check out our FAQ: https://joker.com/f/1
>> _________________________________________________________________________
>>
>>
>> Joker.com is run by
>> CSL Computer Service Langenbach GmbH
>> DE-40549 Düsseldorf
>> Germany
>>
>> https://joker.com
>>
>> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
>>
>>
>> ---- Original message ----
>>
>>> Date: 13.12.2019 5:17:34 [UTC]
>>> User [KID]: sf-lug Client ID: 4035352
>>> Subject: [support][premium] [sf-lug.org]
>>> Domain: sf-lug.org
>>> User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like
>>> Gecko) Chrome/73.0.3683.75 Safari/537.36
>>> Request:
>>> How do I update DNS "glue" records? ("Register nameservers" /
>>> "register NS")
>>> most specifically, for ns0.sf-lug.org,
>>> I want to replace:
>>> ns0.sf-lug.org. 86400 IN A 198.144.194.238
>>> updating to new IPv4 with:
>>> ns0.sf-lug.org. 86400 IN A 96.86.170.229
>>> Your web GUI interface seems to give ability to add new "Register
>>> nameservers"
>>> / "register NS" (where you have your "glue" records
>>> input),
>>> but doesn't seem to give any way to remove them once there or to
>>> update the IP
>>> address(es) associated with them.
>>> Can you please let me know how to do with with your web GUI
>>> interface - or if
>>> it can't be done there, please make that change (just the
>>> IPv4 IP, the IPv6 isn't changing).
>>> Thanks.
More information about the sf-lug
mailing list