Created attachment 1796160 [details] journalctl -b --no-hostname -u NetworkManager -u systemd-resolved Description of problem: In a Fedora 34 Workstation machine, DNS resolution doesn't work until I restart the systemd-resolved service. This has started happening since the last week, so it has to be caused by a recent update. Version-Release number of selected component (if applicable): systemd-248.3-1.fc34.x86_64 NetworkManager-1.30.4-1.fc34.x86_64 How reproducible: Always after boot. Steps to Reproduce: 1. In this specific system, I have this additional configuration: # cat /etc/systemd/resolved.conf.d/local.conf [Resolve] FallbackDNS=1.1.1.1 1.0.0.1 2606:4700:4700::1111 2606:4700:4700::1001 DNSSEC=yes 2. Reboot Actual results: All DNS queries fail. # resolvectl status Global Protocols: LLMNR=resolve -mDNS -DNSOverTLS DNSSEC=yes/supported resolv.conf mode: stub Fallback DNS Servers: 1.1.1.1 1.0.0.1 2606:4700:4700::1111 2606:4700:4700::1001 Link 2 (enp4s0) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=yes/supported Link 3 (wlp5s0) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=yes/supported Link 4 (br-lab) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=yes/supported Link 5 (enp4s0.5) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=yes/supported Link 6 (br-lan) Current Scopes: none Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=yes/supported Current DNS Server: 192.168.10.1 DNS Servers: 192.168.10.1 DNS Domain: lan Link 7 (br-dmz) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=yes/supported Link 8 (enp4s0.7) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=yes/supported Failed to get link data for 9: Unknown object '/org/freedesktop/resolve1/link/_39'. Failed to get link data for 10: Unknown object '/org/freedesktop/resolve1/link/_310'. Failed to get link data for 11: Unknown object '/org/freedesktop/resolve1/link/_311'. Failed to get link data for 12: Unknown object '/org/freedesktop/resolve1/link/_312'. Failed to get link data for 13: Unknown object '/org/freedesktop/resolve1/link/_313'. Expected results: No errors. Additional info: Restarting systemd-resolved fixes the issue.
See also this thread in ask Fedora: https://ask.fedoraproject.org/t/dns-problem-in-fedora-server-due-to-resolvectl/15196?u=jorti
The issue appears to have been resolved after upgrading to kernel-5.12.13-300.fc34.x86_64 No idea what was the cause, though.
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '34'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07. Fedora Linux 34 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. Thank you for reporting this bug and we are sorry it could not be fixed.