5 ms·
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 doma
by lmz 4y ago
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.
- tyingq 4y agoI 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.
- lmz 4y agoIt was always a contended file, before systemd e.g. https://wiki.debian.org/resolv.conf https://wiki.debian.org/resolv.conf names two software packages (choose one) to manage that file.
- tyingq 4y ago>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.
- dsr_ 4y agoOther direction: people used to feel secure that nothing was going to edit resolv.conf away from what they set up.