I recently tried to enable system-wide DNS over https on Fedora. To do so I had to to some research and found out how comfusing it is for the average user (and even experienced users) to change the settings. In fact there are multiple backends messing with system DNS at the same time.
Most major Linux distributions use systemd-resolved for DNS but there is no utility for changing its configuration.
The average user would still try to change DNS settings by editing /etc/relov.conf (which is overwritten and will not survive reboots) or changing settings in Network Manager.
Based on documentation of systemd-resolved, the standard way of adding custom DNS servers is putting so-called ‘drop-in’ files in /etc/systemd/resolved.conf.d directory, especially when you want to use DNS-over-TLS or DNS-over-https.
Modern browsers use their buit-in DNS settings which adds to the confusion.
I think this is one area that Linux needs more work and more standardization.
How do you think it should be fixed?
Nobody is forcing me to buy gas for my car at such high prices, I can just not use my car, right?
Sorry for the dumb joke, but your answer sounds like the kind of answers Poettering gives when someone opens a ticket about a systemd bug.
I’m using Gentoo at home, which is great and still uses OpenRC.
But all my Debian servers run with systemd, there’s not much I can do about it.
Sorry, your comment sounds like everyone else who bogs themselves down in theory when practical solutions are right in front of them.
If you want to make things harder on yourself for no discernible payoff, that’s your prerogative.
It makes sense you’d subscribe to the community hate-boner for one of the few people that actually created useful software for the Linux ecosystem.
Something tells me you just go along with what others recommend, and unfortunately those are usually losers on the internet bringing other people down with them.
Nobody is forcing you to use Debian.
I don’t think it’s worth continuing this conversation.
I totally agree.