FS#61335 - [filesystem][systemd] search domains not used for name resolution

Attached to Project: Arch Linux
Opened by Jarkko Torvinen (fernie) - Thursday, 10 January 2019, 07:00 GMT
Last edited by Sébastien Luttringer (seblu) - Tuesday, 19 May 2020, 22:39 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Dave Reisner (falconindy)
Christian Hesse (eworm)
Sébastien Luttringer (seblu)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

Description:
systemd 240 changed behaviour of systemd-resolved and search domain(s) are no longer appended automatically, this breaks applications (ie ping/ssh/telnet)
See https://github.com/systemd/systemd/issues/11325

One solution is to change /etc/nsswitch.conf
from:
hosts: files mymachines myhostname resolve [!UNAVAIL=return] dns
to:
hosts: files mymachines myhostname resolve dns [!UNAVAIL=return]


Additional info:
filesystem 2018.12-2
systemd 240.0-3


Steps to reproduce:
See https://github.com/systemd/systemd/issues/11325#issuecomment-452635588
This task depends upon

Closed by  Sébastien Luttringer (seblu)
Tuesday, 19 May 2020, 22:39 GMT
Reason for closing:  Not a bug
Comment by Dave Reisner (falconindy) - Thursday, 10 January 2019, 12:53 GMT
Well, that's a silly change. There's no point in moving [!UNAVAIL=return] to the end of the line, since the stack returns at the end, regardless. It does seem that the [!UNAVAIL=return] is unnecessary these days, but clarification from upstream is needed.
Comment by Jarkko Torvinen (fernie) - Thursday, 10 January 2019, 14:20 GMT
Yeah, agree, silly moving to end. Sorry for suggesting that :)
Comment by Bogdan Szczurek (thebodzio) - Wednesday, 16 January 2019, 13:02 GMT
I can confirm the problem.

Edit:

The problem appears to be related to this upstream commit: https://github.com/systemd/systemd/commit/1750854916df6a777e6c12451eb5eb2aebbc93fe. It changes the behaviour of the systemd-resolved to give preference to LLMNR over DNS whenever the former is enabled. It is explained fully in this comment: https://github.com/systemd/systemd/issues/11325#issuecomment-453616064.

A simple, although a bit ugly and hasty, workaround (if practical and possible in ones situation) is to disable LLMNR for systemd-resolved by setting LLMNR to “no” in /etc/systemd/resolved.conf (it is set to “yes” by default).

Loading...