Configure network-manager To Not Use systemd-resolved.service

Configure network-manager To Not Use systemd-resolved.service

Reason : activation via systemd failed for unit ‘dbus-org.freedesktop.resolve1.service’: Unit dbus-org.freedesktop.resolve1.service not found.

Solution

sudo nano /etc/NetworkManager/conf.d/no-systemd-resolved.conf

With this content :

[main]
systemd-resolved=false

Activate and use systemd-resolved.service

Check if it is running and enabled.

systemctl status systemd-resolved.service
● systemd-resolved.service - Network Name Resolution
  Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; disabled; vendor preset: enabled)
  Active: inactive (dead)
    Docs: man:systemd-resolved.service(8)
          https://www.freedesktop.org/wiki/Software/systemd/resolved
          https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
          https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients

Enable and start it.

systemctl enable systemd-resolved.service
Created symlink /etc/systemd/system/dbus-org.freedesktop.resolve1.service → /usr/lib/systemd/system/systemd-resolved.service.
Created symlink /etc/systemd/system/multi-user.target.wants/systemd-resolved.service → /usr/lib/systemd/system/systemd-resolved.service.
systemctl start systemd-resolved.service
systemctl status systemd-resolved.service
● systemd-resolved.service - Network Name Resolution
  Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled)
  Active: active (running) since Fri 2019-04-19 10:36:53 SAST; 32min ago
    Docs: man:systemd-resolved.service(8)
          https://www.freedesktop.org/wiki/Software/systemd/resolved
          https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
          https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
Main PID: 21150 (systemd-resolve)
  Status: "Processing requests..."
    Tasks: 1 (limit: 4915)
  Memory: 5.0M
  CGroup: /system.slice/systemd-resolved.service
          └─21150 /usr/lib/systemd/systemd-resolved

That solved the errors from coming up in the logs.