<![CDATA[Windows IPSec client not getting/using DNS]]>We've had IPSec working well for a long time, with clients on multiple OSes.

But there's one Windows user that doesn't seem to be getting/using our internal DNS.

For example, when he connects to our VPN and does ping www.mycorp.com he gets the public IP instead of our internal 10.1.1.x IP.

Strangely, his ipconfig output shows:

PPP adapter MyVPN:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : MyVPN
   Physical Address. . . . . . . . . :
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 10.1.2.13(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.255
   Default Gateway . . . . . . . . . : 0.0.0.0
   DNS Servers . . . . . . . . . . . : 10.1.1.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

The "DNS Servers" value (10.1.1.1) is the expected internal pfsense LAN IP.

So I'm stumped as to what the problem is...

]]>https://forum.netgate.com/topic/158368/windows-ipsec-client-not-getting-using-dnsRSS for NodeTue, 15 Sep 2026 19:03:06 GMTSun, 15 Nov 2020 01:43:39 GMT60<![CDATA[Reply to Windows IPSec client not getting/using DNS on Fri, 20 Nov 2020 18:25:27 GMT]]>So in case it helps anyone landing here, I found a solution in these:

http://superuser.com/questions/966832/windows-10-dns-resolution-via-vpn-connection-not-working

https://answers.microsoft.com/en-us/windows/forum/windows_10-networking-winpc/win-10-dns-resolution-of-remote-network-via-vpn/513bdeea-0d18-462e-9ec3-a41129eec736?page=4

]]>https://forum.netgate.com/post/946667https://forum.netgate.com/post/946667Fri, 20 Nov 2020 18:25:27 GMT