Bug ID 573581: DNS Search suffix are not restored properly in some cases after VPN establishment

Last Modified: Oct 07, 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.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.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.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

Fixed In:
13.0.0, 12.1.0, 11.6.1 HF1, 11.5.4 HF2

Opened: Feb 12, 2016

Severity: 3-Major

Symptoms

Modified DNS suffix after VPN establishment and closure may result in failure to resolve some DNS names

Impact

DNS suffixes are not restored properly which may lead to incorrect resolution of certain DNS names.

Conditions

DNS Relay proxy service is stopped in the middle of VPN session. User's machine is rebooted.

Workaround

Any of the following workarounds 1) Do not stop DNS relay proxy service in the middle of a VPN session 2)Restore DNS search suffixes manually.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips