The support response time could use improvement. In critical cases, such as in the big environment projects, faster support is needed to address critical issues promptly.
Technical Consultant at a financial services firm with 1-10 employees
Consultant
Top 20
2024-02-26T13:20:52Z
Feb 26, 2024
The IP intelligent services are good for mitigating threats, but there are also false positives. So, it's not a standalone solution that can cover everything. F5 can consider enhancing the security profiles. Another area of improvement is documentation.
F5 is working on improving its identity management features. This is an important area for improvement, as it is a key component of Zero Trust architecture. So, when I was working on the zero-trust architecture, I noticed that there was a lack of documentation. The National Institute of Standards and Technology (NIST) has published some documentation and frameworks for ZTA implementation. In the NIST framework, multiple vendors can be used for different components of the architecture. For example, for identity management, common vendors include Azure, Intune, AWS, Cisco Duo, and Zscaler. I remember reading about F5 mentioned in the context of the ZTA framework. So, it's encouraging to read that F5 is being considered for ZTA implementations. Netskope is also using F5 for their ZTA solutions. I would also like to see all of F5's features integrated into a single box, as it would be the most beneficial for end customers. F5 is already enhancing its security capabilities. Initially, load balancing and security required separate devices, but now F5 offers solutions that combine both functionalities in a single device.
- at a computer software company with 51-200 employees
Real User
Top 20
2023-05-22T10:08:00Z
May 22, 2023
For me, F5 is a great solution. I think all the features we have in the solution now are good. In the product, one of the shortcomings is related to its configuration part. So, F5 issues certificates, and one needs to be a certified engineer to understand the product. Though you can find some manuals or F5 documents, in real life, it's very hard to understand this product. Documentation is an aspect that can be considered for improvement.
Associate Software Engineer at Tech Mahindra Limited
Real User
Top 5
2023-01-23T17:49:26Z
Jan 23, 2023
F5 BIG-IP DNS is quite old and may go extinct in a few days, months, or years, depending on whether it offers additional features. I first heard about the solution over ten years ago. People are moving away from it slowly to cloud-based load-balancing solutions. I don't have any strong evidence to back up my opinion, but that's what I believe based on what I've seen. Cloud-based tools are already available in the market, so no one will consider an on-prem tool unless it's affordable for small organizations. The solution can improve by adding cloud integration through plugins or additional configurations so we can use F5 BIG-IP DNS to communicate with the cloud.
Manager Cyber Security at Dept. of the Premier and Cabinet
Real User
2022-06-28T15:42:00Z
Jun 28, 2022
It would be great to see a F5 BIG-IP DNS cloud version. What we within the Australian government are looking at doing is utilizing a secured DNS service much the same as the English GCHQ version of their protected DNS service. That's a fully-managed external platform and it's used by multiple government agencies, so we get a better holistic view of all malicious DNS traffic that is occurring.
Head of Infrastructure division at a comms service provider with 501-1,000 employees
Real User
2022-01-20T10:15:00Z
Jan 20, 2022
The solution is complicated to use. It is difficult to write to. F5 BIG-IP DNS is powerful but challenging to use. I would like to see the login facilities improved, as well as more troubleshooting.
Hand management and working with rules are two areas that need to be improved. It would be beneficial to have information and categorize it for licensing, features, and what is included in which license. I would like to see more marketing documentation, rather than technical documentation.
Technical Services Manager at ProComm technologies
Real User
2020-10-04T06:40:34Z
Oct 4, 2020
The messaging between NGINX and F5 should be simplified. When I do presentations to customers, they sometimes are confused about this issue. It is not clear where NGINX gets into the network. I would like to see deeper integration with VMware in the sense that F5 compliments VMware, in the context of application availability. VMware has the Site Recovery Manager that looks at the virtual machine side of things. If there's deep integration with VMware, where F5 is able to figure out that an application is impaired and it wants to failover, it should be able to tell VMware to trigger that process. Better pricing for this product would make it more competitive on the market.
F5® BIG-IP® DNS distributes DNS and user application requests based on business policies, data center and cloud service conditions, user location, and application performance. BIG-IP DNS is commonly configured as a full proxy to provide global server load balancing (GSLB) for applications and DNS across architectures, and across the globe.The BIG-IP platform delivers DNS services with visibility, reporting, and analysis; scales and secures DNS responses geographically to survive increased...
The support response time could use improvement. In critical cases, such as in the big environment projects, faster support is needed to address critical issues promptly.
The analysis services needs improvement.
The IP intelligent services are good for mitigating threats, but there are also false positives. So, it's not a standalone solution that can cover everything. F5 can consider enhancing the security profiles. Another area of improvement is documentation.
The monitoring capabilities of F5 BIG-IP DNS could be improved. Sometimes, it requires additional work to monitor details effectively.
F5 is working on improving its identity management features. This is an important area for improvement, as it is a key component of Zero Trust architecture. So, when I was working on the zero-trust architecture, I noticed that there was a lack of documentation. The National Institute of Standards and Technology (NIST) has published some documentation and frameworks for ZTA implementation. In the NIST framework, multiple vendors can be used for different components of the architecture. For example, for identity management, common vendors include Azure, Intune, AWS, Cisco Duo, and Zscaler. I remember reading about F5 mentioned in the context of the ZTA framework. So, it's encouraging to read that F5 is being considered for ZTA implementations. Netskope is also using F5 for their ZTA solutions. I would also like to see all of F5's features integrated into a single box, as it would be the most beneficial for end customers. F5 is already enhancing its security capabilities. Initially, load balancing and security required separate devices, but now F5 offers solutions that combine both functionalities in a single device.
The solution's initial setup is complex compared to Fortinet.
The tool needs to improve its UI.
For me, F5 is a great solution. I think all the features we have in the solution now are good. In the product, one of the shortcomings is related to its configuration part. So, F5 issues certificates, and one needs to be a certified engineer to understand the product. Though you can find some manuals or F5 documents, in real life, it's very hard to understand this product. Documentation is an aspect that can be considered for improvement.
F5 BIG-IP DNS is quite old and may go extinct in a few days, months, or years, depending on whether it offers additional features. I first heard about the solution over ten years ago. People are moving away from it slowly to cloud-based load-balancing solutions. I don't have any strong evidence to back up my opinion, but that's what I believe based on what I've seen. Cloud-based tools are already available in the market, so no one will consider an on-prem tool unless it's affordable for small organizations. The solution can improve by adding cloud integration through plugins or additional configurations so we can use F5 BIG-IP DNS to communicate with the cloud.
The costs could always be a bit lower.
The initial setup could be easier.
It would be great to see a F5 BIG-IP DNS cloud version. What we within the Australian government are looking at doing is utilizing a secured DNS service much the same as the English GCHQ version of their protected DNS service. That's a fully-managed external platform and it's used by multiple government agencies, so we get a better holistic view of all malicious DNS traffic that is occurring.
The solution is complicated to use. It is difficult to write to. F5 BIG-IP DNS is powerful but challenging to use. I would like to see the login facilities improved, as well as more troubleshooting.
Hand management and working with rules are two areas that need to be improved. It would be beneficial to have information and categorize it for licensing, features, and what is included in which license. I would like to see more marketing documentation, rather than technical documentation.
Pricing could be reduced. Scalability is a concern, it could be improved.
The messaging between NGINX and F5 should be simplified. When I do presentations to customers, they sometimes are confused about this issue. It is not clear where NGINX gets into the network. I would like to see deeper integration with VMware in the sense that F5 compliments VMware, in the context of application availability. VMware has the Site Recovery Manager that looks at the virtual machine side of things. If there's deep integration with VMware, where F5 is able to figure out that an application is impaired and it wants to failover, it should be able to tell VMware to trigger that process. Better pricing for this product would make it more competitive on the market.