[Bug 2049392] Re: Symlink for resolv.conf not working with F5 vpn

[Nick Rosbrook]

This sounds like a bug with your VPN. How is it trying to change the DNS
servers? If they are trying to edit /etc/resolv.conf directly, that is
not compatible with systemd-resolved. Instead, they should use the DBus
API for systemd-resolved, or use `resolvectl`, etc.

** Changed in: systemd (Ubuntu)
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2049392

Title:
   Symlink for resolv.conf not working with F5 vpn

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I create this bug issue following an advice from Nick Rosbrook in this
  bug : https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2043234

  
  May be it's a F5 VPN. I haven't found such a bug anywhere. 

  I have an issue when connection to a F5 VPN when  /etc/resolv.conf is
  the symbolic link of ../run/systemd/resolve/stub-resolv.conf

  ➜ ~ sudo ls -la /etc/resolv.conf
  lrwxrwxrwx 1 root root 39 juin 23 12:37 /etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf

  When F5 is launched, /etc/resolv.conf is not changed. I have to
  manually set resolv.conf to change the nameserver(s).


  
  When I change the symbolic link /etc/resolv.conf to /run/systemd/resolve/resolv.conf

  sudo ln -sf /run/systemd/resolve/resolv.conf /etc/resolv.conf

  When F5 is launched, /etc/resolv.conf is  updated whith vpn
  nameserver(s).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2049392/+subscriptions