What Is systemd-resolved? Is It Safe to Disable at Startup?
systemd-resolved is Linux's DNS resolver service. It is normally safe and should usually stay enabled for name lookups and network features.
- Verdict
- Keep runningIt is a core DNS service on many Linux systems and disabling it can break name resolution and network-dependent apps.
- File name
- systemd-resolved
- Publisher
- systemd project
- Platforms
- Linux
- Reviewed
What Is systemd-resolved?
systemd-resolved is the DNS resolver service used by many Linux distributions that run systemd. Its job is to turn names like example.com into IP addresses, cache DNS answers, and provide local name resolution features for apps and the OS.
On some systems it also manages /etc/resolv.conf through a local stub resolver, often using 127.0.0.53. That is normal on distributions that use it by default.
Is It Safe?
Yes, systemd-resolved from the systemd project is a legitimate system service. It is a normal part of many Linux installs and is not something most people should treat as suspicious.
Because it is a system component, the main check is whether it came from your distribution's packages. If you want to verify it, check which package owns the binary with your package manager and inspect the service with systemctl status systemd-resolved. A copy of systemd-resolved running from an unusual location outside normal system paths would be worth investigating.
Should I Disable It at Startup?
Usually no. Keep it enabled unless you know your system uses a different DNS setup and you are comfortable reconfiguring networking yourself.
Disabling systemd-resolved can cause DNS failures, broken web browsing, package manager errors, VPN issues, or apps that cannot connect by hostname. Some distributions integrate it with NetworkManager or other network tools, so turning it off may have side effects beyond simple DNS caching.
If you intentionally use another resolver such as a custom local DNS service, disabling systemd-resolved may be fine, but only after confirming how your distro expects /etc/resolv.conf and network services to be configured.
Why Is It Using High CPU or Memory?
Short bursts of activity are normal when apps make many DNS requests. Constant high usage is not typical.
Common causes include:
- a misbehaving app making repeated DNS lookups
- DNS server timeouts or a bad network connection
- a VPN, proxy, or firewall causing resolver retries
- broken multicast or local name resolution on the network
- resolver loops caused by incorrect DNS configuration
Start by checking logs with journalctl -u systemd-resolved and current status with resolvectl status. If usage stays high, test whether the problem is network-related by disconnecting VPN software, changing DNS servers, or checking which app is generating requests.
How to Disable or Remove It
Only do this if you understand your distro's DNS setup.
To stop it temporarily:
sudo systemctl stop systemd-resolvedTo disable it at boot:
sudo systemctl disable systemd-resolvedOn some systems you may also need to replace or reconfigure /etc/resolv.conf so DNS still works. The exact steps vary by distribution, so use your distro's documentation rather than guessing.
Do not remove core systemd packages casually. If your goal is troubleshooting, disable the service temporarily first and confirm that an alternative resolver is working.
Where Kudu Helps
Kudu can show if another app is causing heavy CPU or memory use while systemd-resolved is active, and it can help you spot startup entries that launch VPNs, proxies, or network tools tied to DNS problems. On Linux, Kudu's Startup Manager can review XDG autostart apps, while Performance Monitor helps identify which processes are active when DNS issues appear.
Kudu is not a replacement for your distro's service manager, but it is useful for tracing related user-level startup items and checking whether high resource use starts with another app.
Frequently asked questions
- Is systemd-resolved a virus?
- No, not when it is the normal Linux service provided by your distribution. If you see a similarly named process from an unusual location, investigate it.
- What happens if I disable systemd-resolved?
- DNS may stop working, which can break web browsing, updates, package installs, and apps that connect by hostname. Only disable it if you have another resolver configured correctly.
- Why is /etc/resolv.conf pointing to 127.0.0.53?
- That usually means systemd-resolved is providing a local DNS stub resolver. On systems that use it by default, this is normal.
See every app that starts with your computer
Kudu’s Startup Manager lists Run keys, Startup folder entries, scheduled tasks, Launch Agents, and XDG autostart items in one place. On Windows it also shows each item’s boot time impact.
Download Kudu Free →