Bug ID 564262: Network Access does not work if DNS cannot be resolved on client and PAC file contains DNS resolution code

Last Modified: Feb 13, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP APM(all modules)

Known Affected Versions:
11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 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.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 12.0.0, 12.0.0 HF1, 12.0.0 HF2

Fixed In:
13.0.0, 12.1.0, 12.0.0 HF3, 11.6.1, 11.5.4 HF2

Opened: Dec 22, 2015
Severity: 3-Major
Related AskF5 Article:
K21518043

Symptoms

Tunnel server component of Edge client crashes, and user cannot establish VPN.

Impact

Tunnel server crashes and user cannot establish VPN.

Conditions

-DNS names cannot be resolved on client system. -PAC file used to determine proxy server uses JavaScript DNS resolution function.

Workaround

Enable DNS resolution on client or do not use DNS resolution JavaScript functions in PAC file.

Fix Information

Network Access now works as expected even when DNS cannot be resolved on client and PAC file contains DNS resolution code.

Behavior Change