We performed a comparison between Amazon Route 53 and Cloudflare DNS based on real PeerSpot user reviews.
Find out in this report how the two Managed DNS solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The solution is cost-effective."
"The scalability is the most valuable feature."
"The solution effectively monitors the health of resources and provides good identity access management."
"Amazon Route 53 is a DNS resolution service that helps you to map your hostname to another hostname."
"The solution offers you the flexibility to control configuration rules."
"We use Amazon Route 53 for dynamic naming and routing policy."
"Technical support from Amazon is very good...Overall, the product is stable."
"It stands out for its user-friendly interface, seamless integration with other AWS services, and ability to efficiently manage DNS, making it a valuable tool for various deployment scenarios, including those involving Kubernetes on AWS."
"I get a lot of value from Cloudflare's API because it enables you to build a separate environment inside the solution. You can create a domain for performing test requests before you move to the production environment and connect various domains."
"The solution automatically detects and responds to certain types of traffic based on geolocation."
"The attacker won't have details since my public IP is anonymous. It offers us good privacy."
"It is a stable solution. I rate the stability a ten out of ten...I rate the scalability a ten out of ten."
"Its most significant benefit to date is the speed with which it refreshes DNS records on the internet once you change it. If you are changing a website or registering a new record, it is very quick."
"The most valuable feature of Cloudflare DNS is its global reach and it is always evolving."
"Its ease of integration with Office 365 and the fact that it's a good product compared to what I had before"
"The most valuable feature of the solution is external DNS. It is also very secure. They have their own main server and once you configure it, the product takes care of everything. There are no issues in resolving IPs and low latency is also present."
"The multiple routing policies present in the product have certain shortcomings where improvements are required."
"The solution should include more robust and secure services for hardening sites."
"When we are looking at the model registry, it may be not clear sometimes. For example, if you use a single grid model and group or registry, it has a different SDK in the pilot. And it may be not so comfortable to use both of them because it is two different places for keeping things in order."
"Supporting DNS check is one feature missing in the solution."
"Streamlining and optimizing processes related to Procter, VPN workflows, and other subjects based on specific needs would allow for continual improvement and adaptation to the evolving requirements of the system."
"The product could improve its price."
"There are no detailed logs, and they should implement that in the solution."
"The platform is more complicated to learn than one of its competitors."
"Cloudflare should add more documentation and pricing to the cloud version."
"There might be helpful if there was some web application firewall feature."
"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 tool needs to improve caching of servers. The product needs to include PFX certificate as well."
"We have noticed multiple instances where Cloudflare falsely indicates that our servers are down, even when there is no actual load on them. This makes it challenging for us to identify the exact issue."
"Cloudflare's free plan is limited to 5,000 records for their free plan. They should increase that. For example, if I create a domain called abc.com and a subdomain called a.abc.com, my record count will be two. I can make a maximum of 5,000 subdomains. However, if we use our own DNS hosted on another provider, there is no limit. Their free plan also lacks name server customization."
"The analytics, basically the dashboard, doesn't have much to it."
"Cloudflare doesn't have a reverse lookup. We can only do a DNS lookup to get the IP address from the hostname. It doesn't work if you want to look up the hostname from an IPA address."
Amazon Route 53 is ranked 3rd in Managed DNS with 19 reviews while Cloudflare DNS is ranked 1st in Managed DNS with 13 reviews. Amazon Route 53 is rated 8.6, while Cloudflare DNS is rated 8.6. The top reviewer of Amazon Route 53 writes "Provides clear documentation, easy to understand, simplifies management and efficiently handles our domain-related configurations and DNS records". On the other hand, the top reviewer of Cloudflare DNS writes "A tool that offers good performance that needs to improve in areas like assessment and payload". Amazon Route 53 is most compared with Azure DNS, Google Cloud DNS, Cisco Umbrella, Akamai Edge DNS and IBM NS1 Connect, whereas Cloudflare DNS is most compared with Quad9, Azure DNS, Google Cloud DNS, Cisco Umbrella and Hurricane Electric Free DNS. See our Amazon Route 53 vs. Cloudflare DNS report.
See our list of best Managed DNS vendors.
We monitor all Managed DNS reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.