VPN works, but wrong DNS server is queried about openconnect-gui

[nmav]

I think this may relate to the priority windows sets to interfaces. What is the output of "netstat -rn" in your system?

[nmav]

Also does changing the priority of the tap adapter as in http://stackoverflow.com/questions/7785874/setting-network-adapter-metric-priority-in-windows-7 help?

[cowens]

Changing the priority doesn't seem to stick. If I set the priority and then run nslookup domain.on.vpn, it still shows the LAN's DNS server being queried (and, of course, the wrong IP address). If I go back into the Advanced Setting menu option, it shows the networks in the order it was to begin with (rather than the order I gave them).

The output of netstat -rn is

===========================================================================
Interface List
 31...00 1a 7d da 71 13 ......Bluetooth Personal Area Network Device
 16...0c 84 dc 63 39 8f ......Microsoft Hosted Network Virtual Adapter
  6...f0 1f af 31 3a 8e ......Broadcom NetXtreme 57xx Gigabit Controller
 25...00 ff 10 c9 cd 51 ......TAP-Windows Adapter V9
  2...0c 84 dc 63 39 8f ......Dell Wireless 1504 802.11b/g/n (2.4GHz)
  1...........................Software Loopback Interface 1
  5...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
  7...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
  3...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0      192.168.2.1     192.168.2.22     10
         10.0.0.0        255.0.0.0      10.254.12.1     10.254.14.89     21
      10.254.12.0    255.255.252.0         On-link      10.254.14.89    276
     10.254.14.89  255.255.255.255         On-link      10.254.14.89    276
    10.254.15.255  255.255.255.255         On-link      10.254.14.89    276
    67.223.177.10  255.255.255.255      192.168.2.1     192.168.2.22     11
        127.0.0.0        255.0.0.0         On-link         127.0.0.1    306
        127.0.0.1  255.255.255.255         On-link         127.0.0.1    306
  127.255.255.255  255.255.255.255         On-link         127.0.0.1    306
       172.15.0.0      255.255.0.0      10.254.12.1     10.254.14.89     21
       172.16.0.0      255.240.0.0      10.254.12.1     10.254.14.89     21
      192.168.2.0    255.255.255.0         On-link      192.168.2.22    266
     192.168.2.22  255.255.255.255         On-link      192.168.2.22    266
    192.168.2.255  255.255.255.255         On-link      192.168.2.22    266
      192.168.6.0    255.255.255.0      10.254.12.1     10.254.14.89     21
      192.168.7.0    255.255.255.0      10.254.12.1     10.254.14.89     21
     192.168.13.0    255.255.255.0      10.254.12.1     10.254.14.89     21
     192.168.15.0    255.255.255.0      10.254.12.1     10.254.14.89     21
     192.168.16.0    255.255.255.0      10.254.12.1     10.254.14.89     21
    192.168.108.0    255.255.255.0      10.254.12.1     10.254.14.89     21
    192.168.150.0    255.255.255.0      10.254.12.1     10.254.14.89     21
    192.168.226.0    255.255.255.0      10.254.12.1     10.254.14.89     21
    192.168.230.0    255.255.255.0      10.254.12.1     10.254.14.89     21
    192.168.254.0    255.255.255.0      10.254.12.1     10.254.14.89     21
        224.0.0.0        240.0.0.0         On-link         127.0.0.1    306
        224.0.0.0        240.0.0.0         On-link      192.168.2.22    266
        224.0.0.0        240.0.0.0         On-link      10.254.14.89    276
  255.255.255.255  255.255.255.255         On-link         127.0.0.1    306
  255.255.255.255  255.255.255.255         On-link      192.168.2.22    266
  255.255.255.255  255.255.255.255         On-link      10.254.14.89    276
===========================================================================
Persistent Routes:
  None

IPv6 Route Table
===========================================================================
Active Routes:
 If Metric Network Destination      Gateway
  1    306 ::1/128                  On-link
  6    266 fe80::/64                On-link
 25    276 fe80::/64                On-link
 25    276 fe80::64d8:800:fb9c:f0b4/128
                                    On-link
  6    266 fe80::a03a:9a87:b8d6:7f16/128
                                    On-link
  1    306 ff00::/8                 On-link
  6    266 ff00::/8                 On-link
 25    276 ff00::/8                 On-link
===========================================================================
Persistent Routes:
  None

[cowens]

Right now my workaround is to go into the LAN's IPv4 settings and manually set the DNS servers to be the VPN DNS servers and then switching them back when I leave the VPN. It is a pain, but it works.

[nmav]

According to windows documentation the DNS server of the "preferred adapter" is queried first. If that's correct we'll need a way to set the VPN adapter as the "preferred".

https://technet.microsoft.com/en-us/library/dd197552%28WS.10%29.aspx

[marksibert]

What version of Windows are you running? I have the same behavior on Windows 10. When I was running the Shrew VPN client, it worked on Windows 7/8, but showed the same DNS behavior when I upgraded to Windows 10. Cisco Anyconnect doesn't have the DNS issue, though.

[nmav]

A solution may be to replace the DNS servers on default adapter as in:
http://superuser.com/questions/463096/change-dns-with-script

We would need to store the old value though and reset them on disconnect. If you have some modification to vpnc-script.js for that open a PR and I'll check it.

[aairey]

Any update on incorparting a DNS setting?
Would be a nice option to specify 2 DNS servers per VPN connection.