This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
system:registrars [2024-02-24T11:29:17+0000] michael_paoli Added details on Google Domains |
system:registrars [2024-03-09T00:59:23+0000] (current) michael_paoli Added bit about GoDaddy's shady auto-renewals that happen slightly after expiration |
||
---|---|---|---|
Line 99: | Line 99: | ||
---- | ---- | ||
- | Will likely well fill out and organize remainder later, | + | Did at least mostly well fill out and organize fair bit of detail, |
- | but in the meantime, some background "discussions"(posts): | + | for the curious/interested, some earlier background "discussions"(posts): |
[[http://linuxmafia.com/pipermail/conspire/2023-February/012261.html|Various pro/con recommendations, including fair bit of supporting reasons]] \\ | [[http://linuxmafia.com/pipermail/conspire/2023-February/012261.html|Various pro/con recommendations, including fair bit of supporting reasons]] \\ | ||
Line 107: | Line 107: | ||
---- | ---- | ||
- | |||
- | Will likely well fill out and organize remainder later. | ||
- | |||
===== Pros and cons and recommendations and not of various example registrars ===== | ===== Pros and cons and recommendations and not of various example registrars ===== | ||
Line 169: | Line 166: | ||
no cost to simply create account there) - I ran across a slight bug in | no cost to simply create account there) - I ran across a slight bug in | ||
their interface - notably setting up account in US, and dealing with | their interface - notably setting up account in US, and dealing with | ||
- | states. I reported the issue to them. They fixed it lickety-split and | + | states. I reported the issue to them. They fixed it in quite quick order and |
were great on communication and follow-through to check and ensure that | were great on communication and follow-through to check and ensure that | ||
all was well and I was no longer seeing the earlier issue I'd reported - | all was well and I was no longer seeing the earlier issue I'd reported - | ||
pretty impressive response for a non-paying (or at least not-yet-paying) | pretty impressive response for a non-paying (or at least not-yet-paying) | ||
- | customer. | + | customer. I looked up that much earlier issue for the details and went |
+ | (summarized) about like this: \\ | ||
+ | 2015-01-23T04:55:34Z I opened issue and got automated response (RT support-en #5534422) \\ | ||
+ | 2015-01-23T10:21:23Z I received notification they'd transferred it to relevant support area \\ | ||
+ | 2015-01-23T16:12:40Z I received notification indicating it was resolved \\ | ||
+ | 2015-01-23T19:06:27Z I checked, not (quite) resolved and notified them \\ | ||
+ | 2015-01-24T15:06:33Z I received notification they'd forwarded to specialist \\ | ||
+ | 2015-01-26T16:19:28Z I received notification they'd applied work-around on my account (effectively fixing it for me) \\ | ||
+ | 2015-01-26T18:31:36Z I checked confirmed all good (not only work-around but bug fixed) \\ | ||
+ | 2015-01-27T16:16:55Z I received notification confirming that they'd solved and fixed the issue \\ | ||
+ | This is vastly better than many registrars, when one often has to do battle with them and go | ||
+ | trough 2 to 3 rounds just to get them to even understand or acknowledge that there's even an issue, | ||
+ | after which other registrars may still fail to fix the issue and/or often provide incorrect information. | ||
+ | And I got that great level of service from Gandi when I wasn't even a customer yet and for a relatively | ||
+ | low priority pretty minor bug. | ||
Their No Bullshit slogan/motto really does very much apply. No | Their No Bullshit slogan/motto really does very much apply. No | ||
Line 236: | Line 247: | ||
Quite same applies for any data one needs to change, e.g. whois, DNS | Quite same applies for any data one needs to change, e.g. whois, DNS | ||
delegation, etc. | delegation, etc. | ||
+ | |||
+ | Oh, and another data point for Gandi's rock solid reliability and | ||
+ | dependability and quality API, etc. When [[https://aws.amazon.com/|AWS]] entered into | ||
+ | offering domain registration via their [[https://aws.amazon.com/route53/|Amazon Route 53]] service offering, | ||
+ | AWS didn't themselves (at least initially) become a registrar, | ||
+ | but resold Gadni's registrar services through AWS's Route 53 service. | ||
I might be forgetting some details and further examples, but pretty much | I might be forgetting some details and further examples, but pretty much | ||
Line 291: | Line 308: | ||
interfaces were rather lacking. Some of their behavior may be or have | interfaces were rather lacking. Some of their behavior may be or have | ||
been shady - at least I've heard such - but didn't run into that | been shady - at least I've heard such - but didn't run into that | ||
- | personally. | + | 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. | ||
---- | ---- |