Planned for implementation in Fedora 33. , translating the distribution to use systemd-resolved by default for resolving DNS queries. Glibc will switch to nss-resolve from the systemd project instead of the built-in NSS module nss-dns.
Systemd-resolved performs functions such as maintaining settings in the resolv.conf file based on DHCP data and static DNS configuration for network interfaces, supports DNSSEC and LLMNR (Link Local Multicast Name Resolution). The advantages of switching to systemd-resolved include support for DNS over TLS, the ability to enable local caching of DNS queries, and the option to bind different handlers to different network interfaces (depending on the network interface, a DNS server is selected for requests; for example, for VPN interfaces, DNS queries will be sent through the VPN). DNSSEC is not planned to be implemented in Fedora (systemd-resolved will be built with the DNSSEC=no flag).
Systemd-resolved is already used by default in Ubuntu since release 16.10, but in Fedora, the integration will be conducted differently — Ubuntu continues to utilize the traditional nss-dns from glibc, meaning glibc continues to manage /etc/resolv.conf, while Fedora plans to replace nss-dns with nss-resolve from systemd. For those who do not wish to use systemd-resolved, there will be an option to disable it (the service systemd-resolved.service needs to be deactivated and NetworkManager restarted, which will create the traditional /etc/resolv.conf).
Source: opennet.ru
