Current scenario: When a user connects to VPN with the full Pulse Secure Desktop client, multiple DNS records are published in DNS for the I've posted this on a couple forums now, and it seems like this is an issue regardless of which VPN solution you use. The clients are connecting and getting ip & dns information just fine. Refer to Cisco bug ID CSCtn14578, currently resolved on Microsoft Windows only, as of Version 3. Manually changing the DNS setting to a local DNS server on the protected network also works. x-adress of the Default “Register this connection’s addresses in DNS” for a VPN connection is not enabled and it is not possible to enable with the Add-VpnConnection PowerShell command. Not sure about the CISCO vpn client but on the SonicWall (We use a pre-Dell 3060 and v4. DNS Issues Again for URL Resolution AND VPN Client Access. When configuring Always On VPN, administrators have the option to enable DNS registration for VPN clients.
