Hacker News Reader

Comment by StavrosK | Hacker News Reader

I did, largely because they take security seriously, but CloudFlare domains isn't a registrar: You can't set the nameservers to whatever you want. It's a CloudFlare lock-in service.

View on HN

The fact that you can't change the nameservers doesn't make them not a registrar. They absolutely are a registrar. Just one that doesn't let you change the nameservers.

But you know what? I'm okay with that. I honestly can't think of a scenario where I'd want to use any other nameservers.

> I honestly can't think of a scenario where I'd want to use any other nameservers.

What about the scenerio where you are thrown off of cloudflare service? A CDN is more inclined to ban sites to limit their own risks from litigious IP owners, etc, irregardless of who would win an actual court case.

Why would they continue allowing you to use the registrar but not the nameservers?

The registry probably has rules on what they can do to customers that curtail them; they are probably not bound (ha!) to anything wrt serving DNS requests.

I'm saying why would you let a CDN be your registrar in what sounds like an abnormal registrar agreement. (If they block you from the CDN, what happens then?)

> If they block you from the CDN, what happens then?

That could be an argument not to use their DNS service and their CDN service.

It shouldn't be an issue for the DNS service by itself.

I believe the path for Krebs when under DDOS was free CF cloud to akamai to special status (from Google?) Using CF domains with or without CF's normal services turned on would have made akamai impossible until a transfer process to a real registrar completed leading to an extra week or so of downtime.

Reply on news.ycombinator.com