<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - systemd-resolved: domain and search lines missing from resolv.conf"
href="https://bugs.freedesktop.org/show_bug.cgi?id=85397#c6">Comment # 6</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - systemd-resolved: domain and search lines missing from resolv.conf"
href="https://bugs.freedesktop.org/show_bug.cgi?id=85397">bug 85397</a>
from <span class="vcard"><a class="email" href="mailto:aelschuring@hotmail.com" title="Arno Schuring <aelschuring@hotmail.com>"> <span class="fn">Arno Schuring</span></a>
</span></b>
<pre>(In reply to Lennart Poettering from <a href="show_bug.cgi?id=85397#c5">comment #5</a>)
>
<span class="quote">> You need to install the dbus policy file for resolved as well, the binary
> alone won't be enough.</span >
Thanks, that helps. With that change (copying
src/resolve/org.freedesktop.resolve1.conf to /etc/dbus/system.d/), the
-resolved from HEAD starts without issue, however it still doesn't write any
domain or search lists. It makes no difference which -networkd I use.
I'm not at home so I can't test the duplicate name servers issue, but I do
notice this:
$ grep ^DNS /run/systemd/netif/leases/* /etc/systemd/resolved.conf
/run/systemd/netif/leases/4:DNS=10.52.0.10 10.0.0.23 10.0.0.17
/etc/systemd/resolved.conf:DNS=2a01:4f8:161:4109::6 2001:4ba0:cafe:383::1
$ cat /etc/resolv.conf
# This file is managed by systemd-resolved(8). Do not edit.
#
# Third party programs must not access this file directly, but
# only through the symlink at /etc/resolv.conf. To manage
# resolv.conf(5) in a different way, replace the symlink by a
# static file or a different symlink.
nameserver 10.0.0.23
nameserver 2001:4ba0:cafe:383::1
nameserver 10.0.0.17
# Too many DNS servers configured, the following entries may be ignored.
nameserver 2a01:4f8:161:4109::6
nameserver 10.52.0.10
That is, the current HEAD version reorders the nameserver list. It mixes
dhcp-provided resolvers with static ones, and it puts the local dns server
last, even though it was listed first in the dhcp answer.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>