Fedora 37 systemd-resolved-251.8-586.fc37.x86_64 bind-chroot-9.18.8-1.fc37.x86_64 As of FC37 (no issue in FC36), I have a caching server configured. Whenever a network configuration event hits, such as a dhclient request or an ifup/ifdown, systemd-resolved goofs up my caching name server. # cat /etc/resolv.conf nameserver 127.0.0.53 options edns0 trust-ad search . And look what happens here: $ host gbis.com Host gbis.com not found: 2(SERVFAIL) Then if I throw a: $ host gbis.com 127.0.0.1 Using domain server: Name: 127.0.0.1 Address: 127.0.0.1#53 Aliases: gbis.com has address 54.151.57.48 gbis.com mail is handled by 0 gbis.com. And now it starts working!!!! $ host gbis.com gbis.com has address 54.151.57.48 gbis.com mail is handled by 0 gbis.com. To clear the issue, I have to throw the following: # systemctl stop named-chroot.service # systemctl start named-chroot.service # host gbis.com 127.0.0.1 It greatly helped but did not cure by switching my Ethernet connection to my router from dhcp client to fixed IP address.
here is my workaround: # dnf remove resolvconf # dnf install resolvconf --releasever=36 # vi /etc/dnf/dnf.conf excludepkgs=resolvconf reboot But I prefer not to have resolvconf working at all
This might help: This might be a hint: Global and eno2 are different when I set /etc/systemd/resolved.conf DNS=192.168.255.10:53 # systemctl restart systemd-resolved.service # resolvectl Global Protocols: LLMNR=resolve -mDNS -DNSOverTLS DNSSEC=no/unsupported resolv.conf mode: stub Current DNS Server: 192.168.255.10 DNS Servers: 192.168.255.10 Link 2 (eno2) Current Scopes: DNS LLMNR/IPv4 Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Current DNS Server: 127.0.0.1 DNS Servers: 127.0.0.1 Link 3 (eno1) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Link 4 (br0) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Link 5 (virbr0) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
I've seen similar behavior beginning in Fedora 35. The difference between working and not-working in my case was the kernel version: kernel version 5.19.16 always works, version 6.0.x doesn't.
*** Bug 2157789 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora Linux 37 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05. 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 '37'. 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. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 37 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 37 entered end-of-life (EOL) status on None. Fedora Linux 37 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 Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.