Fixing systemd-resolved Conflicts With Manually Configured DNS
Why editing /etc/resolv.conf directly often silently fails to change actual DNS behavior on systemd-resolved systems, and the correct way to override DNS settings that actually persists.
tag
4 posts
Why editing /etc/resolv.conf directly often silently fails to change actual DNS behavior on systemd-resolved systems, and the correct way to override DNS settings that actually persists.
Working through the DNS client cache, adapter-specific resolver settings, and the actual configured servers systematically, instead of jumping straight to reinstalling network drivers.
Ping works, but domain names won't resolve inside WSL2 — or the reverse. Here's how to actually diagnose whether the problem is DNS configuration, VPN interference, or the networking mode itself.
Ping by IP works but hostnames don't resolve. Here's a systematic path through resolv.conf, systemd-resolved, and nsswitch.conf to find where resolution is actually breaking.