News for hackers. Stuff that matters.
Re:Cloudflare S-1 by tracker1 on Thursday August 15, 2019 @03:26PM (#20708762)
DNS for sites protected by cloudflare are on cloudflare's DNS afaik.
Re:Cloudflare S-1 by llama052 on Friday August 16, 2019 @12:42AM (#20712232)
That's optional and has been for awhile now I believe, you can CNAME from your own DNS provider. While that does rely on their DNS for that one record, it means you still have control to changeover if need be.
Re:Cloudflare S-1 by tracker1 on Friday August 16, 2019 @03:40PM (#20718912)
And, that doesn't change the point... the website protected by cloudflare still controls the effective dns for that site. The lookups are controlled, and CF is a mitm vector.

A client deployment of an app, that the client had behind cloudflare was making 80ms API requests take 8 seconds. It's not always great.

I'm not saying that there aren't alternatives, and that people have to use Cloudflare... but there really isn't much in the way of an alternative at even a similar level of support and price on the low/introduction side of things. The issue regarding recaptcha can be REALLY annoying, especially on a non-google browser.

Re:Cloudflare S-1 by _bxg1 on Thursday August 15, 2019 @03:42PM (#20708903)
Right but there are plenty of other options for DNS providers.
Re:Cloudflare S-1 by tracker1 on Thursday August 15, 2019 @04:58PM (#20709594)
There are... but as CF correlates to a significant portion of internet traffic and DNS lookups, it's not like the original point is invalid.