After downgrading openresolv from 3.17.2-1 to 3.17.0-1 everything works again.
As I’ve been moved so kindly by @Yochanan to this section of the forum and this is my first obvious bug in testing branch, could someone tell me how I should proceed?
Do you expect me to report this bug upstream?
Will openresolv be downgraded in the testing repo in general?
Or should I wait until it is confirmed here in the forum?
Just checked my pacnews, no change to DNS related stuff.
I use netctl and had an issue with dhcpcd/systemd-resolved, can’t remember exactly what it was. Since then I use openresolv as the more simple solution.
They expect it to be already fixed in 3.17.3. It’s already in the Arch repos.
I’ll wait for it to arrive in testing, or is there a way to install it explicitly from unstable? If it’s already in there?
You can always use pacman -U https://.... - beware of the mirrors sync at different times
$ mbn info openresolv -q
Branch : archlinux
Name : openresolv
Version : 3.17.3-1
Repository : extra
Build Date : Sat 13 Dec 2025 22:34:26
Packager : Jan Alexander Steffens (heftig) <heftig@archlinux.org>
Branch : unstable
Name : openresolv
Version : 3.17.2-1
Repository : extra
Build Date : Fri 12 Dec 2025 16:16:58
Packager : Jan Alexander Steffens (heftig) <heftig@archlinux.org>
Branch : testing
Name : openresolv
Version : 3.17.2-1
Repository : extra
Build Date : Fri 12 Dec 2025 16:16:58
Packager : Jan Alexander Steffens (heftig) <heftig@archlinux.org>
Branch : stable
Name : openresolv
Version : 3.17.0-1
Repository : extra
Build Date : Fri 27 Jun 2025 00:53:52
Packager : Jan Alexander Steffens (heftig) <heftig@archlinux.org>