resolv.conf not updated after connecting to VPN using OpenConnect

I recently switched from the **Cisco AnyConnect Secure Mobility Client** to **OpenConnect** to solve a long-standing issue where my Docker containers could not access internal sites over my corporate VPN. This switch resolved that issue (as reported in several similar cases online), but it introduced a new problem: Now, every time I connect to the VPN using OpenConnect, **/etc/resolv.conf is not properly updated** with the internal DNS servers as the Cisco client used to do automatically. I’ve been working around this by manually updating resolv.conf after each connection, and even wrote a small script to speed that up — but this doesn't feel like a solid or sustainable solution. --- ### My setup: - OS: Ubuntu 24.04.02 - Packages:

network-manager-openconnect         1.2.10-3build2
  network-manager-openconnect-gnome   1.2.10-3build2
  openconnect                         9.12-1build5

- I use the **GNOME UI** for connection because my VPN requires **SSO login via a web view**. --- ### Questions: 1. How can I make OpenConnect automatically update resolv.conf when the VPN connects? 2. Is there a NetworkManager hook or OpenConnect config that I’m missing? 3. Are there known limitations when using OpenConnect via the GNOME UI regarding DNS updates? --- Any advice, workaround, or best practice would be greatly appreciated.