How to Clear DNS Cache in Chrome: Multiple Methods You Can Try

If you have been experiencing problems like websites not loading, pages displaying older versions, or random “DNS error” messages, one of the easiest and most helpful maintenance tasks is flushing your DNS cache.  

Chrome has a little-known internal tool, chrome://net-internals/#dns, which can be used for immediately flushing the DNS entries. Most end users key incorrectly as “chorme //net-internals/#dns”, which doesn’t work. 

What Is a DNS Cache, and Why Clear It? 

DNS stands for Domain Name System. It converts human-friendly URLs-for example, facebook.com-to numerical IP addresses, such as 157.240.3.35. 

The internet would not work without DNS. 

What is DNS cache? 

Your browser and computer cache DNS results temporarily to speed up repeated visits. This stored record is called the DNS cache. Why DNS Cache Becomes a Problem DNS cache can fail under the following circumstances: 

• Changing servers on a website 

• The IP addresses of a domain change Your ISP updates DNS routing  

• When a website blocks or redirects old DNS paths 

• Malware modifies DNS entries 

• Your browser keeps outdated versions of pages 

You might see: 

• “DNS_PROBE_FINISHED_NXDOMAIN” 

• “This site can’t be reached” 

• Weird redirect loops 

• SSL certificate mismatches 

• Only some pages loading, others fail to load 

Clearing the DNS cache resolves all these in an instant, and the quickest way is to use chrome //net-internals/#dns. 

Some people start typing in chorme //net-internals/#dns, but Chrome only recognizes the proper address. 

Method 1: Clear DNS Cache Inside Chrome 

The fastest, most Chrome-specific way to solve browser-only DNS issues involves using chrome://net-internals/#dns. 

Where to Access It 

Type this in Chrome’s address bar: chrome://net-internals/#dns 

Note: chorme //net-internals/#dns will not work — this is a common typo users make. 

Steps by Step  

1. Open Chrome. 

2. Copy and paste: chrome://net-internals/#dns 

3. Press Enter. 

4. You will be taken to Chrome’s internal DNS page. 

5. Click “Clear host cache”. 

What This Actually Does? 

It resets: 

• Chrome’s DNS cache 

• Internal DNS prefetch results 

• DNS lookups that have been temporarily cached 

• Host resolver tables 

Think of it as refreshing Chrome’s memory of the whole internet. 

Who Should Consider This Approach? 

Ideally, this method works when: 

• The issue only occurs in your Chrome browser 

• Other browsers work fine 

• Issue instantly appears once DNS servers are switched 

• A website updated but Chrome shows the old version 

• You see login-related looping errors 

Note that this is a browser-only fix and does not affect system-wide DNS cache. 

Method 2: Clear DNS Cache on Windows 

Even when using chrome //net-internals/#dns, your computer’s DNS cache may still be old or corrupted. 

Windows keeps a huge DNS database systemwide. Clearing that assures all browsers and apps get fresh DNS entries. 

Steps for Windows 10 / Windows 11 

1. Press Win + R. 

2. Type cmd and press Enter. 

3. Type the following command: ipconfig /flushdns 

4. Press Enter. 

5. You should see: 

Successfully flushed the DNS Resolver Cache. 

What This Fixes 

• Discord connectivity issues 

• DNS issues with Chrome + Firefox + Edge 

• Slow loading sites 

• Network changes not taking effect. 

• DNS-based game server issues 

• ISP-level DNS conflicts 

Pro Tip 

Restart computer AND router after clearing DNS for best results. 

Method 3: Clear DNS Cache on macOS 

While Windows handles DNS caching one way, macOS does it another. The flushing procedure is also different, depending on the version. For 2025 versions-Monterey, Ventura, Sonoma-it is the same command: 

Steps for Modern macOS Versions 

1. Open Terminal. 

2. Type: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder 

3. Type your admin password. 

4. macOS refreshes DNS without displaying any confirmation message. 

When You Should Clear DNS on Mac 

• Safari and Chrome load different versions of a website 

• DNS errors after network switch 

• Your Mac always redirects to the wrong website version 

• Sites using a CDN look dated. 

• SSL errors on updated sites 

Method 4: Use Chrome Settings Reset 

If DNS is not resolved after flushing using chrome //net-internals/#dns, it’s possible that the settings of Chrome are corrupt. 

Resetting Chrome may fix 

• Corrupted profiles 

• Bad Chrome flags 

• Incorrect proxy settings 

• Extensions that interfere with DNS 

• Chrome prefetch and loader issues 

Steps to follow  

1. Open Chrome Settings. 

2. Scroll to Reset and Clean Up. 

3. Click Restore settings to their original defaults. 

4. Check 

What Happens When You Reset Chrome? 

It resets: 

• Startup pages 

• New tab settings 

• Cookies 

• Prefetch settings 

• Cached settings 

It does not delete: 

• Bookmarks 

• Passwords 

• History 

• Extensions: They remain installed but are disabled. 

This is your last-resort Chrome-only fix after using chrome://net-internals/#dns. 

Advanced DNS Fixes (Optional but Helpful) 

Following are some more methods concerning deeper network-related DNS issues. 

1. Change Your DNS Provider 

Sometimes it is your ISP’s DNS server that is the problem. Switch to a faster public DNS: 

• Google DNS 

• 8.8.8.8 

• 8.8.4.4 

• Cloudflare DNS (Fastest for most users) 

• 1.1.1.1 

• 1.0.0.1  

• OpenDNS  

• 208.67.222.222  

• 208.67.220.220  

You may need to revisit chrome://net-internals/#dns after a DNS server switch in order to clear old entries. 

2. Clear Chrome’s Internal Cache  

Go to:  

chrome://settings/clearBrowserData  

Clear:  

• Cached images and files  

• Cookies  

• Site data  

• Data for hosted applications  

This deletes old CDN assets.  

3. Disable DNS Prefetching – Temporary Fix  

Sometimes it’s the DNS prefetch system of Chrome.  

• Go to chrome://settings  

• Search for prefetch  

• Deselect Preload pages  

Then use chrome //net-internals/#dns again.  

Troubleshooting: Why Doesn’t chrome://net-internals/#dns Work?  

Some users report that typing chrome://net-internals/#dns loads a minimal page or doesn’t show the DNS panel. Reasons:  

1. Older Version of Chrome  

Update Chrome to version 115+.  

2. Using the Wrong URL  

Common mistakes:  

• chorme //net-internals/#dns  

• chrome://net-internals/#dns  

• chrome:/net-internals  

• chrome:net-internals/#dns  

Only this is correct: ` chrome://net-internals/#dns 

3. Profile Corruption 

Try using Chrome Guest mode.  

4. Interference by Malware  

DNS hijackers may block the DNS panel. 

Clearing DNS Cache 

One of the easiest ways to fix half of the browsing issues you go through each day is the clearing of DNS.  

Be it a website that refuses to load, redirects inappropriately, or shows outdated content; tools like chrome //net-internals/#dns refresh your browser instantly.  

In sum:  

• Chrome DNS = use chrome://net-internals/#dns  

• Windows DNS = use ipconfig /flushdns  

• Mac DNS = use Terminal flush commands  

• Chrome issues = reset settings  

• System-wide issues = restart router + change DNS provider  

Repeating your keyword one last time: While many people make the mistake of typing “chorme //net-internals/#dns”, only the right chrome //net-internals/#dns address will actually open the DNS flush tool.