On artful, no working dns after upgrading to systemd 233-5ubuntu1

[Harry]

After upgrading to the newest systemd 233-5ubuntu1 (in artful proposed) I got no nameserver (dns).
This is very likely a DNS issue.
As a workaround downgrading back to systemd 232-21ubuntu3 the network and DNS work fine.
Or instead, I must manually start systemd-resolved:
~$ sudo service systemd-resolved restart

So something odd has happened between these versions.
Systemd-resolved is not starting automatically at boot anymore.

My setup is a fully upgraded artful with proposed repo turned on.
I use only Gnome DE with GDM.
Everything else works fine, but not systemd 233-5ubuntu1.

[Harry (harry33)]

With the systemd 233-5ubuntu1:

~$ systemd-resolve --status
Failed to get global data: Unit dbus-org.freedesktop.resolve1.service not found.

~$ 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.

With the systemd 232-21ubuuntu3:

~$ 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

~$ 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.

nameserver 127.0.0.53

[Jeremy Bícha (jbicha)]

I am not running artful myself yet, but I am setting the block-proposed tag so that this will be looked into before letting the systemd update out of artful-proposed.

[Harry (harry33)]

Here are the warnings and messages I get when upgrading systemd 232-21-ubuntu3 => 233-5ubuntu1 with synaptic:

Job for systemd-journald.service failed because the service did not take the steps required by its unit configuration.
See "systemctl status systemd-journald.service" and "journalctl -xe" for details.
Removing obsolete conffile /etc/dbus-1/system.d/org.freedesktop.hostname1.conf ...
Removing obsolete conffile /etc/dbus-1/system.d/org.freedesktop.locale1.conf ...
Removing obsolete conffile /etc/dbus-1/system.d/org.freedesktop.login1.conf ...
Removing obsolete conffile /etc/dbus-1/system.d/org.freedesktop.network1.conf ...
Removing obsolete conffile /etc/dbus-1/system.d/org.freedesktop.resolve1.conf ...
Removing obsolete conffile /etc/dbus-1/system.d/org.freedesktop.systemd1.conf ...
Removing obsolete conffile /etc/dbus-1/system.d/org.freedesktop.timedate1.conf ...
...
Removing obsolete conffile /etc/init/udev.conf ...
Removing obsolete conffile /etc/init/udevmonitor.conf ...
Removing obsolete conffile /etc/init/udevtrigger.conf ...
Processing triggers for dbus (1.10.10-1ubuntu2) ...

And, when downgrading back to 232-21ubuntu3 there are no such warnings nor messages.

Losing the network DNS may have something to do with those
"removing the obsolete conffile /etc/d-bus1/..."
messages.

[Harry (harry33)]

I mean particularly this.

~$ systemd-resolve --status
"Failed to get global data: Unit dbus-org.freedesktop.resolve1.service not found."

And as I wrote above, when upgrading to systemd 233-5ubuntu1 I get this:

"Removing obsolete conffile /etc/dbus-1/system.d/org.freedesktop.resolve1.conf ..."

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Dimitri John Ledkov (xnox)]

Messages about removing obsolete conffiles are normal, as dbus config files have moved form /etc to /usr; and upstart jobs are no longer needed as upstart is not required anymore.

I am suspecting if one reboots after an upgrade eveyrhting is fine.

I believe we also need to potentially reload dbus configuration, after the dbus files are moved to /usr and I'm not sure if this is done already or not.

I will investigate further the upgrade issue you are pointing out.

[Harry (harry33)]

Dimitri,

in my case, not even several reboots helped.
It is all the same here, though network should be up, there is no working dns.

[Dimitri John Ledkov (xnox)]

I would like to see package versions of everything that is installed; syslog and journal log; as per your messages it appears that systemd-resolved.service is not running at all, when it should be.

Note that DNSSEC is re-enabled in artful.

[Dimitri John Ledkov (xnox)]

Note i cannot reproduce your issue locally at the moment, and dns resolution works for me as expected.

[Harry (harry33)]

Dmitri,

"I would like to see package versions of everything that is installed"

I have a fully updated artful setup with proposed enabled.

"... as per your messages it appears that systemd-resolved.service is not running at all, when it should be."

Systemd-resolved.service works just fine with systemd 232-21ubuntu3 (see comment #1), but not with systemd 233-5ubuntu1.

How does that service changed between these versions?

"Note that DNSSEC is re-enabled in artful."

What do you mean by that? Should I have certain packages installed because of that?
The new systemd 233-5ubuntu1 did not pull in any new packages.

Note that my setup works just fine with systemd 232-21ubuntu3.

[Harry (harry33)]

OK,

So I got this issue fixed by installing the package bind9.
I tested several times, but dnsutils with bind9-host was not enough.
So I removed those two and installed bind9 instead.
Now I have a working dns.

[Dimitri John Ledkov (xnox)]

How does that service changed between these versions?

$ git diff v232..v233 src/resolve/ | diffstat
36 files changed, 950 insertions(+), 284 deletions(-)

And that's just resolved specific code, but there are a lot more changes in shared code.

You have not provided any system logs, error messages from the daemon, or steps to reproduce the problem.

If you are not going to share systemd-journal logs of the failing systemd-resolved.service there is nothing I can do to fix the problem you have encountered.

Are you sure you are using systemd-resolved now? Is the service running and does resolv.conf point at it?

[Dimitri John Ledkov (xnox)]

dnsutils with bind9-host should be sufficient on regular systems to have network up.

[Harry (harry33)]

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
             ...

[Harry (harry33)]

Dimitri,
one more test I just did.

I started systemd-resolved manually:
~$ sudo service systemd-resolved restart

After that the output of systemd-resolve --status is OK:
Global
         DNS Servers: 8.8.8.8
                      8.8.4.4
                      2001:4860:4860::8888
                      2001:4860:4860::8844
          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: LLMNR/IPv4 LLMNR/IPv6
       LLMNR setting: yes
MulticastDNS setting: no
      DNSSEC setting: allow-downgrade
    DNSSEC supported: yes

[Harry (harry33)]

Dimitri,

My setup does not need the package bind9.
But I need to start systemd-resolved service manually.

After that the output of systemd-resolve --status is OK:
Global
         DNS Servers: 8.8.8.8
                      8.8.4.4
                      2001:4860:4860::8888
                      2001:4860:4860::8844
          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: LLMNR/IPv4 LLMNR/IPv6
       LLMNR setting: yes
MulticastDNS setting: no
      DNSSEC setting: allow-downgrade
    DNSSEC supported: yes

So, what do I have to do to get this working automatically at the boot?

[Dimitri John Ledkov (xnox)]

On 26 April 2017 at 09:11, Harry <email address hidden> wrote:
> Dimitri,
>
> My setup does not need the package bind9.
> But I need to start systemd-resolved service manually.
>
> So, what do I have to do to get this working automatically at the boot?
>

Artful is not ready for general usage. And -proposed packages in
artful are not ready for general consumption at all and are meant for
automatic testing only. Especially if one doesn't know how to check
the logs of individual services and fix their own systems.

I guess the easiest would be to collect a full sosreport.

Install package called sosreport and run `sudo sosreport` to collect
extensive information about your system. The tarball produced will be
large, please upload it.

Unfortunately, the questions you are asking are more suitable as
support questions on how to use journalctl / systemctl - please check
https://www.ubuntu.com/support/community-support or
https://www.ubuntu.com/support

--
Regards,

Dimitri.

[Harry (harry33)]

Sosreport of my setup.

[Harry (harry33)]

Dimitri,

Just added a sosreport as you requested.

My setup is a nearly minimal setup, containing only the applications I need.

The issue here is what packages are needed to get the new systemd 233-5ubuntu1 and its resolved working.
And more, exactly those packages that were not needed to get systemd 232-21ubuntu3 resolved working, because that was OK in my setup.

I hope this helps a bit.

[Harry (harry33)]

Dimitri,
I have a question about the chosen nameservers.

When using systemd 232-21-ubuntu3 or earlier, it was like this (systemd-resolve --status):
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

When using systemd 233-5ubuntu1 (manual start), it is like this (systemd-resolve --status):
Global
         DNS Servers: 8.8.8.8
                      8.8.4.4
                      2001:4860:4860::8888
                      2001:4860:4860::8844

Note the different dns servers.
The latter (8.8.8.8. ...) came from /run/systemd/resolve/resolv.conf

I think dns servers 193.210.18.18 and 193.210.19.19 are the correct ones.
Why are they different.

[Harry (harry33)]

Just to be clear and let those interested know,
my setup is working fine now with the latest systemd (in proposed now) 233-5ubuntu1.

I installed and reinstalled several packages related to systemd and the command
"systemd-resolve --status"
is OK now.
Systemd-resolved is working well now.

So this bug is self-fixed.

[Jeremy Bícha (jbicha)]

This bug report is being closed due to your last comment regarding this being fixed. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

There simply isn't enough information here to tell whether there was a bug here or not, especially because you are running a custom "minimal setup" with -proposed enabled in a development release. A better bug report would include the specific steps someone else could take to reproduce the issue.

[Shahar Or (mightyiam)]

I have a similar issue:

```
➜ ~ git:(master) ✗ systemd-resolve --status
Failed to get global data: Unit dbus-org.freedesktop.resolve1.service not found.
```

```
➜ ~ git:(master) ✗ dpkg -l | grep systemd
ii dbus-user-session 1.10.18-1ubuntu2 all simple interprocess messaging system (systemd --user integration)
ii libnss-resolve:amd64 233-8ubuntu1 amd64 nss module to resolve names via systemd-resolved
ii libpam-systemd:amd64 233-8ubuntu1 amd64 system and service manager - PAM module
ii libsystemd0:amd64 233-8ubuntu1 amd64 systemd utility library
ii python3-systemd 233-1build1 amd64 Python 3 bindings for systemd
ii systemd 233-8ubuntu1 amd64 system and service manager
ii systemd-sysv 233-8ubuntu1 amd64 system and service manager - SysV links
```

I, too, have a custom "minimal setup" 17.10.

[Shahar Or (mightyiam)]

I do not seem to have the /etc/init.d/systemd-resolved symlink at all. Is this normal?

[Shahar Or (mightyiam)]

Here is my sosreport.

[Dimitri John Ledkov (xnox)]

On 26 July 2017 at 10:18, Shahar Or <email address hidden> wrote:
> I do not seem to have the /etc/init.d/systemd-resolved symlink at all.
> Is this normal?
>

Yes normal, Ubuntu only supports systemd as the init system, and
/etc/init & /etc/init.d are not in use for most services. And,
specifically, init.d scripts have never been used for
systemd-resolved.
--
Regards,

Dimitri.

[Shahar Or (mightyiam)]

Should a process `systemd-resolved` be running? I don't have it running at all.

[Dimitri John Ledkov (xnox)]

@Shahar this is not a support forum, this bug is closed. Please stop commenting / high-jacking this bug report, for your own support query. If you have a new bug report, please open a new bug report. This bug is no longer monitored.