Comment 6 for bug 1096326

I think I have the same problem (please advise if not) in Kubuntu 20.04.

When I connect to my company with the official Cisco AnyConnect client, my DNS is automatically switched to 192.168.240.250, which is the company one and allows me to resolve the company internal names, which are in the form "hostname.foobar".

When I use the openconnect Network Manager plugin this does not work "out-of-the-box".
I see that if I add "foobar" in the "search domains" in the IPv4 settings of this openconnect VPN connection using the Network Manager GUI, and reconnect, it seems to work and I can resolve both "hostname" and "hostname.foobar" names (the former is mapped to "hostname.foobar" too). However, randomly, when I disconnect and reconnect, it stops working again: I was not able to determine what makes it fail and what should I do to make it work reliably.

What I noticed is that if I use the official Cisco AnyConnect client, nslookup will resolve names through 192.168.240.250. If I use the openconnect Network Manager plugin it will resolve names with localhost.

I tried to manually add the DNS server name in the IPv4 settings of this openconnect VPN connection using the Network Manager GUI, but it seems to make no difference at all.

I didn't try the workaround in #5: it sounds like an invasive change, what could be the consequences?