Arch Linux User Repository

I had the same error. This solves it.
https://github.com/jonathanio/update-systemd-resolved#how-to-enable

Make sure that you have systemd-resolved enabled and running:

systemctl enable systemd-resolved.service
systemctl start systemd-resolved.service

@JM9 there have been issues around the use of --id for logger within the script. The latest version removes that so it should now work for you. I can confirm it works fine for me under 1.2.6-1:

Jul 25 09:30:56 laptop update-systemd-resolved[3]: Adding DNS Routed Domain .
Jul 25 09:30:56 laptop openvpn[2]: <14>Jul 25 09:30:56 update-systemd-resolved: Adding DNS Routed Domain .
Jul 25 09:30:56 laptop update-systemd-resolved[4]: Adding IPv4 DNS Server 10.8.16.1
Jul 25 09:30:56 laptop openvpn[2]: <14>Jul 25 09:30:56 update-systemd-resolved: Adding IPv4 DNS Server 10.0.0.1
Jul 25 09:30:56 laptop update-systemd-resolved[5]: SetLinkDNS(5 1 2 4 10 0 0 1)
Jul 25 09:30:56 laptop openvpn[2]: <14>Jul 25 09:30:56 update-systemd-resolved: SetLinkDNS(5 1 2 4 10 0 0 1)
Jul 25 09:30:56 laptop update-systemd-resolved[6]: SetLinkDomains(5 1 . true)
Jul 25 09:30:56 laptop openvpn[2]: <14>Jul 25 09:30:56 update-systemd-resolved: SetLinkDomains(5 1 . true)

with latest systemd/openvpn/dbus updates this script is no longer working:

Unit dbus-org.freedesktop.resolve1.service not found.
update-systemd-resolved[3477]: 'busctl' exited with status 1
WARNING: Failed running command (--up/--down): external program exited with error status: 1

@noraj bash is the scripting language the script is written in, and because it makes use of arrays as well as probably the odd bashism, I don't think you can run it in any other shell at the moment.

Why would you need bash ?

@aryklein,

Fixed. My build server flagged it too, but I didn't know about `makepkg -g`; that'll make things easier in the future. Thanks.

I got a validity check error:

==> ERROR: One or more files did not pass the validity check!

I ran 'makepkg -g' and replaced the sha256sums and sha512sums in the PKGBUILD with my output.

sha256sums=('0decae4753d0ad36bb7990252ef21fe34d9ff8d00117e09965f4c98bb2c5e26e')
sha512sums=('8a415d8727e263f5b47aea914d21a6b4fc04be2a956851b9903b5fe4139123368648c1573651a52f149f03e9a776517fc94ca8ba532ea496695cd5c1c17dd03e')

@demoji,

Thanks for the feedback. The post_install script was just a copy of the one used in the google-chrome* packages as that was (at the time) the easiest one to get my hands on when I needed to work out how to add the message. I've toned it down to just a simple echo statement and fixed the messages to separate down/down-pre.

Your post_install notes are out of sync with your upstream README.md.

And I think colored "===> NOTE: bold text" is trying too much, but whatever.

@afiskon,

The purpose of the script is not to update /etc/resolve.conf, as that is a backwards compatibility layer provided by systemd-resolved for programs which do not communicate directly with it over DBUS, nor don't use the stand NSS layer in glibc.

The preferred method is to update your nsswitch.conf file and replace the "dns" option under "hosts:" to "resolve", or add "resolve" before "dns". DOMAIN and DOMAIN-SEARCH can then be used to route appropriately selected domains to the DNS servers on that link. At least in these cases the DNS requests will only be directed to the servers in question rather than broadcasted to all.

Have you tried the following? Maybe as a catch-all, that could work.

dhcp-option DOMAIN .

Otherwise, I'm not sure atm if system-resolved supports overriding all previously configured DNS servers temporarily for the life of a link.