Announcement

Collapse
No announcement yet.

Fedora 33 Planning To Enable Systemd-Resolved By Default

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #21
    Originally posted by Spam View Post

    I prefer Unbound and NSD, or any tool built to support dns properly. SystemD seems to want to build a full OS...
    It would be so easy to do if "properly" meant the same thing for everybody. As it stands, it seems systemd is only implementing DNS the way Internet bodies understand "properly".

    Comment


    • #22
      Originally posted by spstarr View Post
      I am assuming this will break my own private DNS server and my own domain...
      systemd-resolved supports using your own DNS server(s), and can be configured to not cache anything if you so wish. The problem may be that systemd-resolved supports so many options that one can easily get overwhelmed in all the choices you might want to make (and I seem to recall there were some combinations of options that were technically legal, but almost certainly were not what you really wanted).

      Comment


      • #23
        Will this break setting DNS servers through GNOME Settings?

        or can NetworkManager tell systemd-resolved of the DNS servers to use.

        Comment


        • #24
          Originally posted by bug77 View Post
          It would be so easy to do if "properly" meant the same thing for everybody. As it stands, it seems systemd is only implementing DNS the way Internet bodies understand "properly".
          that's the best kind of "properly", given that DNS was created by them.

          Comment


          • #25
            Originally posted by Britoid View Post
            Will this break setting DNS servers through GNOME Settings?

            or can NetworkManager tell systemd-resolved of the DNS servers to use.
            One of the configurations of systemd-resolved is to let other components determine/specify the DNS servers, where NetworkManager is obviously known to be one of them. The (automatic) detection of using other specifications of DNS servers can, of course, be configured.

            Comment


            • #26
              Originally posted by CommunityMember View Post

              One of the configurations of systemd-resolved is to let other components determine/specify the DNS servers, where NetworkManager is obviously known to be one of them. The (automatic) detection of using other specifications of DNS servers can, of course, be configured.
              Do you have the instructions of how to set this up on F32?

              So you could tell NetworkManager the DNS-over-tls severs (like 1.2.3.4#secure-dns.example) and that would get forwarded to resolved?

              Comment


              • #27
                Originally posted by Britoid View Post
                Will this break setting DNS servers through GNOME Settings?

                or can NetworkManager tell systemd-resolved of the DNS servers to use.
                Afaik it's a drop-in replacement as it's taking the DNS/domain list from /etc/resolv.conf, which is the standard way used by NetworkManager and others (also by systemd-networkd) to interact with current DNS daemons.
                https://wiki.archlinux.org/index.php...#Automatically

                Comment


                • #28
                  Originally posted by starshipeleven View Post
                  Afaik it's a drop-in replacement as it's taking the DNS/domain list from /etc/resolv.conf, which is the standard way used by NetworkManager and others (also by systemd-networkd) to interact with current DNS daemons.
                  https://wiki.archlinux.org/index.php...#Automatically
                  It looks like on this proposal, they're going to make /etc/resolv.conf link to the stub-resolver, so anything reading /etc/resolv.conf talks to resolved instead, which then has its own configuration.

                  But, CommunityMember is saying above its possible for NetworkManager to tell systemd-resolved what DNS servers to

                  Edit: So NetworkManager does seem to tell resolved what dns servers to use per-connection. Had to scroll do the bottom of resolvectl status. nm-connection-editor won't let you define dns-over-tls hosts after the IP though.
                  Last edited by Britoid; 15 April 2020, 12:12 PM.

                  Comment


                  • #29
                    Originally posted by Britoid View Post
                    It looks like on this proposal, they're going to make /etc/resolv.conf link to the stub-resolver, so anything reading /etc/resolv.conf talks to resolved instead, which then has its own configuration.
                    As said in both the Fedora proposal and Arch wiki, NetworkManager will detect this and go change this daemon config.

                    Something similar is done already by netconfig scripts in OpenSUSE, my /etc/resolv.conf is a dummy symlinked to another file handled or updated by netconfig scripts (integrated with NetworkManager too) called whenever the system feels like it.

                    Code:
                    cat /etc/resolv.conf
                    ### /etc/resolv.conf is a symlink to /var/run/netconfig/resolv.conf
                    ### autogenerated by netconfig!
                    #
                    # Before you change this file manually, consider to define the
                    # static DNS configuration using the following variables in the
                    # /etc/sysconfig/network/config file:
                    #     NETCONFIG_DNS_STATIC_SEARCHLIST
                    #     NETCONFIG_DNS_STATIC_SERVERS
                    #     NETCONFIG_DNS_FORWARDER
                    # or disable DNS configuration updates via netconfig by setting:
                    #     NETCONFIG_DNS_POLICY=''
                    #
                    # See also the netconfig(8) manual page and other documentation.
                    #
                    ### Call "netconfig update -f" to force adjusting of /etc/resolv.conf.
                    search lan
                    nameserver 192.168.1.240
                    nm-connection-editor won't let you define dns-over-tls hosts after the IP though.
                    This is a NetworkManager limitation that might be removed in the future, you can still add dns-over-tls hosts with a couple line of manual config files as explained in Arch wiki.
                    Last edited by starshipeleven; 15 April 2020, 12:38 PM.

                    Comment


                    • #30
                      https://github.com/systemd/systemd/i...temd-resolved+ gives me 152 open issues... Wish this number were lesser by the time of F33 release

                      Comment

                      Working...
                      X