Ubuntu
systemd package

systemd-resolved returns only short hostname when PTR record of local IP is requested

Bug #1737250 reported by Robert Sander
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

Ubuntu 17.10 comes with systemd-resolved as the default local resolver.

When querying the PTR record of any local IP address it returns only the hostname (without domain) and does not forward the query to the available nameservers.

This results in unwanted results.

How do I change that behaviours without disabling and masking systemd-resolved and manually putting the nameservers in /etc/resolv.conf?

Example:

root@files05:~# host 192.168.48.115
115.48.168.192.in-addr.arpa domain name pointer files05.
root@files05:~# host 192.168.48.116
116.48.168.192.in-addr.arpa domain name pointer files06.example.net.
root@files05:~# host 192.168.48.120
120.48.168.192.in-addr.arpa domain name pointer files05.
root@files05:~# host 192.168.48.120 192.168.48.2
Using domain server:
Name: 192.168.48.2
Address: 192.168.48.2#53
Aliases:

120.48.168.192.in-addr.arpa domain name pointer fileserv.example.net.

Tags: artful
Hans Joachim Desserud (hjd)
tags: added: artful
Revision history for this message
Steve Langasek (vorlon) wrote :

Does setting 'LLMNR=no' in /etc/systemd/resolved.conf and restarting systemd-resolved solve this for you?

(see also bug #1739672)

Changed in systemd (Ubuntu):
status: New → Incomplete
Revision history for this message
Robert Sander (gurubert) wrote :

Yep, that setting fixes the issue.

Please make LLMNR=no the default.

BTW: systemd-resolved seems to have many other issues, too. I do not think that it is fit to be included in a stable release.

Revision history for this message
Steve Langasek (vorlon) wrote :

> Yep, that setting fixes the issue.

> Please make LLMNR=no the default.

Yes, as stated in LP: #1739672, that is the plan for 18.04. It is clearly inappropriate for a DNS stub local resolver to silently proxy other protocols (such as LLMNR).

> BTW: systemd-resolved seems to have many other issues, too. I do not
> think that it is fit to be included in a stable release.

Please file bug reports against the systemd package in Launchpad for other issues that you encounter. We are committed to providing a solid local resolver for 18.04, but this is is dependent on us having a clear picture of the outstanding bugs in the implementation.

Changed in systemd (Ubuntu):
importance: Undecided → Medium
status: Incomplete → Triaged
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.