My main use case for F5 BIG-IP DNS is creating an active-active setup. With two data centers, if I want to make them active-standby or active-active, my major use case is to redirect traffic from or distribute traffic between the two data centers. Global service load balancing is a major use case for F5 BIG-IP DNS. It allows my organization to route user traffic to the most optimal data center based on factors including server health, geographical proximity, network latency, and application availability topology. Key benefits include high availability, improved application performance, disaster recovery, and intelligent traffic streaming. In my organization, I have used F5 BIG-IP DNS for global service load balancing by having two data centers, and for a few of the applications, it works as active-active, and a few of them are active-standby. For example, if I have data center one might be active for one application and the second is standby. If the application is working in data center one perfectly fine, then it functions as expected. If something goes down in data center one, traffic automatically switches to data center two. That is the major use case of this. For a few of the applications, we also have an active-active scenario. For most of the applications, we are using the global availability feature in F5 BIG-IP DNS, and for a few of the applications, we are using round-robin.
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.
We use it for data center (DC) operations. We have a three-tier, eight-site DNS configuration: one DC and two "DR." It's used for the failover of our applications and resolving hosts for applications.
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.
If the client wants to clarify that they are using the trusted packet and trusted browsing, they can use the DNS load balancing. F5 can provide some DNS service solutions. The client forwards the traffic, and the DNS is verified whether it can be trusted. If it's suspicious or malicious, it will be declined. If the traffic is observed to be trusted, valid, or legitimate, then it can pass.
- at a computer software company with 51-200 employees
Real User
May 22, 2023
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.
Associate Software Engineer at a tech vendor with 10,001+ employees
Real User
Top 10
Jan 23, 2023
The solution is used for balancing the load. For example, if someone calls the X-ray department, we use the solution to transfer the calls to different servers. This way, we are not putting a load on one specific server all the time. F5 BIG-IP DNS balances the load. For example, there are a hundred calls and I have ten servers, so every server will receive 10 calls instead of one server receiving all the calls.
Manager Cyber Security at Dept. of the Premier and Cabinet
Real User
Jun 28, 2022
One of our primary use cases for F5 BIG-IP DNS is local traffic management. We also use the LTM module, application services, load balancer, and advanced firewall. F5 BIG-IP DNS is a secure web gateway.
Head of Infrastructure division at a comms service provider with 501-1,000 employees
Real User
Jan 20, 2022
We are using the latest version of FS BIG-IP. We use the solution for classic reverse proxy authentication. We have approximately 800 internal staff and 2,000 external customers using the solution.
Technical Services Manager at ProComm technologies
Real User
Oct 4, 2020
We are a solution provider and F5 DNS Delivery is one of the products that we implement for our customers. This product is normally deployed for high application availability. That means we use the local traffic manager module the most. The DNS module is used for global server load-balancing and fail-over across data centers.
F5 BIG-IP DNS provides intelligent traffic management and DNS security, enhancing application performance and availability through efficient load balancing and DDoS protection.F5 BIG-IP DNS is a powerful tool for managing global traffic across data centers, offering robust security, scalability, and intelligent traffic steering based on server health and location. It balances traffic through its Global Traffic Manager and Global Server Load Balancing, ensuring high availability and improved...
My main use case for F5 BIG-IP DNS is creating an active-active setup. With two data centers, if I want to make them active-standby or active-active, my major use case is to redirect traffic from or distribute traffic between the two data centers. Global service load balancing is a major use case for F5 BIG-IP DNS. It allows my organization to route user traffic to the most optimal data center based on factors including server health, geographical proximity, network latency, and application availability topology. Key benefits include high availability, improved application performance, disaster recovery, and intelligent traffic streaming. In my organization, I have used F5 BIG-IP DNS for global service load balancing by having two data centers, and for a few of the applications, it works as active-active, and a few of them are active-standby. For example, if I have data center one might be active for one application and the second is standby. If the application is working in data center one perfectly fine, then it functions as expected. If something goes down in data center one, traffic automatically switches to data center two. That is the major use case of this. For a few of the applications, we also have an active-active scenario. For most of the applications, we are using the global availability feature in F5 BIG-IP DNS, and for a few of the applications, we are using round-robin.
I use F5 BIG-IP DNS for DNS protection, focusing mainly on DNS security, which is the primary use case, along with GSLB and load balancing as well.
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.
We use F5 BIG-IP DNS for internal and global DNS services for distributing content across our environment.
My use case includes load balance swaps and mostly exposing web applications to the Internet.
We use it for data center (DC) operations. We have a three-tier, eight-site DNS configuration: one DC and two "DR." It's used for the failover of our applications and resolving hosts for applications.
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.
If the client wants to clarify that they are using the trusted packet and trusted browsing, they can use the DNS load balancing. F5 can provide some DNS service solutions. The client forwards the traffic, and the DNS is verified whether it can be trusted. If it's suspicious or malicious, it will be declined. If the traffic is observed to be trusted, valid, or legitimate, then it can pass.
We use F5 BIG-IP DNS to handle traffic from multiple servers.
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.
The solution is used for balancing the load. For example, if someone calls the X-ray department, we use the solution to transfer the calls to different servers. This way, we are not putting a load on one specific server all the time. F5 BIG-IP DNS balances the load. For example, there are a hundred calls and I have ten servers, so every server will receive 10 calls instead of one server receiving all the calls.
This is a DNS solution.
I mainly use BIG-IP DNS to create business recovery scenarios.
I use BIG-IP DNS to replace our DNS servers.
One of our primary use cases for F5 BIG-IP DNS is local traffic management. We also use the LTM module, application services, load balancer, and advanced firewall. F5 BIG-IP DNS is a secure web gateway.
We are using the latest version of FS BIG-IP. We use the solution for classic reverse proxy authentication. We have approximately 800 internal staff and 2,000 external customers using the solution.
F5 BIG-IP DNS is used for global load balancing.
Our primary use case is DNS security.
We are a solution provider and F5 DNS Delivery is one of the products that we implement for our customers. This product is normally deployed for high application availability. That means we use the local traffic manager module the most. The DNS module is used for global server load-balancing and fail-over across data centers.