Amazon Route 53 vs. Infoblox DDI (BloxOne)

- 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.

Incentivized

Infoblox DDI is an excellent alternative for Microsoft DHCP. It is a much more robust solution. It can also do DNS for your entire environment. However, if you are an AD environment, you will still need Microsoft DNS servers. The IPAM functionality is excellent for keeping track of your IP addresses.

Incentivized

• We can purchase our domain through Route 53 and can be hosted for cheaper prices in AWS.
• There are many number of routing policies you can go ahead with and this will come into picture when the customer satisfaction is required at most, so choose routing policy accordingly.
• As usual health checks are part of DNS systems, this is also provided at cheaper rates when total process is done in Route 53 service.
• It can be used as standalone application from AWS

Incentivized

• It creates and manages DHCP scopes very well.
• It identifies scope usage at a glance very well.
• It's very reliable and requires almost no maintenance to keep up and running.

Incentivized

• Price, it is not expensive ... but you can find some cheaper and even free DNS solutions.
• If you use non-AWS infrastructure, Route 53 doesn't have significant advantages on other services.
• AWS Route 53 does not support forwarding or conditional forwarding options for domains used on an on-premise network.

Incentivized

• Support
• UI/UX
• Reports

Incentivized

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

Incentivized

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.

Incentivized

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!

Incentivized

Support has always been responsive and knowledgeable.

Incentivized

Cloudflare is also similar in the features to Route 53. However, since we are completely hosted on the AWS cloud, we can't use Cloudflare for configuring our internal networks, and integrating with the other services. The API based integration of AWS via Terraform is another factor that allows us to automate most of our deployments and manage them programmatically

Incentivized

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 firewall security policies over our external caching grid members.

Incentivized

• All of our brand domain names (about 80 brands) are managed in there
• Many non marketing or brand domains are also in there
• There isn't any defined ROI because it's such a trivial and necessary service with impacts all business operations

Incentivized

• It has lowered the administrative burden on the network team.
• It has allowed us to provide IP address reports and given us another source for asset management validation.
• It reduces risk by centrally managing IP networks.

Incentivized