Skip to content

systemd resolved is cancer

Jump to bottom
Phil Jaenke edited this page Mar 21, 2021 · 1 revision

YOU MUST PERMANENTLY DELETE SYSTEMD-RESOLVED

SYSTEMD-RESOLVED CREATES SIGNIFICANT SECURITY RISKS AND IS KNOWN TO ACTIVELY BREAK DNS. DO NOT RUN SYSTEMD-RESOLVED PERIOD. DO NOT PERMIT IT ON YOUR SYSTEMS. DO NOT PERMIT IT IN YOUR NETWORK.

systemdctl stop systemd-resolved
systemdctl mask systemd-resolved
rm -f /etc/resolv.conf
vi /etc/resolv.conf
ln -sf /dev/null /usr/lib/systemd/systemd-resolved
ln -sf /dev/null /usr/lib/systemd/system/systemd-resolved.service

YOU MUST PERMANENTLY DELETE SYSTEMD-RESOLVED

SYSTEMD-RESOLVED CREATES SIGNIFICANT SECURITY RISKS AND IS KNOWN TO ACTIVELY BREAK DNS. DO NOT RUN SYSTEMD-RESOLVED PERIOD. DO NOT PERMIT IT ON YOUR SYSTEMS. DO NOT PERMIT IT IN YOUR NETWORK.

systemdctl stop systemd-resolved
systemdctl mask systemd-resolved
rm -f /etc/resolv.conf
vi /etc/resolv.conf
ln -sf /dev/null /usr/lib/systemd/systemd-resolved
ln -sf /dev/null /usr/lib/systemd/system/systemd-resolved.service

YOU MUST PERMANENTLY DELETE SYSTEMD-RESOLVED

SYSTEMD-RESOLVED CREATES SIGNIFICANT SECURITY RISKS AND IS KNOWN TO ACTIVELY BREAK DNS. DO NOT RUN SYSTEMD-RESOLVED PERIOD. DO NOT PERMIT IT ON YOUR SYSTEMS. DO NOT PERMIT IT IN YOUR NETWORK.

systemdctl stop systemd-resolved
systemdctl mask systemd-resolved
rm -f /etc/resolv.conf
vi /etc/resolv.conf
ln -sf /dev/null /usr/lib/systemd/systemd-resolved
ln -sf /dev/null /usr/lib/systemd/system/systemd-resolved.service

YOU MUST PERMANENTLY DELETE SYSTEMD-RESOLVED

SYSTEMD-RESOLVED CREATES SIGNIFICANT SECURITY RISKS AND IS KNOWN TO ACTIVELY BREAK DNS. DO NOT RUN SYSTEMD-RESOLVED PERIOD. DO NOT PERMIT IT ON YOUR SYSTEMS. DO NOT PERMIT IT IN YOUR NETWORK.

systemdctl stop systemd-resolved
systemdctl mask systemd-resolved
rm -f /etc/resolv.conf
vi /etc/resolv.conf
ln -sf /dev/null /usr/lib/systemd/systemd-resolved
ln -sf /dev/null /usr/lib/systemd/system/systemd-resolved.service

YOU MUST PERMANENTLY DELETE SYSTEMD-RESOLVED

SYSTEMD-RESOLVED CREATES SIGNIFICANT SECURITY RISKS AND IS KNOWN TO ACTIVELY BREAK DNS. DO NOT RUN SYSTEMD-RESOLVED PERIOD. DO NOT PERMIT IT ON YOUR SYSTEMS. DO NOT PERMIT IT IN YOUR NETWORK.

systemdctl stop systemd-resolved
systemdctl mask systemd-resolved
rm -f /etc/resolv.conf
vi /etc/resolv.conf
ln -sf /dev/null /usr/lib/systemd/systemd-resolved
ln -sf /dev/null /usr/lib/systemd/system/systemd-resolved.service

Kris, it doesn't always have to be a fscking DNS problem... :-) Enjoy! -Jan-Piet

Clone this wiki locally