someone12345

systemd-networkd is not enabled by default (even when its binaries might be installed).

> stuff such as the vulnerabilities in the DNS resolver because they reimplemented things from scratch without the necessary domain knowledge on how to do that securely that has been collected and implemented by the dozens of existing implementations over the decades

By domain knowledge how to do this securely in implementations tested oer time, do you mean something like https://access.redhat.com/articles/2161461?

It doesn't look like systemd's resolver fares worse in comparison... In addition it can be sandboxed (and is), an advantage over having a resolver part of libc.

> They lament

>> servers that don't boot, that don't reboot or systemd-resolved that constantly interferes with our core network configuration

Which is interesting given Debian doesn't use systemd-resolved (unless manually configured). So they made up problems that don't exist by default?