LTSP5

Client DNS is broken with systemd-networkd

Bug #1756260 reported by Alkis Georgopoulos
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
LTSP5
Fix Released
High
Alkis Georgopoulos

Bug Description

When systemd-networkd is used, resolv.conf is a symlink:
/etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf

Currently, /usr/share/ltsp/init-ltsp.d/10-resolv-conf can't cope with that, and this results in broken DNS in clients in recent distributions.

Revision history for this message
Bruce Pieterse (octoquad) wrote :

We are seeing this with an LTSP client using Ubuntu Server 18.04 with a fat client. On the client side, if we do systemd-resolved --set-dns=<ip> --interface=<interface> DNS lookups start to work again.

Changed in ltsp:
status: New → Confirmed
Revision history for this message
Bruce Pieterse (octoquad) wrote :

Apologies, correct command is systemd-resolve not systemd-resolved.

Revision history for this message
fottsia (fottsia) wrote :

I verify that this is still an issue with LTSP in Ubuntu MATE 18.04.

Revision history for this message
Alkis Georgopoulos (alkisg) wrote :

Fix committed in https://git.launchpad.net/ltsp/commit/?id=29e60d090a8058340fe1546f2ca546ab4fe70bd5

Changed in ltsp:
assignee: nobody → Alkis Georgopoulos (alkisg)
importance: Undecided → High
status: Confirmed → Fix Committed
Alkis Georgopoulos (alkisg)
Changed in ltsp:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.