Clearing the DNS cache in Windows 11 removes locally cached hostname lookups. It can help when a website or server recently changed addresses, but it does not clear browser cookies, fix a broken Internet connection, or change your DNS provider.
Flush the Windows DNS resolver cache
Open Command Prompt or Windows Terminal with appropriate permissions and run ipconfig /flushdns. Windows should report that the DNS Resolver Cache was successfully flushed.
Retry the hostname
Close and reopen the affected application or browser tab, then try the site or network resource again. Windows will request fresh DNS information as needed.
Browsers can maintain additional DNS state
Modern browsers may use secure DNS, connection pools, or their own caches. If only one browser is affected, restart it and review its DNS/privacy settings rather than repeatedly flushing Windows.
Check the actual DNS path if the problem continues
Use nslookup or PowerShell DNS tools to see whether the hostname resolves. VPNs, router DNS, corporate filtering, DNS-over-HTTPS, and provider outages can all affect results.
Do not change to an unknown public DNS server merely because flushing did not help. Use a trusted resolver appropriate for your network and follow organization policy on managed PCs.
Restarting the router is not the same operation
The Windows DNS cache belongs to the PC, while a router or local DNS server can maintain its own cache. If several devices resolve the same hostname incorrectly, investigate the shared DNS source rather than flushing every computer repeatedly.
Kermit Matthews is a freelance writer based in Philadelphia, Pennsylvania with more than a decade of experience writing technology guides. He has a Bachelor’s and Master’s degree in Computer Science and has spent much of his professional career in IT management.
He specializes in writing content about iPhones, Android devices, Microsoft Office, and many other popular applications and devices.