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#69963 - [systemd] Stub resolver cannot resolve host

Attached to Project: Arch Linux
Opened by fsdsfd (BCD889) - Friday, 12 March 2021, 22:53 GMT
Last edited by Christian Hesse (eworm) - Monday, 15 March 2021, 06:57 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To Christian Hesse (eworm)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 15
Private No

Details

Description: After upgrade systemd to 247.4-1 pacman and other apps can't resolve hosts, dns resolver works fine only with firefox


systemd 247.4-1

/etc/systemd/resolved.conf.d/resolved.conf
[Resolve]
DNS=1.1.1.1 1.0.0.1
FallbackDNS=
DNSSEC=true
DNSOverTLS=yes


/etc/systemd/network/eth0.network
[Match]
Name=enp3s0

[Network]
DHCP=ipv4

/usr/share/zoneinfo/Europe/Rome -> /etc/localtime
/run/systemd/resolve/stub-resolv.conf -> /etc/resolv.conf
This task depends upon

Closed by  Christian Hesse (eworm)
Monday, 15 March 2021, 06:57 GMT
Reason for closing:  Fixed
Additional comments about closing:  systemd 247.4-2
Comment by fsdsfd (BCD889) - Friday, 12 March 2021, 22:53 GMT
nb: downgrade to 247.3 solve the problem
Comment by Doug Newgard (Scimmia) - Saturday, 13 March 2021, 00:14 GMT
Wait, /run/systemd/resolve/stub-resolv.conf is a symlink to /etc/resolv.conf? How is that supposed to work?
Comment by fsdsfd (BCD889) - Saturday, 13 March 2021, 06:53 GMT
this scenario is recommended upstream
https://www.freedesktop.org/software/systemd/man/systemd-resolved.service.html
https://wiki.archlinux.org/index.php/Systemd-resolved#DNS
Comment by AK (Andreaskem) - Saturday, 13 March 2021, 08:38 GMT
Possibly the same issue?
https://bugs.archlinux.org/task/68981
https://github.com/systemd/systemd/issues/18917

Although they seem somewhat different. My problems only appeared on .4 and I do not have DNSSEC or DNSoverTLS enabled so they might fit better with this bug report.
Comment by rainer (raneon) - Saturday, 13 March 2021, 11:02 GMT
Oh no, so it got worse... I was affected by the Wifi bug already and now my LAN devices are not working anymore.
Comment by Mel (Mel) - Saturday, 13 March 2021, 11:06 GMT
Having the same problem with 247.4.
@Vito does your firefox have DoH enabled? I suspect that's why it was able to resolve domains, bypassing systemd-resolved completely.
Comment by Gabor Hauzer (cysp74) - Saturday, 13 March 2021, 11:58 GMT
Having the same problem.

Tests performed:
Behind openwrt + dnsmasq caching -> systemd-resolved fails on certain domains - some works, others not. Weird.
Shunted and using hotspot on android -> systemd-resolved got back will all domains (same as prev check).

Doesn't make any difference DNS= and FallbackDNS= modifications at resolved.conf.

/etc/resolv.conf point to stub (/etc/resolv.conf -> /var/run/systemd/resolve/stub-resolv.conf)

Not related with NetworkManager, systemd-networkd, wifi, ethernet.
Because has got the same behavior on two different machines (one is attached with wifi + networmanager, whilst other runs with systemd-networkd + cable).
Comment by rainer (raneon) - Saturday, 13 March 2021, 12:02 GMT
Yes, Firefox can circumvent the dns config of the host if DoH is enabled. I've downloaded with with Firefox the package systemd 247.3-1 (it was not anymore in my local cache) so that I could downgrade for now.
Comment by Magnus Boman (katt) - Saturday, 13 March 2021, 12:35 GMT
Getting this as well, reverted to 247.3 to get online. I have DNSSEC=allow-downgrade and use DNS=9.9.9.10.
Comment by Doug Newgard (Scimmia) - Saturday, 13 March 2021, 14:14 GMT
> this scenario is recommended upstream
> https://www.freedesktop.org/software/systemd/man/systemd-resolved.service.html
> https://wiki.archlinux.org/index.php/Systemd-resolved#DNS

Since others are having the same issue with a valid configuration, I'm going to assume you just got your notation backwards.
Comment by Tatsuyuki Ishi (ishitatsuyuki) - Sunday, 14 March 2021, 07:07 GMT
Can we have this update backed out while the upstream figures out what's the root cause? It's awful trying to figure out what's wrong while having your internet broken.
Comment by fsdsfd (BCD889) - Sunday, 14 March 2021, 08:16 GMT
i switch to git branch from aur, resolved works fine, only 247.4 is affected
Comment by Christian Hesse (eworm) - Sunday, 14 March 2021, 20:38 GMT
Does systemd 247.4-2 fix the issue for you?
Comment by Gabor Hauzer (cysp74) - Sunday, 14 March 2021, 21:03 GMT
On my end *-2 works definitely better, no issues found since I rolled out. Thanks for quick roundtrip.
Comment by fsdsfd (BCD889) - Sunday, 14 March 2021, 21:23 GMT
247.4-2 seems to work well, thanks
Comment by Magnus Boman (katt) - Sunday, 14 March 2021, 23:35 GMT
Can confirm 247.4-2 works as expected!
Comment by John (gee) - Monday, 15 March 2021, 01:40 GMT
It works fine here too!

Thanks for the quick fix!

Loading...