Wireless DNS settings are not reverted after logging out from Pulse

[zanyterp]

I do not believe this will be possible with Umbrella due to how it changes DNS on the client.
Can you test with 9.1R10 on if you see the same behavior?
Are those five the only ones that have Umbrella and FQDN policies?

[scoutt]

I hate to chime in but we are starting to see this on 9.1R11.3. Never happened until we went to the cert fixed version. We are also not using the Cisco umbrella client, just the Pulse Client. We also are using "Search client DNS first, then the device"

Shall I create a ticket? I hate to do that as you giuys are slammed and it takes so long to get somebody to call.

[zanyterp]

do you have zscaler installed as well?
we are aware of an issue with zscaler that we are investigating as well; the most efficient way to avoid this is to not use FQDN configurations for split tunneling and/or ACL.

[scoutt]

No, we are not using zscaler. Thing is I have a machine in my office and can't make it happen but the user takes it in the field and happens all the time. We have a update tomorrow so I will see if that changes anything.

[zanyterp]

thank you for the update & confirmation
symptomatically this matches something we are investigating. can you create a test role & profile for the user to test with IP only configuration (no FQDN policies) and confirm that the issue does not occur?

[scoutt]

So basically you want me to make a new split-tunnel network policy and not use FQDN Resources? Leave it blank and only use the IPv4 resource?

[DerFalk]

Same here, v9.1.11 DNS-settings set to manual and not been reset after logout.

[zanyterp]

hi @scoutt
yes, create a policy that does not use FQDN for the role. the other option will be to upgrade the client to 9.1R12

[zanyterp]

@DerFalk
are you seeing that it is working successful or are you seeing that dns settings are not restoring as expected?