Is it OK to use Cloudflare DNS?

Is 1.1.1.1 still the fastest DNS?

I've been using 1.

1 as my primary DNS server for years now, after switching from noip.com as it was the only option when I moved to the UK and I wanted a static ip and I didn't want to pay for it at the time. That service still seemed good enough so I started doing that and never really found an alternative until now. Now that's turned out to be faster for some unknown reason and a better overall solution.

It turns out to be much easier and faster to just set one up now anyway using your browser - even though it hasn't changed. I don't want to know how much money they've made off of it. Maybe there are some interesting statistics?99 and added a paid version too now. Which I'm not happy about because I like 1.1 and if they add a paid version why wouldn't I add their other services such as no-ip?

If its the dns cache then your connection speed is limited not by any DNS traffic ( which itself shouldn't be that big anyhow) but rather by your ISPs upstream bandwidth. Your connections will also suffer from having the dns cached, especially if you're using Bcast (broadcast) addresses. This means anycast (whereas the first address is the primary and the rest are backup) will likely better than broadcast to some extent.

Now if that's the case then you can run a second server or two on the same (or even different) ISP's network from where you are in order to spread the load. Yes, it's that bad for caching? The idea of caching was for me to not have to think about DNS - why am I wasting all that valuable time. That's why I switched to 1.1 and I just need my browser to do a search for whatever domain I'm going to visit. Also works nicely with noip.com in the sense that if I use it then it caches the IP but if I choose not to it'll look up the ip every time.

If its the dns cache then your connection speed is limited not by any DNS traffic ( which itself shouldn't be that big anyhow) but rather by your ISPs upstream bandwidth.

Is 1.0 0.1 Cloudflare DNS?

I was looking at how Cloudflare works and wondering, why do they use DNS when they cache DNS?

Is it just because they are faster? Is it because I have to create a DNS A record with Cloudflare for each site that I want to host in an SSL environment? This is so they can serve DNS on port 80 (for the first page) and then have the secure page that you serve as the HTTPS page for their domains. Yes it's faster because there is less data. But, there is not always one cloudflare.com per customer.

We have a customer that serves up 30 domain names. 30 servers. We have them setup in a similar fashion to what you have. We can actually configure them using the DNS A record we setup on the main Cloudflare account that we own.

The point of adding that A record on Cloudflare is so that when you visit cloudflare.com, it takes you to our domain. But, if you were to make a request to cloudflare.com/anything, we will forward your request to whatever CDN we have for the cdn.com server and that server will then handle it as a cache for that CDN server. So cloudflare.com resolves to server1.com and everything under cloudflare.com, all requests go to the CDN server. If cloudflare.com/anything is going to cloudflare.com/somethingelse, the request will go to server2.com

Basically our CDN server will take the request and forward it to one of the 3 Cloudflare servers based on where the request is going. Thanks for clearing that up. But, I still think that caching DNS should be separate. That way you don't have to make separate A records for each site and everything could be cached in one DNS server.

What is Cloudflare 1.1.1.1 DNS?

Cloudflare 1.

1 DNS (also referred to as 1.1) is a virtual domain name system (DNS) that lets you set up nameservers in one place and access them from anywhere. It's simple, private, and cost effective. Cloudflare 1.1 DNS is a Cloudflare service.

Why use Cloudflare 1.1 DNS can help you set up custom domains and point them at different subdomains in your Cloudflare network.

Custom domain names are great for many things including setting up sub-domains for websites, marketing pages, content distribution networks, media outlets, and more. It's easy to host more than one site using custom domains. For example, you could have one website under mydomain.com and another under myblog. You could also host multiple sites on a single custom domain using Cloudflare's Content Distribution Network.1 DNS offers a simple way to connect multiple Cloudflare users with custom domain names.

For example, mydomain.com is used to host a website. This same site is also hosted on myblog.com where the content of the website is stored in a bucket owned by Cloudflare. Cloudflare DNS makes it easy to point mydomain.com and myblog.com at the same Cloudflare user account. The sites are then served from the user's IP address via Cloudflare's CDN.

You can use Cloudflare DNS with any Cloudflare user. You can even use it to manage the hostnames of multiple Cloudflare users. You can also use it to manage the hostnames of users in your organization. With Cloudflare 1.1 DNS, your organization can have its own internal DNS zone for users to use.

With Cloudflare 1.1 DNS, you don't need to know or manage the hostnames of multiple Cloudflare users. You only need to manage the Cloudflare user account you use.

Setup Cloudflare 1.