lxd is not part of systemd.

Why is lxd touching that file?

How is that a systemd issue?

systemd-resolved

Never had this issue. Sounds like they need to recreate the symlink.

It apparently needs specific tweaking for lxd: https://linuxcontainers.org/lxd/docs/master/howto/network_br...

Maybe I'm wrong, but that just seems to show that if you want to resolve lxd domains (hostnames?), you need to inform systemd-resolved to ask lxd for those domains, which is... sensible?

> you should notify resolved of the domains that LXD can resolve

You'd have the same issues if you replaced systemd-resolved with e.g. dnsmasq. Split DNS always needs resolver configuration.

I think it's just someone unhappy that they used to be able to edit resolve.conf before systemd-resolved took it over. I recall being annoyed about it as well, but that was some time ago.

It was always a contended file, before systemd e.g. https://wiki.debian.org/resolv.conf names two software packages (choose one) to manage that file.

>It was always a contended file

For people using dhcp, yes. The surprise of systemd-resolved was it taking over the file on a typical server that didn't use dhcp.

Other direction: people used to feel secure that nothing was going to edit resolv.conf away from what they set up.