This blog post seems to be a bit incorrect. A distro is affected if the systemd-resolved service is used. It is enabled in Ubuntu but not in Debian. Neither is it in my Fedora system.
Charming. In Debian jessie: Code: $ systemctl status systemd-resolved ● systemd-resolved.service - Network Name Resolution Loaded: loaded (/lib/systemd/system/systemd-resolved.service; disabled) Active: inactive (dead) Docs: man:systemd-resolved.service(8)
Yep, same here in Fedora 25: Code: ● systemd-resolved.service - Network Name Resolution Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; disabled; vendor preset: disabled) Active: inactive (dead) Docs: man:systemd-resolved.service(8) http://www.freedesktop.org/wiki/Software/systemd/resolved http://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers http://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
Arch (Antergos) also unaffected. $ systemctl status systemd-resolved ● systemd-resolved.service - Network Name Resolution Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; disabled; v Active: inactive (dead) Docs: man:systemd-resolved.service( http://www.freedesktop.org/wiki/Software/systemd/resolved http://www.freedesktop.org/wiki/Software/systemd/writing-network-conf http://www.freedesktop.org/wiki/Software/systemd/writing-resolver-cli
The one thing that matters here is - attacker-controlled DNS service. This narrows does the problem. Mrk
Also disabled in Linux Mint 18.1 Cinnamon $ systemctl status systemd-resolved ● systemd-resolved.service - Network Name Resolution Loaded: loaded (/lib/systemd/system/systemd-resolved.service; disabled; vendo Active: inactive (dead) Docs: man:systemd-resolved.service ( 8 ) :
