Flush a local DNS cache when evidence points to an outdated cached answer on that device. It does not change authoritative DNS records, clear every upstream resolver, or guarantee faster browsing. First compare the failing hostname with the expected record and determine which resolver the device or application actually uses.
Separate the layers before clearing anything
Record the hostname, observed address, expected address, configured resolver and time of the check. A recently changed record can remain cached until its TTL expires. Browser DNS-over-HTTPS, VPNs and network resolvers may use different paths from the operating system. A hosts-file override is not a DNS-cache entry.
If the authoritative record itself is wrong, correct it with the DNS operator. If multiple devices receive the same old answer from an upstream resolver, clearing one local cache will not remove that upstream copy.
Windows DNS client cache
In an authorized Command Prompt, inspect the client cache and flush it if appropriate:
ipconfig /displaydns
ipconfig /flushdnsRun with the permissions required by your system. Microsoft documents these options for the Windows DNS client cache. Retry the original lookup and application afterward; a success message alone does not establish that the original fault is resolved.
Linux with systemd-resolved
Linux has no universal DNS-cache service. On a system actually using systemd-resolved, inspect resolver configuration, then clear its cache:
resolvectl status
sudo resolvectl flush-caches
resolvectl query example.comReplace example.com with the hostname being investigated. The Ubuntu resolvectl manual describes this service-specific operation. If the command or service is absent, identify the active resolver; do not restart an unrelated service such as nscd just because an older tutorial used it.
macOS and Android
Use the instructions for the exact operating-system release and resolver involved. On macOS, consult the installed man dscacheutil documentation before using its cache operations; its flush option affects the broader Directory Service cache and is not a universal verification that every DNS layer was cleared.
Changing Android from DHCP to a static IP and entering another DNS service is not a cache-flush procedure. It changes network configuration and can break connectivity. Check the device's Private DNS, VPN and browser resolver settings instead of copying arbitrary static-address instructions.
Verify the result
Repeat the same lookup through the same resolver and then retry the affected application. If the answer is now correct but the website still fails, investigate TLS, routing or application errors rather than repeatedly flushing DNS. Preserve the before-and-after result for your DNS or hosting support team. WebCare360 is the hosting provider publishing this troubleshooting guide.
