F5 BIG-IP DNS Reviews

We use F5 BIG-IP DNS for internal and global DNS services for distributing content across our environment.

One of the most effective feature of F5 BIG-IP DNS is its robustness and integration with our existing F5 infrastructure. It helps us to geographically connect and form an internal topology network with our clients.

The customer had two data centers, one northbound and one southbound. So both are physically in different locations. The customer's requirement was to load balance the traffic originating from any source. 

The primary data center should respond to every query. In the event of a disaster, server unavailability, or any other issues, the traffic should automatically redirect to the alternate data center. This sums up the scenario. 

The GTM feature is very good, It's very useful, especially if we have multiple data centers. If we want to load balance traffic from multiple data centers, the GTM feature is very useful.  

I am using F5 BIG-IP for various modules such as LTM (Local Traffic Manager), ASM (Advanced Security Manager), ABM (Application Policy Manager), and DNS. It helps in achieving scalability and high availability for applications, load balancing traffic, protecting applications from outside attacks, application security management, and DNS solutions for data center communication.

I have not worked on operational improvements directly since I am part of a partner team. Our role is to implement the solution for companies and then leave. However, F5 BIG-IP has helped achieve high availability, scalability, and protection from attacks.

We use the solution for the JPMC Logistics site. In our data center, we have deployed a couple of GTM devices to manage multiple sites across the globe. 

I sometimes encounter issues with the porting of F5 BIG-IP DNS. The porting functionality is not up to the mark when troubleshooting or attempting to access logs or connections. Additional attention is needed to ensure smooth operation. 

We use F5 for load balancing, reverse processing, and for web applications.

There is room for improvement in pricing. It is very pricey. So we don't have a performance problem at this stage. Because the appliances that we use are not the virtual edition. We know that NGINX started using the virtual edition for containers. But, from a performance perspective, we're happy. And from just the price perspective, it's very expensive.

We use F5 BIG-IP DNS to handle traffic from multiple servers. 

The solution is easy to configure and deploy. It is scalable and works without any downtime. F5 BIG-IP DNS is a flexible solution. 

F5 can completely close all issues in infrastructure about application delivery control because these solutions have all the instruments to close these issues.

Speaking about F5 BIG-IP DNS Global Traffic Manager, at a worldwide level, we get the opportunity to secure DNS records. Also, we have the opportunity to secure if customers have opted into DNS in the local area. You can make all DNS requests through only F5 BIG-IP DNS. Also, you can do any manipulation or modification with this traffic. In just one year, I can't know what F5 could do because there are a lot of things and a lot of instruments to push any task, especially because of the killer feature in F5 firewall. It also has a scripting language in which you can do whatever you want. If you know the TECO language, it's based on the TECO language. You can write, so we use something else to work with traffic, like an SAP application with APM and DNS, with which you can create some custom rules. So, if some feature doesn't have something in advance, you can create that feature. I think it's some of the best features of the solution.

I don't know precisely how it improved the functioning of my organization since, from my experience, I can say that it can close all issues in infrastructure, especially application publishing.

For caching purposes, we use F5 BIG-IP DNS.

The security features, DDoS mitigation facilities, and SQL configuration are the most valuable aspects of this solution.

The data mitigation is very good.