systemd-resolve error

brent

I've sat on this 3 weeks thinking an update would fix, but it didn't happen.

$ sudo systemd-resolve --flush-caches
Password:
Failed to flush caches: Unit dbus-org.freedesktop.resolve1.service not found.

I cut and paste this command from Solus Forum, like I do so many, to work into my routine maintenance.
Am I missing a parameter? No emergency here, all operates correctly. Thank you.

ender

Typo ? → systemd-resolved

brent

$ systemd-resolve --help systemd-resolve [OPTIONS...] HOSTNAME|ADDRESS... systemd-resolve [OPTIONS...] --service [[NAME] TYPE] DOMAIN systemd-resolve [OPTIONS...] --openpgp EMAIL@DOMAIN... systemd-resolve [OPTIONS...] --statistics systemd-resolve [OPTIONS...] --reset-statistics .........--flush-caches Flush all local DNS caches

resolve is the command.
resolved is the service.
From my reading, systemd-resolved service appears to be switched off. It can be switched on.
Also, you can configure network not to used systemd-resolved.
Elsewhere I'm reading it's a missing symlink in the etc/.

Is this service being disabled harmful or hurtful in any way I wonder?
Unsure how it got disabled unless default?

ender

brent ooh, TIL, thx. Does switching on the service solve your issue ?

brent

ender $ sudo systemctl enable systemd-resolved.service Password: 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. ~ $ sudo systemd-resolve --flush-caches ~ $

See that bottom dollar sign? That means I got no verbose confirmation that it happened (there is no --verbose command in systemd-resolve that I could see.) but I'm sure it's enabled.

I'd say it's resolved.
Any reason it was disabled? Or what does systemd-resolved service do?
Unless anybody else chimes in I will find this out on my own somehow.

Really appreciate your help, ender , thanks

ender

well didn't help much 😀, glad it pointed you in the right direction though.
To my understanding, the Solus team tends to enable as few service as needed. Since dns resolution is working fine without this particular service it would make sense they didn't use it by default. Guess it means we don't have dns cache by default, which would be a sensible set up to me.

If you want to use systemd-resolved, I think you have to enable it in the network manager configuration:

[main]
dns=systemd-resolved

See man 5 NetworkManager.conf

brent

ender I'm reading about this service and many of my google entries mention this service as a vulnerability to bad guys and leave it disabled. Of course there is a "2017" affixed to most of these anti-resolved articles so that notion might be dated.
I am going to disable back to the way it was.

Gracia, again, and thanks for that info.

Mods: SOLVED