Last Modified: Apr 10, 2019
See more info
Known Affected Versions:
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.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 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, 11.6.1, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 11.6.3, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 11.6.4, 12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 12.1.4, 22.214.171.124, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1
Opened: May 11, 2017
DNS resolution fails for hostnames that can be resolved only by internal Network Access DNS. DNS Relay Proxy does not properly forward DNS requests to internal DNS servers when the virtual server is accessed using a hostname. Note: This problem does not occur when the same APM virtual server is accessed by IP address.
-- DNS resolution does not work for hostnames that can be resolved only by internal Network Access DNS server. -- DNS resolution (using ping or via browser) works for other hostnames that can be resolved by local DNS. -- nslookup does not work for any hostname.
-- DNS relay proxy is present. -- IP filtering engine is enabled. -- Split tunnel config with no DNS-include space. -- Access virtual server by hostname. -- Running Microsoft Windows v10.
You can use either of the following workarounds: Note: nslookup can be enabled only with workaround #2. 1. While specifying split tunnel configuration, make sure DNS scope is also split by specifying the include DNS scope in the configuration. With this workaround, ping and browser work while accessing hostnames that can be resolved only by internal Network Access DNS. DNS requests received on the physical adapter will be forwarded to the internal Network Access DNS server when the scope pattern matches. 2. This workaround involves modifying the Windows Registry. Note this warning from Microsoft about modifying the registry: "Warning: Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk." Add the following key: -- HKLM\SOFTWARE\Policies\Microsoft\Windows NT\DnsClient -- Set DWORD "EnableMultiHomedRouteConflicts" to 0 (zero). This workaround restores Windows DNS client behavior to pre-Windows 10, so DNS relay proxy will create listeners on loopback for incoming requests, and the driver will redirect DNS requests to the listener on the loopback. The IP filtering engine allows all traffic on loopback, so DNS resolution via ping, browser, and nslookup all work as expected.
Now the Windows Edge Client DNS Relay Proxy service correctly forwards requests to client-local DNS servers if the name resolution is not avilable on the APM-local DNS servers.