(Quote)

(Quote)

(Quote)

Messing with DNS/hosts/etc. won't work since it's done on the ISP level with a 302 redirect injected to the webpage.

Right. And now they can harvest DNS data as well, with their "non logging" resolver.

Their DNS is pretty performant. I'm coming to the same conclusion: if your server is optimized then CF won't bring much to you in most cases, and they'll MITM your traffic. Full cache with pagerules i

I still use them for DNS - and I have the domain set to "paused" to bypass all CDN and security features unless I need them for some reason or if I expect a surge in traffic.

(Quote)

I don't have a source on this but I believe it is true. Iirc you can infer a common account from the Cloudflare DNS servers assigned and the (shared/free) SSL certificate.

But how to circumvent big chief DNS?

At first I thought that it could be a block via DNS and I tried to change the dns of the users or mess with the hosts file but didnt work.

(Quote)

(Quote)

BunnyCDN is often faster than CF Free (but it was using their premium network, which comes with more locations than CF) BUT adding an extra DNS resolution that is sometimes (Australia if memory serves

(Quote)

netsh interface ipv4 set dns name="Ethernet 2" static 192.187.107.16

(Quote)

You can always setup a dns record like cdn.yourdomain.com and only turn on cloudflare for that cdn record and then use it just for your images, css, js, and stuff rather then turn it on for the whole

I now use Cloudflare only for DNS, and in my experience they are fantastic for that.

The problem with subdomains (be it with cloudflare, bunnycdn or any of the expensive options) is that it implies another DNS request. This takes time. That's a good point for CF with no subdomain: you