systemd-resolved bypassed by default on Debian and RedHat families

[MarinBernard]

Hi,

Applying the systemd.resolved formula on Debian / RedHat nodes results in the /etc/resolv.conf symlink pointing to /run/systemd/resolve/resolv.conf, which forwards DNS queries to external DNS servers instead of the local systemd-resolved service.

Two observations:

1. While symlinking /etc/resolv.conf to /run/systemd/resolve/resolv.conf is perfectly fine, it would result in systemd-resolved being bypassed by most DNS consumers. Since the systemd-resolved state explicitly configures and enables systemd-resolved, I suppose most people would also expect the state to also promote systemd-resolved as the main DNS resolver on the configured system.

2. In osfamilymap.yaml, different defaults apply on Arch systems. On such systems, the /etc/resolv.conf symlink will be configured to target /run/systemd/resolve/stub-resolv.conf, which will result in systemd-resolved actually becoming the main DNS resolver.

Shouldn't we:

1. Use the same defaults (whatever they might be) for all OS families ?

2. Change the target of /etc/resolv.conf to /run/systemd/resolve/stub-resolv.conf to enable the use of systemd-resolved by default ?