Clearing the DNS cache on a Linux machine is a straightforward troubleshooting step that resolves a surprising number of connectivity issues. While the operating system manages this database automatically, corrupted or outdated entries can prevent your browser from reaching a website, even when the target server is online. This guide walks you through the exact steps to flush the resolver cache, depending on your specific distribution and setup.
Understanding the DNS Cache Mechanism
Before you execute commands, it helps to understand what is happening behind the scenes. Linux does not rely on a single universal "DNS cache service." Instead, the functionality is usually provided by one of two components: systemd-resolved or a local caching daemon like nscd. When you visit a website, your computer stores the IP address in this temporary memory. This avoids the delay of querying the internet’s root servers every time you load a page. If the TTL (Time To Live) value changes unexpectedly or the cache fails to purge old records, you might find yourself locked in a digital waiting room, unable to reach the correct destination.
Checking Your Current DNS Configuration
It is always wise to inspect the current state of the resolver before making changes. This allows you to confirm whether the cache is the actual culprit. You can query the active statistics to see cache hits and misses without restarting any services. The following commands provide a snapshot of the current health of your DNS resolution layer.
Utilizing resolvectl
If your system uses systemd-resolved, which is standard on Ubuntu, Debian, and recent versions of Fedora, the resolvectl command is your primary tool. Running this command will display the current status, including the number of cached entries.
Reviewing Legacy Services
On older distributions or servers running nscd, you will need to interact with that specific daemon. Checking the status of nscd provides insight into whether the cache daemon is currently active and how much memory it is consuming.
The Standard Flush Command for systemd-resolved
The most common scenario in modern Linux environments involves systemd-resolved. This init system manages the DNS cache and links directly to the operating system’s networking stack. Flushing this cache requires terminal access, but the process is designed to be safe and immediate. You simply notify the daemon to discard all stored records, and it will begin populating the cache with fresh data on the next lookup.
Alternative Methods for Different Daemons
Not every Linux distribution uses systemd-resolved. Some system administrators prefer to run nscd or dnsmasq to handle name resolution. If the standard flush command returns an error or does not seem to work, it is likely because a different service is managing the cache. The good news is that the process is equally simple for these alternative daemons; you merely need to target the correct process name.
Flushing nscd
The Name Service Cache Daemon (nscd) is a veteran in the Linux networking stack. To clear its stored data, you send a specific signal to the daemon instructing it to invalidate its memory. This action forces nscd to query the authoritative DNS server the next time a request arrives.
Flushing dnsmasq
Lightweight routers and custom configurations often rely on dnsmasq. This utility is popular for its simplicity and low resource usage. Flushing the cache here involves touching a specific log file, which triggers the daemon to reload its internal tables. It is a quick operation that yields immediate results.
Verification and Testing
After executing the flush command, you should verify that the cache is clean and resolving correctly. You can check the statistics again to see if the cache count has dropped or if new queries are being processed. Furthermore, attempting to visit a website or ping a hostname confirms that the new DNS records are being fetched properly. This step ensures that the troubleshooting effort was successful and that the issue will not immediately recur.
