I just ran into this issue myself on 20.04. Specifically I was adding my own internal nameserver to a vm.
@Ubfan, why is stub-resolv.conf the correct file? The file that /etc/systemd/resolved.conf updates is /run/systemd/resolve/resolv.conf. As far as I can tell, the proper way to update /etc/resolv.conf is via /etc/systemd/resolved.conf. So if I want my changes to apply, then the /etc/resolv.conf link should point to the file systemd actually changes. Or is there a different method of updating what nameservers your computer uses? If there is, why is systemd involved with resolv.conf at all? Anyway, I believe this is a bug. Fortunately not one that effects people who don't know how to find the workarounds, but still a bug. I do hope it eventually gets fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1774632 Title: The symbolic link /etc/resolv.conf points to the wrong file by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1774632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
