A while back there was an issue with the Pulse Client not changing the DNS settings back after a disconnect. This meant the users wouldn't be able to connect to anything because the DNS settings were pointing to the corporate/VPN DNS address.
I ended up creating a script to reset the DNS settings on user login which got around this issue. I ended up disabling the script because it had been a while, but it appears there's still a bug with the client?
we expect this to be working in user-space tunnels with the 22.x client. there is an on-going investigation with machine tunnels; however, we are not currently aware of failures with user connections. what are you seeing?
Ok. We're just using user connections on the 22.x client. People connect to the VPN, disconnect, but their wifi adaptor still has the DNS settings set as static to our corporate DNS settings and doesn't change it back to DHCP.
Is there anyway on the VPN appliance to not set the DNS as static on their adaptor?
you have two options (both of which are equally viable; it depends on what works best for your use case):