News for hackers. Stuff that matters.
Re:How to take back control of /etc/resolv.conf on Linux (2018) by oblio on Wednesday March 20, 2019 @06:07AM (#19440556)
Debian, Ubuntu and the vast majority of their derivatives use systemd.

Fedora and Red Hat and the vast majority of their derivatives use systemd.

OpenSUSE and SUSE and the vast majority of their derivatives use systemd.

In most production environments bar custom distributions used by Google & co. (and those are a minority), systemd is used, presumably with the systemd resolver.

I'm not sure I'd call all users of commercial Linux distributions "laymen" :)

Re:How to take back control of /etc/resolv.conf on Linux (2018) by yrro on Wednesday March 27, 2019 @07:19AM (#19499745)
> Debian, Ubuntu and the vast majority of their derivatives use systemd.

Debian doesn't use nss-resolve(8) by default though. I'd be very surprised if RHEL or any other other distros suitable for a "production environment" were to take that step given systemd-resolved's current level of maturity.

(This is not a knock at systemd-resolved; I use it myself on most of my machines, but unless you want to spend a lot of time debugging weird resolver issues I would not recommend doing so until it has matured a bit more.