Comment 14 for bug 1685900

Dimitri,
thank you for the information.

Now, as I am not very familiar with the systemd nor the dns setup, I would be happy if you could give me advice how to proceed on this issue.

The status of my setup is as follows.
I have installed all the latest packages of artful aardvark, also from proposed repo.

Network:
I have now installed systemd 233-5ubuntu1.
Like I wrote, if I install dnsutils and bind9-host, I get no working dns (not even after several reboots).
But, if I install bind9, the dns is working (after one reboot).
This means already, I suppose, I do not have systemd-resolved working.
My setup is using bind9 dns server instead.

Here is the output of systemd-resolve --status:
Failed to get global data: Unit dbus-org.freedesktop.resolve1.service not found.

Here is the output of systemctl status systemd-journald.service:
● systemd-journald.service - Journal Service
   Loaded: loaded (/lib/systemd/system/systemd-journald.service; static; vendor preset: enabled)
   Active: active (running) since Wed 2017-04-26 09:59:31 EEST; 18min ago
     Docs: man:systemd-journald.service(8)
           man:journald.conf(5)
 Main PID: 301 (systemd-journal)
   Status: "Processing requests..."
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/systemd-journald.service
           └─301 /lib/systemd/systemd-journald
april 26 09:59:31 Sabertooth systemd-journald[301]: Journal started
april 26 09:59:31 Sabertooth systemd-journald[301]: Runtime journal (/run/log/journal/bd732b34a1caf7
156751544d541ed208) is 8.0M, max 157.3M, 149.3M free.
april 26 09:59:31 Sabertooth systemd-journald[301]: Runtime journal (/run/log/journal/bd732b34a1caf7
156751544d541ed208) is 8.0M, max 157.3M, 149.3M free.
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

Here is the output of cat /etc/resolv.conf:
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.

* * * * *

Now, with the older systemd 232-21ubuntu3 the systemd-resolved was working OK (and dns).
Here is the output from systemd 232-21ubuntu3 systemd-resolve --status:
Global
          DNSSEC NTA: 10.in-addr.arpa
                      16.172.in-addr.arpa
                      168.192.in-addr.arpa
                      17.172.in-addr.arpa
                      18.172.in-addr.arpa
                      19.172.in-addr.arpa
                      20.172.in-addr.arpa
                      21.172.in-addr.arpa
                      22.172.in-addr.arpa
                      23.172.in-addr.arpa
                      24.172.in-addr.arpa
                      25.172.in-addr.arpa
                      26.172.in-addr.arpa
                      27.172.in-addr.arpa
                      28.172.in-addr.arpa
                      29.172.in-addr.arpa
                      30.172.in-addr.arpa
                      31.172.in-addr.arpa
                      corp
                      d.f.ip6.arpa
                      home
                      internal
                      intranet
                      lan
                      local
                      private
                      test
Link 2 (eth0)
      Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
       LLMNR setting: yes
MulticastDNS setting: no
      DNSSEC setting: no
    DNSSEC supported: no
         DNS Servers: 193.210.18.18
                      193.210.19.19
          DNS Domain: dhcp.inet.fi

* * * * * * * *

So please, can you print what specific commands or installations should I do now in order to get systemd-resolved service running and resolf.conf pointing at it?

Also how do I get the journal logs?
Runtime journal (/run/log/journal/bd732b34a1caf7156751544d541ed208) is 8.0M, so it is a very big file indeed.