| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| system:registrars [2024-07-20T00:13:05+0000] – . --> , (fix apparent typo) michael_paoli_admin | system:registrars [2025-01-15T19:58:23+0000] (current) – +RFC 7344 michael_paoli |
|---|
| specific domains?) via [[https://www.gandi.net/|Gandi.net]]. \\ | specific domains?) via [[https://www.gandi.net/|Gandi.net]]. \\ |
| [[https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/welcome-domain-registration.html|AWS > Documentation > Amazon Route 53> Developer Guide "At the end of the registration process, we send your information to the registrar for the domain. The domain registrar is either Amazon Registrar, Inc. or our registrar associate, Gandi. To find out who the registrar is for your domain, see Finding your registrar."]] \\ | [[https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/welcome-domain-registration.html|AWS > Documentation > Amazon Route 53> Developer Guide "At the end of the registration process, we send your information to the registrar for the domain. The domain registrar is either Amazon Registrar, Inc. or our registrar associate, Gandi. To find out who the registrar is for your domain, see Finding your registrar."]] \\ |
| %%**%%[[https://cloud.google.com/|cloud.google.com]] registrar services has been sold off to and is now \\ | %%**%%[[https://cloud.google.com/|cloud.google.com]]'s registrar services ([[https://domains.google/|Google Domains]]) has been sold off to and is now \\ |
| owned and managed by[[https://www.squarespace.com/|squarespace.com]] and, at least as of the time of \\ | owned and managed by[[https://www.squarespace.com/|squarespace.com]] \\ |
| this writing, is still being transitioned fully over to [[https://www.squarespace.com/|squarespace.com]] \\ | |
| See also: \\ | See also: \\ |
| [[https://newsroom.squarespace.com/blog/googledomains|Squarespace Enters Definitive Agreement to Acquire Google Domains Assets]] \\ | [[https://newsroom.squarespace.com/blog/googledomains|Squarespace Enters Definitive Agreement to Acquire Google Domains Assets]] \\ |
| AWS didn't themselves (at least initially) become a registrar, | AWS didn't themselves (at least initially) become a registrar, |
| but resold Gadni's registrar services through AWS's Route 53 service. | but resold Gadni's registrar services through AWS's Route 53 service. |
| | |
| | And more positive experience: \\ |
| | Around 2024-06-08T08:46:00Z I opened support request #155532 API & Web: feature request: DNSSEC: add capability to manage via CDNSKEY/CDS records \\ |
| | And yes, not expecting anything on it anytime particularly soon, but they did well understand it and take note, |
| | so, rather likely will come in future API and web interface. \\ |
| | See also: [[https://www.rfc-editor.org/rfc/rfc7344.html|RFC 7344]], [[https://www.rfc-editor.org/rfc/rfc8078.html|RFC 8078]], etc. |
| |
| I might be forgetting some details and further examples, but pretty much | I might be forgetting some details and further examples, but pretty much |
| |
| [[https://www.networksolutions.com/|NetworkSolutions.com]] / [[https://www.web.com/|Web.com]] - avoid like the plague. They may not be | [[https://www.networksolutions.com/|NetworkSolutions.com]] / [[https://www.web.com/|Web.com]] - avoid like the plague. They may not be |
| the worst out there, but they're pretty horrible. Some of their sh*t: | //the worst// out there, but they're pretty horrible. Some of their sh*t: |
| * Tons of marketing/sales/spam email, difficult to opt out (have to call a phone number and can take up to 30 days to opt out!). | * Tons of marketing/sales/spam email, difficult to opt out (have to call a phone number and can take up to 30 days to opt out!). |
| * Overpriced - their default pricing is horrible. But if you play the song and dance with their offers (e.g. yearly at renewal), you can get a reasonable price (just start to go through the motions like one is going to transfer the domain away - then you get offers for a reasonable price - about market rate and about 1/3 what they'd otherwise charge). But alas, to take that offer, you have to opt in to their marketing emails ... and yeah, opting out ... ugh. | * Overpriced - their default pricing is horrible. But if you play the song and dance with their offers (e.g. yearly at renewal), you can get a reasonable price (just start to go through the motions like one is going to transfer the domain away - then you get offers for a reasonable price - about market rate and about 1/3 what they'd otherwise charge). But alas, to take that offer, you have to opt in to their marketing emails ... and yeah, opting out ... ugh. |
| * Sometimes they'll opt you in for stuff you didn't ask for and don't want ... e.g. just gave you a crud yourbasedomainname.somecrudTLD without your asking or wanting ... then they of course want to sell you on renewing it. Ugh. | * Sometimes they'll opt you in for stuff you didn't ask for and don't want ... e.g. just gave you a crud yourbasedomainname.somecrudTLD without your asking or wanting ... then they of course want to sell you on renewing it. Ugh. |
| * They also tend to push lots of announcing clueless offers. Got [[https://www.sf-lug.org/|sf-lug.org]]? How 'bout buy up all these sf-tote.someTLD and sftote.someTLD domains, I mean tote is like lug (as in sf-lug for San Francisco Linux Users' Group), right? Ugh. | * They also tend to push lots of announcing clueless offers. Got [[https://www.sf-lug.org/|sf-lug.org]]? How 'bout buy up all these sf-tote.someTLD and sftote.someTLD domains, I mean tote is like lug (as in sf-lug for San Francisco Linux Users' Group), right? Ugh. |
| | * 1997-07-17 they majorly screwed up Internet DNS for com. and net. TLDs, effectively knocking them off The Internet for many/most folks for many many hours. See reports, e.g.: [[https://archive.nytimes.com/www.nytimes.com/library/cyber/week/071797dns.html|The New York Times: Human Error Cripples the Internet]], [[https://groups.google.com/g/comp.protocols.dns.bind/c/rDunynim12U/m/FedJdyxt484J?pli=1|USENET (as seen on Google Groups)]] |
| |
| So, yeah, general experience with NetworkSolutions.com / Web.com has | So, yeah, general experience with NetworkSolutions.com / Web.com has |
| ==== GoDaddy.com ==== | ==== GoDaddy.com ==== |
| |
| [[https://www.godaddy.com/|Godaddy.com]] ... uhm, probably just don't. How 'bout start with their | [[https://www.godaddy.com/|Godaddy.com]] ... uhm, probably just don't. How 'bout ... |
| sexist/racist/... sleazy crud advertising ([[https://www.youtube.com/watch?v=dTvYVxO_9N8|YouTube: Washington Post: GoDaddy's most controversial Super Bowl ads]], and [[https://www.youtube.com/watch?v=zDqQhaUaVq0&t=84s|The Onion can't help but to take a well deserved parody shot at them]]) ... maybe they're better now on that? I | * start with their sexist/racist/... sleazy crud advertising ([[https://www.youtube.com/watch?v=dTvYVxO_9N8|YouTube: Washington Post: GoDaddy's most controversial Super Bowl ads]], and [[https://www.youtube.com/watch?v=zDqQhaUaVq0&t=84s|The Onion can't help but to take a well deserved parody shot at them]]) ... maybe they're better now on that? I haven't particularly tracked. |
| haven't particularly tracked. They're also based in Canada, so if you | * They're also based in Canada, so if you have some serious issue/dispute with them, and want to take legal action ... good luck with that (at least if you're not, e.g. a Canadian citizen or resident). |
| have some serious issue/dispute with them, and want to take legal action | * Been a while, but last I dealt with them their interfaces were rather lacking. |
| ... good luck with that (at least if you're not, e.g. a Canadian resident or citizen). | * Some of their behavior may be or have been shady - at least I've heard such - but didn't run into that personally. |
| Been a while, but last I dealt with them their | * Oh, but one thing I have repeatedly seen, that's quite shady, and as far as I'm aware they're still doing it. So automatic renewals ... no biggie, right, should be quite straight forward. Yeah, ... the way they do those ... they actually do the renewals //slightly after the domains expire//. Yeah shady as fsck - basically completely and totally exposes one to the mercy of GoDaddy every single time they do that. They don't even renew day, or //hours// before expiration, but only slightly after expiration. |
| interfaces were rather lacking. Some of their behavior may be or have | * Oh, and no shortage of additional issues and controversies, e.g. [[https://en.wikipedia.org/wiki/Controversies_surrounding_GoDaddy#Backing_of_SOPA_and_resultant_boycott|their (mis)handling regarding their position, etc. on]] [[https://en.wikipedia.org/wiki/Stop_Online_Piracy_Act|SOPA]]. |
| been shady - at least I've heard such - but didn't run into that | * Egad, and their DNSSEC interface for delegated DNS doesn't even work properly: "Date: Mon, 07 Oct 2024 16:14:27 -0600" ... "we all know that it makes sense to have multiple ones otherwise how can one do a rollover? I should explain that with GoDaddy every time I enter a DS record it always gives me an error message and says that it failed. However afterwards I can look and see that it was in there anyway. I reported this to the customer service for pro customers about 4 years ago. They solved the problem rather nearty by eliminating customer service. Not a joke. I think that was very clever of them. Nowadays I could pay $119 a month if I were an idiot and get someone that spoke poor English and wondered out loud what DNS stood for. In any event the bug, however, is still present. It kind of does what it ever feels like at any given moment which is usually not what the person entering the data wants." ... "Date: Mon, 7 Oct 2024 21:44:45 -0600" ... "10th time is a charm" "both 8/2 records now in place" |
| personally. Oh, but one thing I have repeatedly seen, that's quite shady, and as far as I'm aware they're still doing it. | |
| So automatic renewals ... no biggie, right, should be quite straight forward. Yeah, ... the way they do those ... they actually do the renewals | |
| //slightly after the domains expire//. Yeah shady as fsck - basically completely and totally exposes one to the mercy of GoDaddy | |
| every single time they do that. They don't even renew day, or //hours// before expiration, but only slightly after expiration. | |
| Oh, and no shortage of additional issues and controversies, e.g. [[https://en.wikipedia.org/wiki/Controversies_surrounding_GoDaddy#Backing_of_SOPA_and_resultant_boycott|their (mis)handling regarding their position, etc. on]] [[https://en.wikipedia.org/wiki/Stop_Online_Piracy_Act|SOPA]]. | |
| |
| ---- | ---- |
| |
| [[https://www.namecheap.com/|Namecheap.com]] - sucky interface, | [[https://www.namecheap.com/|Namecheap.com]] - sucky interface, |
| and not so competent staff. Ugh, 2022 | and not so competent staff.\\ |
| | Ugh, 2022 |
| and they still can't do IPv6 for glue records on their interface ... | and they still can't do IPv6 for glue records on their interface ... |
| even though they have | even though they have |
| [[https://www.namecheap.com/support/knowledgebase/article.aspx/292/10/how-can-i-update-my-personal-nameservers-ip-address/#comment-601548546|support requests open to do that for more than a decade]]! | [[https://www.namecheap.com/support/knowledgebase/article.aspx/292/10/how-can-i-update-my-personal-nameservers-ip-address/#comment-601548546|support requests open to do that for more than a decade]]! |
| So, have to do support request for that ... ugh, really, in | So, have to do support request for that ... ugh, really, in |
| 2022 ... and they're not very competent about handing it at that. | 2022 ... and they're not very competent about handing it at that.\\ |
| Oh, and API ... 2023 and still: | Oh, and API ... 2023 and still: |
| [[https://www.namecheap.com/support/api/intro/|whitelist at least one IP before your API access will begin to work. Please keep in mind that only IPv4 addresses can be used]]. | [[https://www.namecheap.com/support/api/intro/|whitelist at least one IP before your API access will begin to work. Please keep in mind that only IPv4 addresses can be used]].\\ |
| Also much of the information their support staff provides is incorrect ... ugh. | Also much of the information their support staff provides is incorrect ... ugh.\\ |
| | Ugh, "spam" - created account there 2024-11-19 (to assist someone with something), and very explicitly opted out of their "marketing" communication. Yet 2024-11-26 they're sending me spam: "Subject: Forgot something? Hot deals inside" and body that starts with: "Namecheap Top deals" ... |
| | And "of course", their unsubscribe link tells me: "You’ve already been unsubscribed from newsletter & marketing communications".\\ |
| | And I vote "no confidence" (at best) on Namecheap.com. As of 2024-12-18 they're still doing DS records with SHA-1 |
| | (see e.g.: [[https://dnsviz.net/d/lunacrescentnails.com/Z2J5fw/dnssec/|lunacrescentnails.com]]), |
| | which is disallowed for new DS records, and has now been for years per [[https://datatracker.ietf.org/doc/html/rfc8624#section-3.3|RFC 8624 Section 3.3]]. |
| | Furthermore, on 2024-12-18 I commented on this matter on their |
| | [[https://www.namecheap.com/support/knowledgebase/article.aspx/9723/2232/managing-dnssec-for-domains-pointed-to-premium-or-basicdns/|Managing DNSSEC for domains pointed to Premium or BasicDNS]] |
| | web page, and "waiting to be approved by Namecheap.com" - well, over 5 days later, not only is the comment not yet approved/visible nor responded to nor an email response, |
| | but sorting comments by most recent, the most recent is about 4 //years// old, |
| | so appears they don't care to accept/post comments nor reply, and very possible they don't even bother to read them. |
| | So, yeah, paint me not surprised - when they've already got open requests that have been open for more than a decade that should've been implemented, |
| | and haven't yet been ... alas, not surprised //at all//. This DS SHA-1 issue //may// be limited to just their "BasicDNS" |
| | (and likely also "Premium DNS") services, and possibly certain domains thereupon, |
| | as it seems to //not// impact (at least some, if not all) domains which are not on their DNS hosting |
| | (e.g. [[https://dnsviz.net/d/savingthedolph.in/Yt3Rhg/dnssec/|savingthedolph.in]]). |
| |
| ---- | ---- |
| ==== domains.google ==== | ==== domains.google ==== |
| |
| So, [[https://domains.google/|Google Domains]] has been a competent reliable registrar. | So, [[https://domains.google/|Google Domains]] had been a competent reliable registrar. |
| However, on 2023-06-15 [[https://www.squarespace.com/|Squarespace]] concluded an agreement to purchase the Google Domains business. | However, on 2023-06-15 [[https://www.squarespace.com/|Squarespace]] concluded an agreement to purchase the Google Domains business. |
| So, what has been Google Domains is being migrated over to Squarespace. And, though I'd expect that for the basic registrar services that | So, what had been Google Domains has been migrated over to Squarespace. And, though I'd expect that for the basic registrar services that |
| would continue to be functional (but may be a bit different), it's certainly not being an entirely smooth transition for many customers. | would continue to be functional (but may be a bit different), it's certainly not been an entirely smooth transition for many customers. |
| But that may mostly be due to differing interfaces, and that Google Domains offered services beyond that of registrar which Squarespace | But that may mostly be due to differing interfaces, and that Google Domains offered services beyond that of registrar which Squarespace |
| doesn't offer at all. E.g. Google Domains, in its DNS offering, has supported hosting of Dynamic DNS (DDNS). Squarespace has no such | doesn't offer at all. E.g. Google Domains, in its DNS offering, had supported hosting of Dynamic DNS (DDNS). Squarespace has no such |
| offering, so there are many customers not so thrilled with such changes, and many have been scrambling to find suitable replacement services. | offering, so there are many customers not so thrilled with such changes, and many have been scrambling to find suitable replacement services. |
| Note historically and generally, Google often launches things, and later drops them, as/when they find/decide they're not (sufficiently) profitable | Note historically and generally, Google (& Alphabet) often launches things, and later drops them, as/when they find/decide they're not (sufficiently) |
| and/or don't well (enough) fit to their core business model, etc. So, although Google was quite competent as registrar, I find it no great | profitable and/or don't well (enough) fit to their core business model, etc. So, although Google was quite competent as registrar, I find it no great |
| surprise that they're exiting the registrar business. Do I see that as an issue with failed or reduced integration with | surprise that they're exiting the registrar business. Do I see that as an issue with failed or reduced integration with |
| [[https://cloud.google.com/|Google Cloud / Google Cloud Platform (GCP)]]? | [[https://cloud.google.com/|Google Cloud / Google Cloud Platform (GCP)]]? |
