Bug ID 456911: Add BIG-IP hostname to system's static DNS host entries

Last Modified: Sep 13, 2023

Affected Product(s):
BIG-IP APM(all modules)

Known Affected Versions:
11.5.1 HF1, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.6.2 HF1, 11.2.1, 11.4.0, 11.4.1, 11.6.0, 11.6.1, 11.6.2, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 12.1.0 HF1, 12.1.0 HF2, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2

Fixed In:
12.0.0, 11.6.0 HF5, 11.5.1 HF6

Opened: Apr 11, 2014

Severity: 4-Minor

Symptoms

In a GTM deployed configuration BIG-IP resolves to different IP addresses. If the IP address used when establishing a network access connection is different while accessing (after the network access is established) a corporate resource, then this corporate URL access will be denied.

Impact

Access to corporate resources might be denied.

Conditions

GTM deployment. BIG-IP network access configuration and corporate resource resolves to different BIG-IP than the one to which network access is established.

Workaround

Configure BIG-IP system with static host DNS entry.

Fix Information

A certain scenario in GTM deployment was fixed where access to certain corporate resource might be denied despite network access connection.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips