Share your experience using Cloudflare DNS

The easiest route - we'll conduct a 15 minute phone interview and write up the review for you.

Use our online form to submit your review. It's quick and you can post anonymously.

Your review helps others learn about this solution
The PeerSpot community is built upon trust and sharing with peers.
It's good for your career
In today's digital world, your review shows you have valuable expertise.
You can influence the market
Vendors read their reviews and make improvements based on your feedback.
Examples of the 83,000+ reviews on PeerSpot:

Senior Cloud Solution Architect at ITSG integrated Technology Solution Group
Real User
Top 5
A tool that offers good performance that needs to improve in areas like assessment and payload
Pros and Cons
  • "The most valuable features of the solution are performance and security."
  • "Areas like how assessment, discovery, and payload are dealt with and how it all comes into your organization can be considered when trying to make suggestions to Cloudflare for improvements."

What is our primary use case?

I had one design that I did, and it was related to Cloudflare API Gateway. Anything that comes in the front-end URL was basically something to deal with Cloudflare API gateway. Based on separations required in Cloudflare DNS, I set the traffic manager and then manage areas, like configuration, DDoS, and all such related areas. The aforementioned area helps manage the traffic that comes in, the load of the application, how you want to secure access and authentication, and then have the authorization.

In Cloudflare DNS, I use all the service modules the tool offers. The use cases attached to the solution can be related to areas like performance checks, protection, security modules, scalability, and allocation frequency of checking DNS.

What is most valuable?

The most valuable features of the solution are performance and security.

What needs improvement?

Cloudflare DNS is still a new tool in the market. I haven't come across any issues with the product. I did two designs with the help of Apigee and Cloudflare. I had done one design with the help of Apigee, while the other one was done with Cloudflare. In a lot of organizations, when it comes to the area of design, companies don't understand the broader perspective of what I try to do, how I try to do it or try to understand the right configuration needed. Areas like how assessment, discovery, and payload are dealt with and how it all comes into your organization can be considered when trying to make suggestions to Cloudflare for improvements. The improvements to be made in the tool can be based on your thought process instead of trying to bring up something that is over-prescribed or over-allocated by others, which won't make sense. Based on the functional requirements of every user of the tool, improvements need to be made to the product.

For how long have I used the solution?

I have experience with Cloudflare DNS.

Which solution did I use previously and why did I switch?

Initially, I used to use Apigee. Cloudflare DNS was chosen since management made a business decision to deal with the security requirements. Cloudflare DNS has a lot of different compliances and regulations, and related areas, like authentication and authorization, are introduced in the tool. Things change constantly in the product.

How was the initial setup?

When it comes to the product's initial setup phase, I have dealt with a lot of complexity when it comes to different applications, especially with the ones where I had to deal with AWS. Users need to bundle their applications, especially when there are critical applications, which may range from platinum, gold, silver, or bronze applications. Users need a landing zone, and they need to put everything in one particular landing zone, making it one of the Year's good use cases of the product to which a lot of people don't pay much attention; because of this, I feel it is my vision related to the product. I feel the companies need to see what the product can offer rather than just using the tool straight out of the box.

In every organization, there is a security component involved, and as long as the tool meets the requirements of the security layers in an environment, the product's setup phase is somewhat straightforward, but I am sure you could do a lot of different stuff with the tool. I don't think the setup process is complex, considering just a single source when it comes to the product, which revolves around the area of security. Based on the workload, users can make the setup process complex. I don't like straightforward processes, especially when dealing with critical applications that need to be designed in a particular way and could be totally different from the other applications in an environment. I am the type of person who likes to make the setup process more complicated and unique. When it comes to the setup process, users can choose different avenues to ensure that the resource separation is consistent in the setup phase.

What other advice do I have?

Cloudflare is designed to offer API Gateway, Traffic Acceleration, and DNS. Based on your pages and URL performance, Apigee is a solution you can use, and you could tie that in either AWS, Google, or Azure, or if you are making a SaaS application going through a front-end web component and have a pass-through gateway.

Cloudflare DNS is a pretty solid product as it is not tied to any cloud environment.

I rate the overall tool around seven or eight out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
Manish  Purohit - PeerSpot reviewer
Sr. Cloud Solution Architect at Green Point Technology Services (I) Pvt. Ltd
Real User
Top 5Leaderboard
A cloud DNS solution for all products hosted on Azure with simple to use DNS server
Pros and Cons
  • "The solution is stable, and the DNS servers are simple to use."
  • "Cloudflare should add more documentation and pricing to the cloud version."

What is our primary use case?

We use the solution for all our products hosted on Azure.

What is most valuable?

The solution is stable, and the DNS servers are simple to use.

What needs improvement?

Cloudflare should add more documentation and pricing to the cloud version.

For how long have I used the solution?

I have been using Cloudflare DNS for nine years, since 2014.

What do I think about the stability of the solution?

I rate the solution’s stability a ten out of ten.

What do I think about the scalability of the solution?

We never faced any problems with scalability. We’ve 100-200 users using the solution.

How was the initial setup?

The initial setup is straightforward and takes 15-20 minutes to complete if you want to start a new one. 

Deployment is pretty straightforward when you take a domain. You need to set the DNS to Cloudflare. Once that is done, it hardly takes one or two minutes to take effect. We first pointed to Cloudflare as our DNS. From there, it took a pretty simple configuration for our web browser.

What about the implementation team?

We deployed the solution by ourselves.

What's my experience with pricing, setup cost, and licensing?

We are using the free tier of the solution.

What other advice do I have?

When we started, Cloudflare was the best solution for us. We were using the free service, and it was working well. We never considered switching to Azure DNS because Cloudflare met our needs. Azure DNS has improved recently, and they now offer free SSL domain registration on App Services.

Overall, I rate the solution a ten out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate