casper

I have the same issue. I have several machines which does not have this bug, except one machine which is encountering this bug. I rebooted with 'systemd.log-level=debug' to generate the...

> @fantomfp Are the ones that don't have this bug also running BIND (named)? > > Your log contains: > > ``` > Nov 11 16:56:35 sd-128718 named[906]: compiled by...

I can see a small difference between 2 machines: ``` casper@vulcain:~ % ssh nsb resolvectl Global Protocols: LLMNR=resolve -mDNS -DNSOverTLS DNSSEC=no/unsupported resolv.conf mode: foreign Current DNS Server: 127.0.0.1 DNS Servers:...

``` casper@vulcain:~ % ssh nsb ls -l /etc/resolv.conf -rw-r--r--. 1 root root 66 Nov 10 07:51 /etc/resolv.conf ``` and ``` casper@vulcain:~ % ssh nsd ls -l /etc/resolv.conf lrwxrwxrwx. 1 root...

FYI, I will run 'dnf update' on all machines next sunday. systemd version (systemd-250.8-1.fc36.x86_64) will become false. Also, I didn't had the bug before, so I'm curious to see if...

Thank you for the doc. It helped me to fix the issue on the impacted server. Thank you very much. This is the feedback: That server was installed with Fedora...

I made a backup of the logs before DNF update, here they are: Timeline: - 13:34:01 reboot - 13:38:03 ssh login attempt Connection closed by port 22 - 13:40:23 ssh...

I searched on my other machines the same setup exactly than the server having issues. Given the infos in this ticket. (Maybe to reproduce the issue, or to try to...

> I think we're getting off track here. If you don't want /etc/resolv.conf to point to ../run/systemd/resolve/stub-resolv.conf then you need to manually configure things how you like, or else just...

New feedback: As mentioned in https://github.com/systemd/systemd/issues/23406#issuecomment-1311928702 I never had this bug before. The systemd-resolved error log was confusing me. Thanks to @poettering for downgrading the error message to debug level....