Linux

47952 readers

1406 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

142

Linux DNS settings is a total mess (lemdro.id)

submitted 1 year ago by mfat@lemdro.id to c/linux@lemmy.ml

63 comments fedilink hide all child comments

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?

you are viewing a single comment's thread
view the rest of the comments

[–] Molecular0079@lemmy.world 42 points 1 year ago (2 children)

changing settings in Network Manager.

What's wrong with this method? I feel like this is the main one and it works well for me. Even if you were using systemd-resolved, I believe it still works.

[–] jollyrogue@lemmy.ml 17 points 1 year ago

This is the answer for desktop Linux. Have NM create the drop in for systemd-resolved when the settings are changed. This is NM’s job.

[–] mfat@lemdro.id 12 points 1 year ago (1 children)

1.It doesn't support DoH 2.It's set per connection, not system-wide. If you connect to another wifi network you have to set dns again.

[–] timbuck2themoon@sh.itjust.works 2 points 1 year ago (2 children)

Do any modern OS's set DNS system wide?

I don't disagree there should be an option because I see maybe why they wouldn't do that.

[–] michaelmrose@lemmy.world 5 points 1 year ago (1 children)

All of them?

[–] timbuck2themoon@sh.itjust.works 3 points 1 year ago

Oh never mind. I'm thinking per adapter, not per connection. You're right.

[–] lo_fi@lemmy.world 1 points 1 year ago

Yeah, it's pretty easy on macos using configuration profiles