Bug ID 539013: DNS resolution does not work on a Windows 10 desktop with multiple NICs after VPN connection has been established in some cases

Last Modified: Dec 10, 2018

Bug Tracker

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

Known Affected Versions:
10.2.4, 11.0.0, 11.1.0, 11.2.0, 11.2.1, 11.3.0, 11.4.0, 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.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 12.0.0

Fixed In:
12.1.0, 12.0.0 HF1, 11.6.0 HF6, 11.5.3 HF2, 11.4.1 HF10

Opened: Aug 10, 2015
Severity: 3-Major

Symptoms

DNS resolution stops working on a Microsoft Windows 10 desktop when the VPN connection is established.

Impact

User cannot access resources by DNS name.

Conditions

This occurs when the client system meets all of the following conditions: - Running BIG-IP software version Hotfix-BIGIP-11.5.3.1.47.167-HF1-ENG.iso. - Running Microsoft Windows version 10. - Has multiple NICs and one of them is in the disconnected state, with a statically assigned IPv4 configuration.

Workaround

Disable disconnected NICs that have a statically assigned IPv4 configuration.

Fix Information

After VPN connection has been established, DNS resolution works, in the case of a Windows 10 desktop with multiple NICs and one of them is in a disconnected state and has a statically assigned IPv4 configuration.

Behavior Change