openconnect соединен, но не использует правильный DNS

sudo openconnect --protocol=nc [corporate vpn url]
GET [corporate vpn url]
Connected to [corporate vpn ip]:443
SSL negotiation with [corporate vpn url]
Connected to HTTPS on [corporate vpn url]
Got HTTP response: HTTP/1.1 302 Found
GET [corporate vpn url]/auth/url_13/welcome.cgi
SSL negotiation with [corporate vpn url]
Connected to HTTPS on [corporate vpn url]
frmLogin
username: [a username]
password: [a password]
POST [corporate vpn url]/auth/url_13/login.cgi
Got HTTP response: HTTP/1.1 302 Moved
GET [corporate vpn url]/home/starter0.cgi?check=yes
Connected as [new ip address], using SSL, with ESP in progress
ESP session established with server

Это, кажется, прекрасно в том смысле, что torguard показывает другой IP-адрес и страну прежде и после того, как openconnect соединен.

Однако кажется, что я не могу получить доступ к корпоративным веб-сайтам, когда я пробую, говорят, что Chrome, я заканчиваю с:

Server IP address could not be found.
DNS_PROBE_FINISHED_NXDOMAIN

Как то, если DNS не был выбран или что-то как.

Это странно, хотя причина, когда я делаю это от живого CD, который является без любого предшествующего соединения с любой сетью, оно работает просто великолепно...

Я задаюсь вопросом, как DNS выбирается.

[Править]

Я прямо сейчас использую Linux Mint, живой для наблюдения то, что является используемым DNS или является там чем-либо специальная установка:

Для Беспроводного соединения:

mint@mint:~$ nmcli device show wlp1s0
GENERAL.DEVICE:                         wlp1s0
GENERAL.TYPE:                           wifi
GENERAL.HWADDR:                         E0:94:67:32:46:AF
GENERAL.MTU:                            1500
GENERAL.STATE:                          100 (connected)
GENERAL.CONNECTION:                     [our wireless hotspot at home]
GENERAL.CON-PATH:                       /org/freedesktop/NetworkManager/ActiveConnection/1
IP4.ADDRESS[1]:                         192.168.1.104/24
IP4.GATEWAY:                            192.168.1.1
IP4.ROUTE[1]:                           dst = 0.0.0.0/0, nh = 192.168.1.1, mt = 600
IP4.ROUTE[2]:                           dst = [what an ip address?!], nh = 0.0.0.0, mt = 600
IP4.ROUTE[3]:                           dst = [yet another one!], nh = 0.0.0.0, mt = 1000
IP4.ROUTE[4]:                           dst = [an address, geez], nh = 192.168.1.1, mt = 0
IP4.DNS[1]:                             192.168.1.1
IP4.DOMAIN[1]:                          home
IP6.ADDRESS[1]:                         [ipv 6 craziness]
IP6.ADDRESS[2]:                         [woooa]
IP6.ADDRESS[3]:                         [asdasdad]
IP6.GATEWAY:                            [&*^$]
IP6.ROUTE[1]:                           dst = [incredible]::/64, nh = ::, mt = 600
IP6.ROUTE[2]:                           dst = ::/0, nh = [beyond understanding], mt = 600
IP6.ROUTE[3]:                           dst = ff00::/8, nh = ::, mt = 256, table=255
IP6.ROUTE[4]:                           dst = fe80::/64, nh = ::, mt = 256
IP6.ROUTE[5]:                           dst = fe80::/64, nh = ::, mt = 600
IP6.DNS[1]:                             [fantastic!]

И VPN созданный интерфейс:

mint@mint:~$ nmcli device show tun0
GENERAL.DEVICE:                         tun0
GENERAL.TYPE:                           tun
GENERAL.HWADDR:                         (unknown)
GENERAL.MTU:                            1400
GENERAL.STATE:                          100 (connected)
GENERAL.CONNECTION:                     tun0
GENERAL.CON-PATH:                       /org/freedesktop/NetworkManager/ActiveConnection/2
IP4.ADDRESS[1]:                         [magic ip]
IP4.GATEWAY:                            0.0.0.0 
IP4.ROUTE[1]:                           dst = [magic ip], nh = 0.0.0.0, mt = 0
IP4.ROUTE[2]:                           dst = 0.0.0.0/0, nh = 0.0.0.0, mt = 0
IP6.ADDRESS[1]:                         [magic ip again]
IP6.GATEWAY:                            --
IP6.ROUTE[1]:                           dst = ff00::/8, nh = ::, mt = 256, table=255
IP6.ROUTE[2]:                           dst = fe80::/64, nh = ::, mt = 256

Интересно достаточно кажется что etc/resolv.conf был изменен, когда я соединился с vpn:

#@VPNC_GENERATED@ -- this file is generated by vpnc
# and will be overwritten by vpnc
# as long as the above mark is intact
# This file is managed by man:systemd-resolved(8). Do not edit.
#
# This is a dynamic resolv.conf file for connecting local clients to the
# internal DNS stub resolver of systemd-resolved. This file lists all
# configured search domains.
#
# Run "systemd-resolve --status" to see details about the uplink DNS servers
# currently in use.
#
# Third party programs must not access this file directly, but only through the
# symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a different way,
# replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.

options edns0
nameserver [some address 1]
nameserver [some address 2]
search home [loads of corporate related names]

... и когда я разъединяюсь от VPN:

# This file is managed by man:systemd-resolved(8). Do not edit.
#
# This is a dynamic resolv.conf file for connecting local clients to the
# internal DNS stub resolver of systemd-resolved. This file lists all
# configured search domains.
#
# Run "systemd-resolve --status" to see details about the uplink DNS servers
# currently in use.
#
# Third party programs must not access this file directly, but only through the
# symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a different way,
# replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.

nameserver 127.0.0.53
options edns0
search home