zlacker

[return to "Introducing Cloudflare Registrar"]
◧
1. ksec+tK[view] [source] 2018-09-27 17:11:09
>>jgraha+(OP)
I wouldn't have cared much about Domain Name Register just a week ago, but after what happen at Zoho, and all the horror story in the comments section from namecheap and others, Cloudflare Registar couldn't come at a better time.

I really wish Cloudflare at least made $1 or $2 Gross Profits per domain. Who paids for Domain Register Support? I would much rather be a "customer" than I am not sure where they are making money from my Domain.

P.S - If those were wholesale price, do other companies get heavy discount for signing up in bulks? How do other companies made money when they are selling it for $0.99 or $6.99

◧◩
2. conrad+3G1[view] [source] 2018-09-28 00:37:17
>>ksec+tK
Interesting that no one here has mentioned Google Domains:

- It has no up-sells

- I trust Google's security more than Cloudflare's

- It has decent customer support, unlike some of Google's other products

◧◩◪
3. brandu+5H1[view] [source] 2018-09-28 00:49:21
>>conrad+3G1
Aside from the price, one very good reason to be interested in CloudFlare as a registrar compared to Google Domains is that CloudFlare supports CNAME flattening [1] so that you can use a CNAME instead of an IP address for an A record (AKA "ALIAS" on DNSimple or Route53).

I'm using Google Domains right now, but have been using CloudFlare to host my DNS for ages for this reason alone. I'll think about transferring my domains to them when the time comes to take one service out of the equation.

[1] https://support.cloudflare.com/hc/en-us/articles/200169056-C...

◧◩◪◨
4. amluto+DT1[view] [source] 2018-09-28 03:56:43
>>brandu+5H1
Would it really be that hard to update DNS so that CNAMEs on non-leaf domains actually worked? Sure, IoT devices might never update, but I’m not sure that actually matters.
◧◩◪◨⬒
5. toast0+102[view] [source] 2018-09-28 05:48:21
>>amluto+DT1
If you got the rfc changed today, I suspect you wouldn't be able to reliably use it for about 20 years. 5 years for everybody to pick it up in new software, 5 years for new hardware to not be shipped with the old software, and 10 years for all the old software and hardware to die out.

And all for what? So you can cname example.org instead of www.example.org? Doesn't seem worth it. Also, consider that in 20 years, we're likely to consider IPv6 only servers, and a host can more easily offer you a IPv6 ip that they can commit to serving your traffic for a long time on. It's a lot harder to be flexible with IPv4 addresses.

[go to top]