Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#68981 - [systemd] Since 247.1-4 the resolution with systemd-resolved is broken for me

Attached to Project: Arch Linux
Opened by Martin (MartinX3) - Tuesday, 15 December 2020, 10:55 GMT
Last edited by Toolybird (Toolybird) - Wednesday, 27 September 2023, 08:11 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Christian Hesse (eworm)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

Description:
With 247.1-3 everything was fine.
But since 247.1-4 I can't use web addresses anymore. Their resolution fail.
I disabled now the systemd-resolved service to get my internet back.
(In /etc/resolv.conf I inserted my router as the nameserver and search)

Additional info:
* package version(s) 247.1-4
* config and/or log files etc.
* link to upstream bug report, if any

Steps to reproduce:
Using the internet. Firefox, thunderbird, pacman, etc.

   resolved.conf (1 KiB)
This task depends upon

Closed by  Toolybird (Toolybird)
Wednesday, 27 September 2023, 08:11 GMT
Reason for closing:  Upstream
Additional comments about closing:  This looks quite old and stale and clearly not an Arch packaging issue. If still happening, please report upstream.
Comment by Martin (MartinX3) - Tuesday, 15 December 2020, 10:59 GMT
nss version used is 3.60-1
Comment by rainer (raneon) - Tuesday, 15 December 2020, 11:12 GMT
Same issue here after upgrading 2 systems. It was just a minor upgrade... what is wrong with this package?
Comment by Christian Hesse (eworm) - Tuesday, 15 December 2020, 14:13 GMT
I can't reproduce... Any error messages?
Any special configuration in /etc/nsswitch.conf?
Comment by Martin (MartinX3) - Tuesday, 15 December 2020, 16:30 GMT
The requested files
   nsswitch.conf (0.3 KiB)
   systemd-resolved.logs (659.9 KiB)
Comment by rainer (raneon) - Tuesday, 15 December 2020, 20:26 GMT
My config:
not changed: /etc/nsswitch.conf

ln -sf /run/systemd/resolve/resolv.conf /etc/resolv.conf

more /etc/systemd/resolved.conf.d/dns_over_tls.conf
[Resolve]
DNS=2606:4700:4700::1111 2606:4700:4700::1001 1.1.1.1 1.0.0.1
DNSOverTLS=yes
MulticastDNS=yes
DNSSEC=true
Comment by rainer (raneon) - Thursday, 17 December 2020, 14:31 GMT
For now, I did just downgrade systemd-libs to 247.1-3 and then domain names are resolved again.
Comment by Martin (MartinX3) - Friday, 18 December 2020, 22:35 GMT
Still broken with 247.2-1
Comment by Christian Hesse (eworm) - Friday, 18 December 2020, 23:41 GMT
The offending commit is:
https://github.com/systemd/systemd/commit/3c229a9afb670025a3c1792bf5ac233b5a566ec5

I am still unable to reproduce this, so maybe you want to open an upstream issue?
Comment by rainer (raneon) - Saturday, 19 December 2020, 14:30 GMT
After updating now my desktop, I cannot reproduce the issue with a LAN device. So it might be related to NetworkManager and/or wireless devices.
Comment by Martin (MartinX3) - Saturday, 19 December 2020, 17:36 GMT
Sadly happening on Wifi and LAN

I hope I have luck with my upstream report
https://github.com/systemd/systemd/issues/18025
Comment by rainer (raneon) - Saturday, 19 December 2020, 23:30 GMT
For LAN devices I've enabled systemd-networkd to bring up my network devices (DHCP) and this works reliable even with the latest systemd-libs package in Arch. Maybe the issue happens in combination with NetworkManager.
Comment by Martin (MartinX3) - Sunday, 20 December 2020, 09:39 GMT
I already use systemd-networkd for Wifi and LAN :(

Luckily on github are more people with this issue
Comment by Martin (MartinX3) - Sunday, 20 December 2020, 18:01 GMT
I was able to isolate the problem to the option `DNSOverTLS`
Since this commit the option breaks my dns resolution.
Without it, everything is fine.
Now I'll use only `DNSSEC` until the bug is fixed. :)
Comment by Ng Oon-Ee (ngoonee) - Saturday, 13 March 2021, 07:09 GMT
I have two (64-bit) Arch systems, one on wifi and one on LAN.

Fully upgrading (to systemd 247.4-1 from 247.3-1) on both machines broke domain name resolution in the LAN machine, but my wifi machine was working fine. Some comparisons showed that systemd-resolved was enabled on the LAN machine but not the wifi one, disabling that brought my resolution back. This took a while since I was scratching my head trying to find out why resolv.conf options weren't being taken into account.

Symptoms I got was that dig/drill worked fine but ping did not.
Comment by AK (Andreaskem) - Saturday, 13 March 2021, 08:23 GMT
I got bit by this on my WiFi interface. DNSSEC and DNSOverTLS are off. For some reason, domains without an IPv6 address seemed to work, still. With resolvectl, the error message was '[domain] does not have any RR of the requested type'. A downgrade to .3 immediately resolved the issue. For me, it seems similar to
https://github.com/systemd/systemd/issues/18917

edit:
My symptoms fit better with this
https://bugs.archlinux.org/task/69963
Comment by Buggy McBugFace (bugbot) - Tuesday, 08 August 2023, 19:11 GMT
This is an automated comment as this bug is open for more then 2 years. Please reply if you still experience this bug otherwise this issue will be closed after 1 month.

Loading...