Managing a Linux server often requires troubleshooting network issues, and one of the most common tasks is clearing cached DNS data. When applications fail to resolve domain names correctly, the flush dns command linux becomes an essential tool for system administrators. This operation forces the operating system to discard old records and request fresh information from DNS servers, resolving connectivity surprises caused by outdated entries.
Understanding DNS Caching on Linux
Before executing the flush command, it is important to understand how DNS caching works on Linux. Unlike desktop operating systems, most Linux distributions do not enable a caching service by default; instead, they rely on a local daemon that forwards queries to upstream servers. The cache is often managed by systemd-resolved, nscd, or dnsmasq, depending on the distribution and configuration. When you modify DNS records or experience server migrations, these cached entries can cause the system to point to obsolete IP addresses.
Identifying Your DNS Resolver
Because the method varies between distributions, you must first identify which service is handling name resolution. Modern systems using systemd utilize the resolvectl command to interact with systemd-resolved. If the output shows that systemd-resolved is active, you will use a specific syntax to flush the cache. Alternatively, if you are running nscd or dnsmasq, the terminal commands differ slightly. Determining the active service ensures you target the correct cache and avoid unnecessary restarts of the wrong daemon.
Using resolvectl to Clear Cache
For systems running systemd version 229 or later, the flush dns command linux is simplified through resolvectl. The command sudo resolvectl flush-caches is non-destructive and immediately clears all cached entries without disrupting active connections. This is the recommended method for Ubuntu 20.04, CentOS 8, and other systemd-centric distributions. After execution, you can verify the cache statistics with resolvectl statistics to confirm that the hit rate has reset.
Commands for nscd and dnsmasq
If your environment relies on Name Service Cache Daemon (nscd), you must restart the daemon to purge the cache. The command sudo /etc/init.d/nscd restart or sudo systemctl restart nscd achieves this, though it also restarts the service rather than just clearing memory. For setups using dnsmasq, the process often involves restarting the daemon with sudo systemctl restart dnsmasq. While these methods are effective, they are heavier operations compared to the targeted flush provided by systemd-resolved.
Validating the Flush Operation
After performing the flush dns command linux, validation is necessary to ensure the issue is resolved. You can use standard networking tools like dig or host to query the DNS records directly from the server. Comparing the TTL (Time To Live) values before and after the flush confirms that the old data is gone. Monitoring application logs immediately following the flush provides final confirmation that the connectivity problems were caused by stale cache entries.
Automating Cache Management
In complex infrastructures, manually flushing the cache on multiple servers is inefficient. Savvy administrators script the flush dns command linux using SSH to execute the commands remotely across the fleet. Combining the cache clear with a service restart script ensures consistency after known DNS changes. These scripts are often triggered by deployment pipelines or configuration management tools like Ansible to maintain network integrity without manual intervention.
Best Practices and Caveats
While the flush operation is safe, it should not be a daily routine, as frequent cache clearing adds load to upstream DNS servers. Ensure your resolvers are configured to reliable upstream providers to avoid performance degradation. Additionally, be aware that short TTL records are designed to expire quickly; if you are not facing resolution issues, allowing the system to refresh naturally might be more efficient than forcing a flush.
