The Fedora guys have been working with all their enthusiasm and time available to meet the distribution launch schedule but, it seems that this year will be another year in which the release date of the distribution It will not be fulfilled, tomore of what information was also released what pFor the next version of the distribution which is Fedora 33 (which I already know is starting to work) sI will make a small change on the system that provides network name resolution to applications from “nss-resolve” by “systemd-resolved”.
For implementation in Fedora 33, "systemd-resolved" is planned to replace "nss-resolve" to resolve DNS and Glibc queries it will be changed to nss-resolve from the systemd project instead of the built-in NSS module nss-dns.
Table of Contents
systemd-resolved will replace nss-resolve in Fedora 33
This change is made due to the decision made internally in Fedora that instead of opting to disable "systemd-resolved" (as it has been doing for a long time) better be enabled.
The developers comment that systemd-resolve performs functions such as keep the configuration in the resolv.conf file based on DHCP data and a static DNS configuration for network interfaces, supports DNSSEC and LLMNR (Link Local Multicast Name Resolution).
Among the benefits of switching to systemd-resolved is the support for DNS over TLS, the ability to enable local caching of DNS queries and support for binding different processors to different network interfaces (depending on the network interface, a DNS server is selected to access, eg DNS queries for VPN interfaces will be sent over VPN). It is not planned to use DNSSEC in Fedora (systemd-resolve will be constructed with DNSSEC = no flag).
Systemd-resolve is already used by default in Ubuntu As of version 16.10, but the integration will be done differently in Fedora, since Fedora acts totally different from Ubuntu to begin with and Ubuntu continues to use traditional glibc nss-dns, that is, glibc continues to handle / etc / resolv. conf, while Fedora hopes to replace nss-dns with systemd's nss-resolve.
For those who do not want to use systemd-resolve, it will be possible to disable it and to do this you must disable the systemd-resolve.service service and restart NetworkManager, which will create the traditional /etc/resolv.conf.
Final version of Fedora 32 delayed for a week
Finally, another of the changes that the developers of the Fedora project announced was the postponement of the release of the final version of Fedora 32 for a week due to non-compliance with quality criteria.
The launch of Fedora 32 is scheduled for April 28, instead of April 21, as originally planned.
In the final test builds that forced the developers to postpone the final release at least 3 problems are commenteds that are classified as version lock that remain uncorrected.
Version locking issues include: problems with LVM partition recognition in crash recovery mode, freezing when trying to boot on systems with NVIDIA Turing GPUs in "Safe Boot" mode, and missing final version of the f32-background package in a stable repository.
The developers hope that these bugs will be solved within the time they stipulated to take the end date for granted (previously mentioned), but in case it is not so, the date will be delayed more days:
Due to open blocker bugs, Fedora 32 Final was declared "forbidden". We will meet again at 17:00 UTC on Thursday, April 23 to reassess the situation and announce the final release of Fedora 32.
If we determine at that time that Fedora 32 is ready, it will be released on "expected release date # 1" of April 28th.
Finally if you want to know more about the communications issued by the guys at Fedora, you can check out the following links we provide.