4 ms·

resolvd was running by default on Ubuntu 24. I was struggling with it while trying to troubleshoot a VPN connection because resolvd automates resolve.conf into

resolvd was running by default on Ubuntu 24. I was struggling with it while trying to troubleshoot a VPN connection because resolvd automates resolve.conf into a generated file from several other files and will overwrite any other functionality trying to add resolvers to resolve.conf, like an internal VPN company resolver for example. Why is systemd even touching DNS? Seems a little outside of it's scope. This is kinda crazy to me personally when I found out resolvd was doing this. https://www.man7.org/linux/man-pages/man8/systemd-resolved.service.8.html#/ETC/RESOLV.CONF https://www.man7.org/linux/man-pages/man8/systemd-resolved.s...

tuna74 2y ago
"Why is systemd even touching DNS?" resolvd != systemd. It seems like you are mad that Ubuntu changed DNS resolver, but isn't that the actual job of a Linux distro?
- the_real_cher 2y ago
  the full name of the service is systemd-resolvd...
  - vetinari 2y ago
    yes, and full name of coreutils is GNU coreutils.
    - the_real_cher 2y ago
      systemd-resolvd is in the literal systemd code base. https://github.com/systemd/systemd/tree/main/src%2Fresolve https://github.com/systemd/systemd/tree/main/src%2Fresolve
      - vetinari 2y ago
        So are udev and nss modules. It's monorepo.
        the_real_cher 2y ago
        so if it's 1> in the systemd repo 2> if it's written and maintained by the same people who write systemd 3> if systemd is in the NAME I don't really know what more is needed to say it a is part of systemd
        vetinari 2y ago
        After a quick check, in 100% of distributions checked, it is a separate package. In many of them, not even installed by default (which is too bad).
        the_real_cher 2y ago
        okayyy
egorfine 2y ago
I believe systemd-resolved is easily the absolute worst piece of systemd infrastructure. And especially so in Ubuntu! In 24.04 you can get away by uninstalling it then creating a sane /etc/resolv.conf; previous Ubuntu distros required a bit more than that.
vetinari 2y ago
Ideally, with systemd-resolved, you would have only 127.0.0.53 in your resolv.conf. (Anything that reads it directly is broken anyway). Then you configure your DNS using NetworkManager, on respective connections. I.e. on your VPN, you configure the DNS on the other side of the connection, and (optionally) which zones it is supposed to resolve. (NetworkManager then configures systemd-resolved accordingly). The usage of this DNS then goes up and down together with your VPN connection. That's it.

tuna74 2y ago

"Why is systemd even touching DNS?" resolvd != systemd. It seems like you are mad that Ubuntu changed DNS resolver, but isn't that the actual job of a Linux distro?

the_real_cher 2y ago
the full name of the service is systemd-resolvd...
- vetinari 2y ago
  yes, and full name of coreutils is GNU coreutils.
  - the_real_cher 2y ago
    systemd-resolvd is in the literal systemd code base. https://github.com/systemd/systemd/tree/main/src%2Fresolve https://github.com/systemd/systemd/tree/main/src%2Fresolve
    - vetinari 2y ago
      So are udev and nss modules. It's monorepo.
      - the_real_cher 2y ago
        so if it's 1> in the systemd repo 2> if it's written and maintained by the same people who write systemd 3> if systemd is in the NAME I don't really know what more is needed to say it a is part of systemd
        vetinari 2y ago
        After a quick check, in 100% of distributions checked, it is a separate package. In many of them, not even installed by default (which is too bad).
        the_real_cher 2y ago
        okayyy

egorfine 2y ago

I believe systemd-resolved is easily the absolute worst piece of systemd infrastructure. And especially so in Ubuntu! In 24.04 you can get away by uninstalling it then creating a sane /etc/resolv.conf; previous Ubuntu distros required a bit more than that.

vetinari 2y ago

Ideally, with systemd-resolved, you would have only 127.0.0.53 in your resolv.conf. (Anything that reads it directly is broken anyway). Then you configure your DNS using NetworkManager, on respective connections. I.e. on your VPN, you configure the DNS on the other side of the connection, and (optionally) which zones it is supposed to resolve. (NetworkManager then configures systemd-resolved accordingly). The usage of this DNS then goes up and down together with your VPN connection. That's it.