F5 BIG-IP DNS vs. F5 BIG-IP Local Traffic Manager (LTM)

F5 BIG-IP DNS is well-suited for any organization looking to improve their Authoritative and Local DNS security and performance capabilities.

Incentivized

There was a need to have the DR environment to be available actively but not to send the traffic unless the production is down The F5 BIG-IP Local Traffic Manager (LTM) priority feature helped achieving it. It was well suited in handling the HTTP headers using polices and iRules. It was less appropriate from the application security perspective in the current version. But after attending the AppWorld 2024, I see a lot of ways to protect the network and the application with several features.

Incentivized

• The easy of importing DNS records into the BIG-IP
• The ease of searching and locating records
• The speed of creating multiple records when you need to duplicate effort.
• The DNS dashboards to see requests and data points.

Incentivized

• Does web traffic management very well.
• To allow API's to work with our in house services
• To make intelligent load balancing decisions.

Incentivized

• More support documentation will be a nice to have.
• I have not automated DNS deployments yet, but it would be nice to have ansible libraries for this module. (I have used ansible for many others).

Incentivized

• Time investment in creating Virtual Servers across many LTMs
• Ability to change object names after creation
• Support ability to troublshoot iRUles

Incentivized

F5 DNS is like DNS with out training wheels and data that can help you make real changes and improvements

Incentivized

As far as I know, F5 BIG-IP Local Traffic Manager (LTM) from F5 is the best and the number of features is unmatched compared to its competitors. The first-time setup is also quick and easy and the product behaves as a full proxy which is rarely seen. The support is good and also the help articles are numerous.

Incentivized

• Protection against security threats using DNS as a vector.
• Protection against security threats targeting DNS itself.
• Provide top user experience to application clients, by directing their requests to where they will be treated with the best performance.

Incentivized

• Negative impact in that it makes it very easy for applications to be spun up but cleanup of old/ unused deployments do not happen causing resources to be consumed unnecessarily
• When used in a multiblade viprion guest, issues with backplane and blade replication causing impact
• Ability to deploy multiple instances helped with network segmentation

Incentivized