Amazon Route 53 is a Cloud Domain Name System (DNS) offered by Amazon AWS as a reliable way to route visitors to web applications and other site traffic to locations within a company's infrastructure, which can be configured to monitor the health and performance of traffic and endpoints in the network.
$0.40
Per Zone Per Month
Infoblox DDI (BloxOne)
Score 8.0 out of 10
Enterprise companies (1,001+ employees)
Infoblox DDI consolidate DNS, DHCP and IP address management into a single platform, deployed on-site and managed from a common console.
N/A
Pricing
Amazon Route 53
Infoblox DDI (BloxOne)
Editions & Modules
Standard
$0.40
Per Zone Per Month
Queries
$0.60
Per Million Queries
No answers on this topic
Offerings
Pricing Offerings
Amazon Route 53
Infoblox DDI (BloxOne)
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Amazon Route 53
Infoblox DDI (BloxOne)
Considered Both Products
Amazon Route 53
No answer on this topic
Infoblox DDI (BloxOne)
Verified User
Employee
Chose Infoblox DDI (BloxOne)
Infoblox DDI supports services across hybrid platforms and the capability to switch from appliances to VMs has added to the mobility of the applications. Setting up two grids(Internal and external) helps manage and segment the network in scopes of DNS and DHCP and apply …
- Routing users to the closest or best-performing resources: Route 53 allows you to use geolocation and latency-based routing to route users to the resources that will give them the best performance. - Load balancing: Route 53 can be used to distribute incoming traffic across multiple resources, such as Amazon Elastic Compute Cloud (EC2) instances or Amazon Elastic Container Service (ECS) tasks, to improve the availability and scalability of your application. - Managing domain names: Route 53 can be used to register domain names and manage DNS records, making it a one-stop solution for managing your domain name and routing traffic to your resources. Scenarios where Route 53 is less appropriate include:Applications with very high query rates: Route 53 is designed to handle millions of queries per second, but if your application generates an extremely high query rate, you may need to use a specialized DNS service.Applications that require very low latency: Route 53 is designed to provide low-latency DNS service, but if your application requires ultra-low latency, you may need to use a specialized DNS service or a self-hosted DNS solution.Applications that require advanced security features: Route 53 provides basic security features such as DNSSEC, but if your application requires advanced security features such as DDoS protection, you may need to use a specialized DNS service.
We have been using Infoblox DDI for 10+ years at Pitney Bowes. The experience has improved gradually. As far as DNS and DHCP go, they are amongst the top ones offering this service. The support is great and downtime is minimal. The IPAM is always scanning the network to update the IP database. The caching servers reduce the lookups towards the internet. All in all, this is a must-have in every data center.
Uptime - Route53 is highly performant and available. We have had only 3-4 instances in the last 12 years when we had any downtime or outages due to Route53.
Extensive API layer on Route53 that allows integration with external tools and SDK's (Boto, Terraform, etc)
Closely integrated with the other AWS services. Makes it easy to operate the infra.
During initial setup when you are using Route 53 or DNS systems for very first time, there are little number of documentation from AWS which is kinda of little tough. But, once you get hold of it, its a cake walk for everyone.
Health checks are kinda of little costly when Compared to other big players, but that doesn't affect much when you compare its uses.
Reporting is an add-on feature, which requires another system. The basics are free.
Network systems management and reporting is another add-on. However, this is significantly expensive.
The pricing structure is somewhat ridiculous. It's the least expensive system for a duel site. It has 10s of thousands (for a full feature IP tool), but in our case is crazy expensive.
You need to know what DNS is; this is a tool built for developers who already know the technology and are just looking for a DNS management tool. The tool is very usable given that. If you're not familiar with DNS, Route53 isn't really for you and you won't find it to be very usable-- you'll need to go read the documentation, and that will start with learning what DNS is
It's generally easy to navigate through all of the menus. It's also very powerful in that there are many options available for configuration, allowing one to take advantage of IP address management tools. This tool is definitely a leader in the space, and provided you have the budget, is a very good investment. The team that uses it will appreciate the tool.
Until today, I have never needed support to Route53 because the documentation is great. But, I have needed it for other services. And they're near perfect always. Except that they don't have Portuguese support yet and they're sometimes slow to answer (48 hours in non-critical ones, in two tickets). But usually, they're amazing!
We purchased our domain names through Networksolutions.com and do rely on their DNS services for basic functionality (SPF hard reject records, etc.), since it was included at no cost; however, for our main domains, we utilize Route 53 because of AWS's high availability, reasonable cost, and capabilities to integrate with EC2 and other security certificate services to make hosting on AWS simple. We also front-end some of our sites with Cloudflare and while it's not as streamlined as using AWS natively, it does a good job.
Between Solarwinds IPAM and Infoblox, I'd still choose Infoblox even if Solarwinds is prettier to look at. Infoblox does a fantastic job at managing IP space and really doesn't have much competition in this space. Ease of use, being able to queue changes and having all this done via a web interface that just works is very convenient.
