Hi, > as Windows10 Always uses local DNS servers this represents a built-in DNS > Leak. > At present, the only solution appears to be to de-configure default DNS > servers after connecting to a VPN. > I wonder if anybody has come up with a scripted solution (or other). > > https://community.openvpn.net/openvpn/ticket/605#ticket
We just ran into this problem as well. User cannot access resources on our network as pushed dns setting do not get used. Dns servers get properly pushed to the client, this is what the client sees: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : TAP-Windows Adapter V9 Physical Address. . . . . . . . . : 00-FF-94-B7-29-9B DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::b018:750b:7f60:4e93%34(Preferred) IPv4 Address. . . . . . . . . . . : 172.16.1.150(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.252 Lease Obtained. . . . . . . . . . : donderdag 15 oktober 2015 15:05:15 Lease Expires . . . . . . . . . . : vrijdag 14 oktober 2016 15:05:15 Default Gateway . . . . . . . . . : DHCP Server . . . . . . . . . . . : 172.16.1.149 DHCPv6 IAID . . . . . . . . . . . : 570490772 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1C-63-50-12-F0-76-1C-65-6D-C4 DNS Servers . . . . . . . . . . . : 172.16.128.40 Primary WINS Server . . . . . . . : 172.16.128.40 NetBIOS over Tcpip. . . . . . . . : Enabled However, Windows 10 keeps using the ISP provided dns servers and therefore all mapings etc fail. As most of my users are not "smart users" I do NOT want them to mess with the dns settings. So now what? Do we prohibit the use of Windows 10? That is not an option. ;-) Bonno Bloksma ------------------------------------------------------------------------------ _______________________________________________ Openvpn-users mailing list Openvpn-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-users
