systemd-resolved is disabled but is loaded at boot

[cedricmc]

Hi there!

I have disabled systemd-resolved to prevent the DNSSEC problems, however systemd-resolved is loaded at boot. Who is infringing my orders?

$this->bbcode_second_pass_code('', '* systemd-resolved.service - Network Name Resolution
Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; disabled; vendor preset: enabled)
Active: active (running) since Mon 2019-06-17 12:04:08 CEST; 37min 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: 446 (systemd-resolve)
Status: "Processing requests..."
Tasks: 1 (limit: 995)
Memory: 6.3M
CGroup: /system.slice/systemd-resolved.service
`-446 /usr/lib/systemd/systemd-resolved

Jun 17 12:04:08 myrpi systemd-resolved[446]: Positive Trust Anchors:
Jun 17 12:04:08 myrpi systemd-resolved[446]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5
Jun 17 12:04:08 myrpi systemd-resolved[446]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Jun 17 12:04:08 myrpi systemd-resolved[446]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21>
Jun 17 12:04:08 myrpi systemd-resolved[446]: Using system hostname 'myrpi'.
Jun 17 12:04:08 myrpi systemd[1]: Started Network Name Resolution.
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.')

$this->bbcode_second_pass_code('', 'Jun 17 12:04:08 myrpi kernel: audit: type=1130 audit(1560765848.304:13): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=dbus comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jun 17 12:04:07 myrpi audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-timesyncd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jun 17 12:04:08 myrpi audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=dbus comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jun 17 12:04:07 myrpi systemd[1]: Started Network Time Synchronization.
Jun 17 12:04:08 myrpi haveged[447]: haveged: ver: 1.9.4; arch: generic; vend: ; build: (gcc 8.2.0 CTV); collect: 128K
Jun 17 12:04:08 myrpi haveged[447]: haveged: cpu: (VC); data: 16K (D); inst: 16K (D); idx: 11/40; sz: 15528/64688
Jun 17 12:04:08 myrpi haveged[447]: haveged: tot tests(BA8): A:1/1 B:1/1 continuous tests(B): last entropy estimate 7.99816
Jun 17 12:04:08 myrpi haveged[447]: haveged: fills: 0, generated: 0
Jun 17 12:04:07 myrpi systemd[1]: Reached target System Time Set.
Jun 17 12:04:07 myrpi systemd[1]: Reached target System Time Synchronized.
Jun 17 12:04:07 myrpi systemd[1]: Reached target System Initialization.
Jun 17 12:04:07 myrpi systemd[1]: Started Daily rotation of log files.
Jun 17 12:04:07 myrpi systemd[1]: Started Daily verification of password and group files.
Jun 17 12:04:07 myrpi systemd[1]: Started Daily man-db regeneration.
Jun 17 12:04:07 myrpi systemd[1]: Started Daily Cleanup of Temporary Directories.
Jun 17 12:04:07 myrpi systemd[1]: Reached target Timers.
Jun 17 12:04:07 myrpi systemd[1]: Listening on D-Bus System Message Bus Socket.
Jun 17 12:04:07 myrpi systemd[1]: Reached target Sockets.
Jun 17 12:04:08 myrpi systemd[1]: Reached target Basic System.
Jun 17 12:04:08 myrpi systemd[1]: Starting Login Service...
Jun 17 12:04:08 myrpi systemd-networkd[407]: eth0: Gained carrier
Jun 17 12:04:08 myrpi systemd-timesyncd[442]: Network configuration changed, trying to establish connection.
Jun 17 12:04:08 myrpi systemd[1]: Condition check resulted in SSH Key Generation being skipped.
Jun 17 12:04:08 myrpi systemd[1]: Started D-Bus System Message Bus.
Jun 17 12:04:08 myrpi systemd-resolved[446]: Positive Trust Anchors:
Jun 17 12:04:08 myrpi systemd-resolved[446]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5
Jun 17 12:04:08 myrpi systemd-resolved[446]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Jun 17 12:04:08 myrpi systemd-resolved[446]: Negative trust anchors: 10.in-addr.arpa 16.172.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 168.192.in-addr.arpa d.f.ip6.arpa corp home internal intranet lan local private test
Jun 17 12:04:08 myrpi systemd-resolved[446]: Using system hostname 'myrpi'.
Jun 17 12:04:08 myrpi systemd[1]: Started Network Name Resolution.
Jun 17 12:04:08 myrpi audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-resolved comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jun 17 12:04:08 myrpi systemd[1]: Reached target Host and Network Name Lookups.
Jun 17 12:04:08 myrpi kernel: audit: type=1130 audit(1560765848.864:14): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-resolved comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jun 17 12:04:08 myrpi systemd[1]: Starting No-IP Dynamic DNS Update Client...
Jun 17 12:04:08 myrpi systemd[1]: Reached target Network.')

[ufo6000]

"Disable" prevents a unit to start during bootup.
It can still be started by hand or others ways...

"Mask" a unit to make it impossible to start it (both manually and as a dependency, which makes masking dangerous):
https://wiki.archlinux.org/index.php/Sy ... sing_units