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