We've been using MX client VPN for a few years now and overall it's been successful. We don't have too many issues, but I did notice that clients connected to the VPN are not registering in DNS. MX hands out the IPs from a range outside our normal network. We're using Windows DHCP/DNS for internal systems. We have 50 Z1 devices where clients there will register to our internal DNS, but the client VPN doesn't seem to be working the same way.    We rolled our client VPN out via a PowerShell script and the 'Register to DNS server' option in the advanced settings is not checked for VPN connections. I don't see an obvious option to check that box in the add-vpnconnection or set-vpnconnection cmdlets for PowerShell. Does anyone have any advice?   In most cases client VPN devices not in our DNS probably isn't a big deal, but we do have some remote users who only use the client VPN and we'd like to be able to push things to them via DNS name vs looking up their IP and manually pushing.  ... View more