this post was submitted on 20 Oct 2023
145 points (89.6% liked)

Linux

48343 readers
391 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

Related Communities

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

founded 5 years ago
MODERATORS
 

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
[–] [email protected] 13 points 1 year ago (4 children)

That doesn't help outside of home. When we are in an untrusted network then the DNS mess makes us vulnerable for spoofing attacks.

[–] [email protected] 10 points 1 year ago (1 children)

Wireguard to home or a vps running a pihole. Block all dns other than over wireguard.

[–] [email protected] 2 points 1 year ago (1 children)

Doesn’t this solution mess with captive portals?

[–] [email protected] 5 points 1 year ago

Ive never had an issue. You could always just disable it to load the captive portal then turn it back on after you're connected.

[–] [email protected] 6 points 1 year ago
  1. Wireguard
  2. I run my own DoT/DoH server and able to connect it from everywhere. This makes option 1 mostly obsolete.

PS. And yes, I fucking love to solve captchas. No, I am not a Robot.

[–] [email protected] 0 points 1 year ago

Could also look at tailscale, set it up on you home PCs and mobile devices, set the magic DNS to a home server or vps running pihole. If you don't like the aspect of tailscale being controlled by a third party you could self host that part using headscale on docker as well