4 ms·

Exactly - this is a perfect example of what has always bothered me about systemd.

rerdavies 2y ago
Binding a DNS server to 127.0.01:53 is a perfect example of what has always bothered you about systemd? Seriously not getting it. Providing DNS services on 127.0.0.1:53 has nothing to do with systemd. It's a convention used by NetworkManager, and associated network services. The very good reason being that network interfaces that are being brought up and down can choose to forward their DNS requests to 127.0.0.1, and allow a completely separate unit (resolved?) to deal with the details of where DNS requests get forwarded from there. (Or not, if they so choose). Was there some OTHER burning compelling use-case that makes you want to use 127.0.0.1:53 for some other purpose?
- the_real_cher 2y ago
  From the man pages: "Additionally, systemd-resolved provides a local DNS stub listener on the IP addresses 127.0.0.53 and 127.0.0.54 on the local loopback interface" https://www.man7.org/linux/man-pages/man8/systemd-resolved.service.8.html https://www.man7.org/linux/man-pages/man8/systemd-resolved.s... > Was there some OTHER burning compelling use-case that makes you want to use 127.0.0.1:53 for some other purpose? The problem is... by default... resolvd routes ALL DNS REQUESTS to this stub by over writing resolv.conf with ONLY that socket and forcing you to configure resolvers elsewhere. And you have to manually reconfigure this if you want to change it and it forces you to get in the weeds way to much when all you want to do is add a DNS resolver. https://www.man7.org/linux/man-pages/man8/systemd-resolved.service.8.html#/ETC/RESOLV.CONF https://www.man7.org/linux/man-pages/man8/systemd-resolved.s... The confusing thing is why the heck is SYSTEMD an init system writing DNS resolvers? Seems out of it's scope in my opinion. I was surprised resolvd existed when I was trying to troubleshoot a DNS error caused by it.
  - johnny22 2y ago
    resolved is neither started by default on systemd nor required in any way. Your distro chose that.
    - the_real_cher 2y ago
      As most mainstream distros will just to fall in line with the standard. unless you want to use Arch at some point it will be the default for most Linux.
      - johnny22 2y ago
        there is no standard. it's just a tool that ships with systemd that some folks use and some don't.
        the_real_cher 2y ago
        yeah just like systemd right?
      - rerdavies 2y ago
        Isn't mainstream distros all doing the same thing a Very Good Thing Indeed?

Binding a DNS server to 127.0.01:53 is a perfect example of what has always bothered you about systemd? Seriously not getting it. Providing DNS services on 127.0.0.1:53 has nothing to do with systemd. It's a convention used by NetworkManager, and associated network services. The very good reason being that network interfaces that are being brought up and down can choose to forward their DNS requests to 127.0.0.1, and allow a completely separate unit (resolved?) to deal with the details of where DNS requests get forwarded from there. (Or not, if they so choose). Was there some OTHER burning compelling use-case that makes you want to use 127.0.0.1:53 for some other purpose?

the_real_cher 2y ago
From the man pages: "Additionally, systemd-resolved provides a local DNS stub listener on the IP addresses 127.0.0.53 and 127.0.0.54 on the local loopback interface" https://www.man7.org/linux/man-pages/man8/systemd-resolved.service.8.html https://www.man7.org/linux/man-pages/man8/systemd-resolved.s... > Was there some OTHER burning compelling use-case that makes you want to use 127.0.0.1:53 for some other purpose? The problem is... by default... resolvd routes ALL DNS REQUESTS to this stub by over writing resolv.conf with ONLY that socket and forcing you to configure resolvers elsewhere. And you have to manually reconfigure this if you want to change it and it forces you to get in the weeds way to much when all you want to do is add a DNS resolver. https://www.man7.org/linux/man-pages/man8/systemd-resolved.service.8.html#/ETC/RESOLV.CONF https://www.man7.org/linux/man-pages/man8/systemd-resolved.s... The confusing thing is why the heck is SYSTEMD an init system writing DNS resolvers? Seems out of it's scope in my opinion. I was surprised resolvd existed when I was trying to troubleshoot a DNS error caused by it.
- johnny22 2y ago
  resolved is neither started by default on systemd nor required in any way. Your distro chose that.
  - the_real_cher 2y ago
    As most mainstream distros will just to fall in line with the standard. unless you want to use Arch at some point it will be the default for most Linux.
    - johnny22 2y ago
      there is no standard. it's just a tool that ships with systemd that some folks use and some don't.
      - the_real_cher 2y ago
        yeah just like systemd right?
    - rerdavies 2y ago
      Isn't mainstream distros all doing the same thing a Very Good Thing Indeed?