Reset Search
 

 

Article

KB44429 - How to Restore Network Connectivity due to DNS Settings Issues on Physical Adapter and FQDN Split Tunneling is configured?

« Go Back

Information

 
Last Modified Date7/15/2020 11:43 PM
Synopsis

How to Restore Network Connectivity due to DNS Settings Issues on Physical Adapter and FQDN Split Tunneling is configured?

This article describes a scenario where domain name server (DNS) settings are not properly restored on the physical adapter when using FQDN Split Tunneling or Device Only DNS is enabled.
Problem or Goal
End users lose their network connectivity during a tunneled connection.  End user may notice that all DNS resolution will fail, but able to connect to resources via IP Address.
Cause
This issue is caused due to DNS settings not being restored on physical adapters (Ethernet/Wireless) when using FQDN split tunneling. This issue may occur during wake up after the machine was put to sleep/hibernate and restart/reboot scenarios.
 
Note: Applicable only to Pulse Desktop Client (Windows)
Solution

To workaround this issue, use IP-based split tunneling instead of FQDN split tunneling if the problem is occurring for reboot scenarios. 

Note:
  1. Sleep/hibernate scenarios are fixed only in Pulse Desktop Client 9.1R6 and above.
  2. An additional fix is planned for Pulse Desktop Client 9.1R7.1 (tentative for the week of July 20th) to address an issue where DNS settings are not properly restart during a reboot or restart scenario. The DNS restore process is abruptly stopped and the DNS restore is unsuccessful before reboot or restart occurs.

To help root cause the issue, please create the following registry entries for debugging purposes:
// Check the DNSRestoreNumTries value from registry and set the retry count, set this value to 10 (Decimal).
// "HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Pulse Secure" : "DNSRestoreNumTries"
// Check the DNSRestoreLog *value from registry and enable the DnsRetry.log. Set this value to *1
// "HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Pulse Secure" : "DNSRestoreLog"

By default, the number of DNS restore attempts is 5.  Please try to increase to 10 and see if this improves the results.  If not, please add a registry entry for the to enable the DNSRestoreLog, replicate the issue and gather the Pulse Client logs to Pulse Secure support for additional review.
 
Related Links
Not Applicable
Attachment 1 
Created ByRaghu Kumar

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255