Bug ID 591268: VS hostname is not resolvable when DNS Relay proxy is installed and running under certain conditions

Last Modified: Oct 16, 2023

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

Known Affected Versions:
11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.1 HF10, 11.5.1 HF11, 11.5.2 HF1, 11.5.3 HF1, 11.5.3 HF2, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.3, 11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2, 12.1.1

Fixed In:
13.0.0, 12.1.2, 11.6.1 HF2

Opened: May 04, 2016

Severity: 3-Major

Symptoms

VS hostname is not resolvable when DNS Relay proxy is installed and running under certain conditions, it depends on client machine configuration. Symptom: negative record in windows DNS cache, can be verified by running ipconfig /displaydns

Impact

VS hostname is not resolvable: - 'Refresh' of webtop causes unavailable webtop - Recurring check report may fail due to DNS resolve issue

Conditions

Specific client machine configuration

Workaround

* Clean windows DNS cache: ipconfig /flushdns or * Disable DNS Relay proxy service

Fix Information

Now DNS Relay proxy service cleans up DNS cache after initialization mitigating issue described

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips