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

[Thomas Schweikle]

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

-> resolv.conf only holds two lines:
--- snip

nameserver 127.0.0.1
--- snap

and "host google.com" leads to
Host google.com not found: 5(REFUSED)

dnsmasq is running, but does not know whom to query upstream, because "/etc/resolv.conf" only holds the local address.

"/etc/resolv.conf" is created by "resolvconf". Systems address is assigned by dhclient.

"/etc/dhcp/dhclient.conf" holds:
--- snip
option rfc3442-classless-static-routes code 121 = array of unsigned integer 8;

send host-name = gethostname();
request subnet-mask, broadcast-address, time-offset, routers,
        domain-name, domain-name-servers, domain-search, host-name,
        dhcp6.name-servers, dhcp6.domain-search, dhcp6.fqdn, dhcp6.sntp-servers,
        netbios-name-servers, netbios-scope, interface-mtu,
        rfc3442-classless-static-routes, ntp-servers;
timeout 300;
--- snap

There are three instances of dnsmasq started:
--- snip
 7272 ? S 0:00 /usr/sbin/dnsmasq -x /run/dnsmasq/dnsmasq.pid -u dnsmasq -r /run/dnsmasq/resolv.conf -7 /etc/dnsmasq.d,.dpkg-dist,.dpkg-old,.dpkg-new --local-service --trust-anchor=.,19036,8,2,49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5 --trust-anchor=.,20326,8,2,e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
 7838 ? S 0:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
 7839 ? S 0:00 \_ /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
--- snap

"/etc/network/interaces" holds:
--- snip
# Local loopback
auto lo
iface lo inet loopback
--- snap

What I'd expected after upgrading: working network config with a working "/etc/resolv.conf"!

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: systemd 237-3ubuntu10.3
ProcVersionSignature: Ubuntu 4.4.0-137.163-generic 4.4.144
Uname: Linux 4.4.0-137-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
Date: Wed Oct 3 11:57:42 2018
InstallationDate: Installed on 2011-10-19 (2540 days ago)
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MachineType: Acer TravelMate P643-M
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-137-generic root=/dev/mapper/vg-root ro elevator=deadline splash acpi=force reboot=bios ipv6.disable=1 vt.handoff=1
SourcePackage: systemd
UpgradeStatus: Upgraded to bionic on 2018-10-02 (1 days ago)
dmi.bios.date: 10/21/2013
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: V2.15
dmi.board.asset.tag: No Asset Tag
dmi.board.name: TravelMate P643-M
dmi.board.vendor: Acer
dmi.board.version: V2.15
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: Acer
dmi.chassis.version: V2.15
dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd10/21/2013:svnAcer:pnTravelMateP643-M:pvrV2.15:rvnAcer:rnTravelMateP643-M:rvrV2.15:cvnAcer:ct9:cvrV2.15:
dmi.product.name: TravelMate P643-M
dmi.product.version: V2.15
dmi.sys.vendor: Acer

[Launchpad Janitor (janitor)]

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

[Jim Baxter (jbaxter)]

This happened to me when I upgraded from 16.04 LTS to 18.04 LTS, I noticed error dialog boxes during the install but unsure if they are related.

The /etc/resolv.conf contained:

# Generated by NetworkManager
search lan
nameserver 127.0.0.53

I compared it to a fresh install of 18.04 and this had /etc/resolv.conf as a symlink pointing to /run/systemd/resolve/stub-resolv.conf, so I modified the broken system with these commands.

sudo mv /etc/resolv.conf /etc/resolv.conf.bak
sudo ln -s /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf

But this did not work.

I then found that the broken system had the package resolvconf installed that is not installed on the new 18.04 installation so I removed it with the command:

sudo apt purge resolvconf

After a reboot my networking now works though the /etc/resolv.conf symlink has become a file again containing:

# Generated by NetworkManager
search lan
nameserver 192.168.1.1

The command systemd-resolve --status still fails with the error:
Failed to get global data: Unit dbus-org.freedesktop.resolve1.service not found.

So I suspect this is not a correct fix but more of an accidental workaround.

[Dan Streetman (ddstreet)]

please reopen if this is still an issue

[tomthumb99 (thoffelder)]

Got caught in this error after an autommatic distro update to Ubuntu LTS20. Not going to do that again. (why offer updates that do not work)

The simple command wored for me after a reboot:===> sudo apt purge resolvconf

Ugh they keep making this distro more coomplicated, KISS should be folowed. Folks just want to browse, not fix an OS each time. People going to jump to Chrome-OS it works.