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
F5 BIG-IP
Score 9.2 out of 10
N/A
F5 BIG-IP software from Seattle-based F5 Networks is a load balancing and application protection solution suite available on cloud or via virtual editions, on a subscription or perpetual licensing basis.
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, …
Amazon is priced higher than Google's DNS, but since our gear (Cloudfront, ALB, etc) is in AWS, Amazon Route 53 is easier to use sop we don't have to manage two vendors.
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 …
Amazon Route 53 DNS service is much better than GCP and Azure or any other cloud provider DNS service due to the fact that it not only provides basic DNS service but on top of it it offers firewall DNS feature i.e. rules and policies can be defined to allow/reject certain …
Since we are heavy users of AWS, it was only natural for us to go with Route53. It's well integrated with other AWS services, and domain creation and modifications can get automated with the infrastructure itself, with tools like terraform.
Amazon Route 53 is intended for simple websites that host HTML5 or static content. This is probably the default solution if you need something simple and don't want to rent a web server to host a website. It is good to host full functional but simple website or HTML5 game.
When working with AWS, Route 53 is hands down the better solution. If you live in GCP, then Google Cloud DNS is the way to go. GoDaddy is more of a consumer-facing product and is perfectly fine when Services are not being utilized in any Cloud Environment. Eventually, all of …
Route 53 is one of those essential services that you'll inevitably come across. It's one of the easiest to understand and configure in AWS, and using it is helpful if you're making use of any other components in the AWS ecosystem because most other components will …
Both Azure DNS and GoDaddy's DNS works great, but when you use AWS services and infrastructure, it is much easier to use AWS DNS service. Using AWS DNS service you can manage and maintain your infrastructure in one place, it saves some time. If you use AWS services, you can …
GoDaddy is fine if you just want to have a domain and set up a few simple records. But if part of your business is transferring domains and constantly updating records for new websites, email changes, and security, then a registrar-based DNS service just won't cut it. Route 53 …
Infoblox is the one we used on premises and briefly looked at for AWS. Route 53 however is well suited for our needs and was easier to implement. As AWS was already new for use, learning Route 53 anew made no difference in selecting it.
Route 53 is head and shoulders above GoDaddy. GoDaddy's DNS availability was problematic with us earlier on and at that time we made a decision to move our domains to Route 53 under Amazon. Since then we haven't experienced any DNS outages and it has been pretty rock solid. …
Route53 was used because I initially thought we were going to have our infrastructure on AWS. Once our team transitioned to Google Cloud, I was left scrambling to migrate our DNS solution to point to those servers instead. Because there is a mandatory 45-day transfer wait …
I have experience running several on-site DNS services such as PowerDNS, djbdns, bind, and others. Route 53 removes the need to manage the server and DNS software, allowing you to focus on the DNS content itself.
We chose Amazon Route 53 over Azure DNS for its advanced routing, built-in health checks, and seamless integration with AWS services like EC2, ALB, and CloudFront. Amazon Route 53 also supports domain registration and automated failover, which Azure DNS lacks natively. Its …
Porque nos es agnóstico a la tecnología implementada, de esta manera podemos evaluar en un futuro adquirir nuevas tecnologías y no depender de un solo vendor para implementar distintas necesidades que puedan surgir a futuro. Por lo tanto, se puede decir que los productos de F5 …
There's other, Kemp is one for that would be where we see the gap, where they do better in the mid-market space and then a 10 in the larger accounts. Those are probably the two that come to mind the most.
That's the one thing that really stood out. It was a lot easier to use from an administrator standpoint, so I think that's the one thing that really made our team decide to go with this product versus another competitor. Just ease of use.
Works really well. Like I was saying with the ease of use and I mean it's great hardware really fast, we've had zero issues with that, so it's been good
As I said previously, the F5 BIG-IP products are far and away the easiest, most robust and powerful application delivery platform I've ever worked on. The user experience was really the most noteworthy difference when using other products. The Kemp Load master platform was …
- 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.
Definitely in larger environments, more mature organizations that obviously have the budget to spend and want best in class. Where it struggles is those organizations that don't have the funding and money to spend on it and need more basic functionality. So I'd say that's smaller customers we've worked with and kind of mid-market. They tend to get scared when they get the quotes. Also we've had some struggles with account team consistency. So for the sales team, just a lot of turnover and a lot of missteps on customer calls.
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.
The great thing is the IP address management that's happening. When you set up the network it's very easy and you don't have to keep on configuring everything together. Again, it's very streamlined and it's one of the biggest players there in the market for this work.
Well, not necessarily the features. I find that we have to change our processes in order to kind of match what F5 BIG-IP does. And it's not a bad thing, it's just that a lot of my engineers want to do it their way, not they F5 BIG-IP way.
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 not difficult to understand the parts of application configurations and features. Setting up new virtual servers with multiple profiles, certificates, and nodes is easy for new users through the web interface, which also translates to programability in scripts, DevOps, or other configuration management use-cases. Users from different backgrounds such as networking and infrastructure can use F5 BIG-IP, while users who are familiar with API calls can easily configure objects without needing to understand the platform at all.
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!
On the occasions when we've had to engage f5 support, they have been great. They have always resolved our issues quickly and been easy to work with and professional. The reason I give them a 10 out of 10, however, is because when we've had issues that have crossed over between the f5 BIG-IP, our Cisco switches, and our Microsoft IIS server the f5 support representatives have been extremely knowledgeable about every product and device involved and have been able to troubleshoot end-to-end without having to engage other vendors.
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
I would say from a security perspective, because I manage security, availability is sort of the key area for us and making sure that is properly handled through BIG-IP, that is the biggest business success, I would say from the product perspective.