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. toast0+xI1[view] [source] 2018-09-28 01:11:12
>>brandu+5H1
Note that if you're cnaming to some thing that is doing dns based load balancing or Geo targeting, introducing flattening in the middle may reduce the ability of your provider to do those things.
◧◩◪◨⬒
5. danger+EZ1[view] [source] 2018-09-28 05:39:45
>>toast0+xI1
What is the alternative for a root domain A record? You are saying use a direct ip to the load balancer instead?
◧◩◪◨⬒⬓
6. toast0+KE2[view] [source] 2018-09-28 14:54:46
>>danger+EZ1
If you want dns based load balancing on the root domain, you really have to delegate that domain to your DNS based load balancing service.

Otherwise, set up a couple stable IPs to redirect to a subdomain and nothing else. (I'm comfortable putting two quality machines in different data centers for this, but you can use a load balancer it you have access to quality load balancer). If all of your published urls have www (or m) and all of your inbound links have it too, it's not really a big deal if the root domain is unreachable for some time in the event of a server/load balancer/datacenter failure.

[go to top]