Wireless DNS settings are not reverted after logging out from Pulse

[zanyterp]

i know we had seen something similar in earlier versions of pulse; I believe this has been resolved by the latest 9.0R6 and 9.1R4 (at the time of this post)

[ladjune]

Hello,

Zanyterp, do we have any release note or KB related to this issue ?

The https://kb.pulsesecure.net/articles/Pulse_Secure_Article/KB43851 says that it's resovled since 9.0R2.1

Can any body confirm that we can get rid of this issue with the 9.1R4 ? I know that's not easy to confirm anything while we cannot replicate it

Have a good day folks!

[jpcorzo]

Hello all,

wanted to reach out if any of you had success in resolving the static DNS issues. We have been seeing the same behavior since 9.1.R2 and support has suggested to upgrade to 9.1R6. Unfortunately we started the rollout to our pilot group and still see the same behavior. We've now testing 9.1R7 and behavior doesn't change. Support has provided a beta version but it seems it is not resolving our issue.

[ladjune]

do you still have the DNS issue ? this https://kb.pulsesecure.net/articles/Pulse_Secure_Article/KB44429 states that it's fixed with the 9.1R7.1 and above.

Or maybe you have the Cisco Umbrella client ? https://kb.pulsesecure.net/articles/Pulse_Secure_Article/KB44545/

[Jforio08]

We have the same issues also. Even upgrading to  9.1R9 (build)9189. The issue is still persist, our appliance is on the azure cloud. Mostly happens in Win10 machine.

[kita]

Yes, we are aware this problem is still occurring even with the latest Pulse Desktop Client.  The current scenario is known and working towards a fix:

1. End users disconnect the tunnel and the DNS setting should be restored properly.
2. End users reboot or wake from sleep, then the DNS settings are changed to the VPN Tunnel DNS setting.

We are still performing additional analysis of the issue, but it would be helpful to understand the steps taken by end-users when they see the problem.

[azuspam]

Hi,

I'm able to reproduce it almost everytime, on my side it happens when Pulse asked me if I want to extend my connection (after 4hours), if I declined, it'll disconnect after 5minutes then my DNS are not restored.

[azuspam]

Hi,

I'm able to reproduce it almost everytime, on my side it happens when Pulse asked me if I want to extend my connection (after 4hours), if I declined, it'll disconnect after 5minutes then my DNS are not restored.

[zanyterp]

are you using cisco umbrella or zscaler?
if you have not already opened a case, please do so

[dcxtbender]

Is there any solution to this with Cisco Umbrella roaming clients? We have Pulse Client 9.1.8 with system build 9.1R8.2 build 8511 and cisco Umbrella installed. We have this occuring on 5 out of 150 clients and we do have some FQDN resources defined in the split tunnel profile that users have to access over the tunnel and out to the internet via corporate network.

Will also say this just recently was reported in the last two weeks with no changes to environment