[solved] systemd 240 breaks local domain resolving

lnxsrt · 2019-02-14 02:16:29

I've noticed that after upgrading a couple of machines to systemd 240 that local domain resolution no longer works. I've confirmed that all of the settings are correct and identical and the "search domain" is present in the /etc/resolv.conf (link to /run/systemd/resolve/stub-resolv.conf). "networkctl status" confirms that all is identical.

Identical config works with 239, but no longer works with 240. The long form still works (hostname.domain), but the short version is broken (hostname). Downgrading to 239 fixes the issue. Anyone else seeing similar behavior?

Last edited by lnxsrt (2019-02-23 15:32:34)

dmartins · 2019-02-14 05:21:11

Looks like it could be this upstream issue, which has a fix merged for version 241.
https://github.com/systemd/systemd/issues/11391

You can try cherry picking this commit to test it by adding 'fea46786ce45f1fa4ba2ad3a88049ccf078e68d3' to the backports array in the systemd PKGBUILD, then run makepkg as usual to create updated packages.

If this works for you, open a bug on the Arch Linux bug tracker referencing the systemd issue from above, and the devs may backport this to the official repos.

Last edited by dmartins (2019-02-14 05:23:00)

Defender110 · 2019-02-21 18:52:56

disregard. sorry, I don't think my issue is directly related to this bug.

Last edited by Defender110 (2019-02-21 18:55:34)

lnxsrt · 2019-02-21 18:56:54

241 has fixed local name resolution for me. It works as it did in 239.

seth · 2019-02-21 21:09:53

You might want to edit your OP and tag that into the subject.

lnxsrt · 2019-04-28 00:52:21

Broken again in 242. I've really tried to accept systemd, but they make it so very hard. Unreal.

Lone_Wolf · 2019-04-28 11:03:07

I've really tried to accept systemd, but they make it so very hard.

That's a familiar feeling to me .

as for the name resolving problems :
systemd-resolved appears to be the single biggest source of network problems this year.

You can't use systemd-networkd without systemd-resolved.
Networkmanager also is using systemd-resolved now by default.

You may want to look at other network managing options.
dhcpcd , dhclient, netctl are some of the possibilities.

seth · 2019-04-28 11:44:20

If you desire a local dns cache (what's questionable enough and silly if you've a dns proxy in your router) have a look at the alternatives here: https://wiki.archlinux.org/index.php/Do … NS_servers

Head_on_a_Stick · 2019-04-28 21:14:59

Lone_Wolf wrote:

You can't use systemd-networkd without systemd-resolved.

Yes you can:

empty@shinken:~ $ systemctl is-enabled systemd-resolved
disabled
1|empty@shinken:~ $ networkctl --no-p
IDX LINK             TYPE               OPERATIONAL SETUP     
  1 lo               loopback           carrier     unmanaged 
  2 enp0s25          ether              no-carrier  configuring
  3 wlp2s0           wlan               routable    configured

3 links listed.
empty@shinken:~ $

Lone_Wolf wrote:

Networkmanager also is using systemd-resolved now by default.

If the OP removes the symlink and keeps /etc/resolv.conf as a static file then systemd-resolved will act as a consumer rather than a provider.

Or just disable it, as seth suggests.

Lone_Wolf · 2019-04-29 10:23:42

Thanks for the correction .

My personal solution :
only use tools that work with multiple PID1 implementations.
I use dhcpcd + ntp and let my router take care of name resolution.

Last edited by Lone_Wolf (2019-04-29 10:24:01)

seth · 2019-04-29 15:08:15

You can, but I'm not sure whether we've already established if systemd-networkd (by itself) can obtain the DNS server via dhcp to feed resolv.conf (and at least idk how)

gdl · 2019-04-30 06:06:03

lnxsrt wrote:

Broken again in 242. I've really tried to accept systemd, but they make it so very hard. Unreal.

Yea, broken for me too.

Arch Linux

#1 2019-02-14 02:16:29

[solved] systemd 240 breaks local domain resolving

#2 2019-02-14 05:21:11

Re: [solved] systemd 240 breaks local domain resolving

#3 2019-02-21 18:52:56

Re: [solved] systemd 240 breaks local domain resolving

#4 2019-02-21 18:56:54

Re: [solved] systemd 240 breaks local domain resolving

#5 2019-02-21 21:09:53

Re: [solved] systemd 240 breaks local domain resolving

#6 2019-04-28 00:52:21

Re: [solved] systemd 240 breaks local domain resolving

#7 2019-04-28 11:03:07

Re: [solved] systemd 240 breaks local domain resolving

#8 2019-04-28 11:44:20

Re: [solved] systemd 240 breaks local domain resolving

#9 2019-04-28 21:14:59

Re: [solved] systemd 240 breaks local domain resolving

#10 2019-04-29 10:23:42

Re: [solved] systemd 240 breaks local domain resolving

#11 2019-04-29 15:08:15

Re: [solved] systemd 240 breaks local domain resolving

#12 2019-04-30 06:06:03

Re: [solved] systemd 240 breaks local domain resolving

Board footer