{"id":11337,"date":"2025-04-27T10:44:48","date_gmt":"2025-04-27T04:59:48","guid":{"rendered":"https:\/\/nestnepal.com\/blog\/?p=11337"},"modified":"2025-05-23T14:08:04","modified_gmt":"2025-05-23T08:23:04","slug":"how-to-clear-dns-cache-on-your-computer-guide","status":"publish","type":"post","link":"https:\/\/nestnepal.com\/blog\/how-to-clear-dns-cache-on-your-computer-guide\/","title":{"rendered":"How to Clear DNS Cache on Your Computer (Flush DNS Guide for Developers)"},"content":{"rendered":"

Introduction<\/strong><\/h1>\n

\"clear-DNS-cache\"<\/p>\n

Clearing your DNS<\/a> cache is a must-know move, whether you’re building a new website, switching environments, or just troubleshooting connectivity issues. <\/span>DNS cache<\/strong> issues can cause delays, errors, or outdated websites to load. Knowing how to clear DNS cache<\/strong> or flush DNS<\/strong> is crucial for developers. Think of it like hitting refresh on your browser. But for your system’s internal phonebook. In this updated guide, we go all-in on clearing DNS caches across Windows, macOS, Linux, and browsers like Chrome<\/a> and Firefox. We’ve also added dev-friendly tips like automation, aliases, and scripts so you can streamline your workflow.<\/p>\n

Whether you’re building a new website, switching environments, troubleshooting a DNS resolver, or dealing with DNS cache issues, this guide will help. Flushing the DNS cache updates the Domain Name System (DNS) records your computer stores, ensuring faster, more reliable browsing.<\/p>\n

What is the DNS Cache?<\/span><\/h2>\n

Your computer stores DNS (Domain Name System) data locally to quickly resolve domain names<\/a> to IP addresses. While this speeds up web browsing, it can be a nightmare during website updates or DNS propagation. If you’re seeing outdated or incorrect website versions, your DNS cache might be the culprit.<\/span><\/p>\n

How to Clear DNS Cache on Windows<\/span><\/h2>\n
    \n
  1. Press `Windows + R`, type `cmd`, then press Enter.<\/span><\/li>\n
  2. In the Command Prompt, run:<\/span><\/li>\n<\/ol>\n

    \u00a0\u00a0\u00a0“`cmd<\/span><\/p>\n

    \u00a0\u00a0\u00a0ipconfig \/flushdns<\/span><\/p>\n

    \u00a0\u00a0\u00a0“`<\/span><\/p>\n

      \n
    1. You\u2019ll see a confirmation: `Successfully flushed the DNS Resolver Cache.`<\/span><\/li>\n
    2. (Optional) Restart your browser or system for full effect.<\/span><\/li>\n<\/ol>\n

       <\/p>\n

      Pro Tip:<\/b> Create a `.bat` file for easy flushing:<\/span><\/p>\n

      “`bat<\/span><\/p>\n

      @echo off<\/span><\/p>\n

      ipconfig \/flushdns<\/span><\/p>\n

      echo DNS Cache Cleared \u2705<\/span><\/p>\n

      pause<\/span><\/p>\n

      “`<\/span><\/p>\n

      How to Clear DNS Cache on macOS<\/span><\/h2>\n

      Open the Terminal from `Applications > Utilities > Terminal`.<\/span><\/p>\n

       <\/p>\n

      For macOS Ventura, Monterey, Big Sur, or later<\/b>:<\/span><\/p>\n

      “`bash<\/span><\/p>\n

      sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder<\/span><\/p>\n

      “`<\/span><\/p>\n

      For older versions:<\/b><\/p>\n

      “`bash<\/span><\/p>\n

      # <\/span>Yosemite (10.10.4+) and Mavericks<\/b><\/p>\n

      sudo killall -HUP mDNSResponder<\/span><\/p>\n

       <\/p>\n

      #<\/span> Yosemite (10.10.0 – 10.10.3)<\/b><\/p>\n

      sudo discoveryutil mdnsflushcache<\/span><\/p>\n

       <\/p>\n

      # <\/span>Snow Leopard<\/b><\/p>\n

      sudo dscacheutil -flushcache<\/span><\/p>\n

      “`<\/span><\/p>\n

       <\/p>\n

      \u2705 <\/span>Alias this command<\/b> in `.zshrc` or `.bash_profile`:<\/span><\/p>\n

      “`bash<\/span><\/p>\n

      alias flushdns=”sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder && echo ‘DNS Cache Cleared \u2705'”<\/span><\/p>\n

      “`<\/span><\/p>\n

      \ud83d\udc27 How to Clear DNS Cache on Linux<\/span><\/h2>\n

      Linux doesn’t cache DNS by default, but if it does, it’s via a resolver like `systemd-resolved`, `dnsmasq`, `nscd`, or `BIND`. Here’s how to flush them:<\/span><\/p>\n

      \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/span>Find your resolver:<\/b><\/p>\n

      “`bash<\/span><\/p>\n

      sudo lsof -i :53 -S<\/span><\/p>\n

      “`<\/span><\/p>\n

      \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/span>Based on the resolver:<\/b><\/p>\n

      After identifying your DNS resolver, it’s important to flush DNS<\/strong> to ensure changes take effect.<\/p>\n

      systemd-resolved<\/b>:<\/span><\/p>\n

      “`bash<\/span><\/p>\n

      sudo resolvectl flush-caches<\/span><\/p>\n

      “`<\/span><\/p>\n

      dnsmasq:<\/b><\/p>\n

      “`bash<\/span><\/p>\n

      sudo systemctl restart dnsmasq<\/span><\/p>\n

      “`<\/span><\/p>\n

      nscd:<\/b><\/p>\n

      “`bash<\/span><\/p>\n

      sudo nscd -i hosts<\/span><\/p>\n

      “`<\/span><\/p>\n

      BIND:<\/b><\/p>\n

      “`bash<\/span><\/p>\n

      sudo rndc flush<\/span><\/p>\n

      “`<\/span><\/p>\n

      \u2705 <\/span>Alias example (for systemd-resolved)<\/b>:<\/span><\/p>\n

      “`bash<\/span><\/p>\n

      alias flushdns=”sudo resolvectl flush-caches && echo ‘DNS Cache Flushed \u2705'”<\/span><\/p>\n

      “`<\/span><\/p>\n

      How to Clear DNS Cache in Web Browsers<\/span><\/h2>\n
      \"dns-chrome\"
      3DiconsMediaApps-04<\/figcaption><\/figure>\n

      \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Google Chrome \/ Chromium<\/span><\/h3>\n
        \n
      1. Open Chrome and enter:<\/span><\/li>\n<\/ol>\n

        \u00a0\u00a0\u00a0“`<\/span><\/p>\n

        \u00a0\u00a0\u00a0chrome:\/\/net-internals\/#dns<\/span><\/p>\n

        \u00a0\u00a0\u00a0“`<\/span><\/p>\n

          \n
        1. Click <\/span>Clear host cache<\/i><\/b>.<\/span><\/li>\n
        2. Then go to:<\/span><\/li>\n<\/ol>\n

          \u00a0\u00a0\u00a0“`<\/span><\/p>\n

          \u00a0\u00a0\u00a0chrome:\/\/net-internals\/#sockets<\/span><\/p>\n

          \u00a0\u00a0\u00a0“`<\/span><\/p>\n

            \n
          1. Click <\/span>Close idle sockets<\/i><\/b> and <\/span>Flush socket pools<\/i><\/b>.<\/span><\/li>\n
          2. Restart the browser.<\/span><\/li>\n<\/ol>\n

             <\/p>\n

            \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Mozilla Firefox<\/span><\/h3>\n
              \n
            1. Open Firefox and visit:<\/span><\/li>\n<\/ol>\n

              \u00a0\u00a0\u00a0“`<\/span><\/p>\n

              \u00a0\u00a0\u00a0about: networking#dns<\/span><\/p>\n

              \u00a0\u00a0\u00a0“`<\/span><\/p>\n

                \n
              1. Click <\/span>Clear DNS Cache<\/b>.<\/span><\/li>\n
              2. Restart the browser.<\/span><\/li>\n<\/ol>\n

                Automate DNS Flushing in Dev Workflows<\/span><\/h2>\n

                Add the flush command to a <\/span>bash alias<\/b>, or include it in your <\/span>build\/deploy script<\/b> to ensure you\u2019re never debugging with stale DNS data.<\/span><\/p>\n

                \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Bash Alias Example (macOS\/Linux):<\/span><\/h3>\n

                “`bash<\/span><\/p>\n

                alias flushdns=”sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder && echo ‘DNS Cache Cleared \u2705'”<\/span><\/p>\n

                “`<\/span><\/p>\n

                \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Hook into a Dev Script:<\/span><\/h3>\n

                “`bash<\/span><\/p>\n

                #!\/bin\/bash<\/span><\/p>\n

                flushdns() {<\/span><\/p>\n

                \u00a0\u00a0sudo dscacheutil -flushcache<\/span><\/p>\n

                \u00a0\u00a0sudo killall -HUP mDNSResponder<\/span><\/p>\n

                \u00a0\u00a0echo “DNS Cache Cleared During Deployment \u2705”<\/span><\/p>\n

                }<\/span><\/p>\n

                # Call the function as part of the deployment<\/span><\/p>\n

                flushdns<\/span><\/p>\n

                “`<\/span><\/p>\n

                FAQs:<\/span><\/h2>\n

                1. What is DNS cache, and why should I clear it?<\/h3>\n

                The DNS cache stores IP addresses from the Domain Name System (DNS) to speed up browsing. Clearing it removes outdated records and fixes DNS resolver errors.<\/p>\n

                2. How do I flush DNS cache on Windows?<\/h3>\n

                Open Command Prompt (Win + R, type cmd) and run:<\/p>\n

                ipconfig \/flushdns<\/em><\/p>\n

                You\u2019ll see: Successfully flushed the DNS Resolver Cache. <\/em>Restart your browser for full effect.<\/p>\n

                3. How do I flush DNS on a Mac?<\/h3>\n

                Open Terminal and run:<\/p>\n

                sudo dscacheutil\u00a0 -flushcache; sudo killall\u00a0 -HUP mDNSResponder<\/em><\/p>\n

                This works on Ventura, Monterey, Big Sur, and later. Older macOS versions require different commands listed in the guide.<\/p>\n

                4. Does Linux store DNS cache?<\/h3>\n

                Linux typically doesn\u2019t cache DNS unless you’re using a resolver like [systemd-resolved, dnsmasq, nscd,<\/strong> or BIND]<\/strong>. Check your active service with:<\/p>\n

                sudo lsof\u00a0 -i :53\u00a0 -S<\/em>
                \nThen, flush the appropriate cache using the matching commands.<\/p>\n

                5. How do I clear DNS cache in Chrome?<\/h3>\n

                Flushing DNS within Chrome ensures the browser doesn’t hold onto outdated DNS resolver data.<\/p>\n

                  \n
                • Go to:<\/li>\n<\/ul>\n

                  chrome:\/\/net-internals\/#dns<\/em><\/p>\n

                    \n
                  • Click Clear host cache, then go to:<\/li>\n<\/ul>\n

                    chrome:\/\/net-internals\/#sockets<\/em><\/p>\n

                    Click Close idle sockets and Flush socket pools. Restart the browser.<\/p>\n

                    6. How do I clear DNS cache in Firefox?<\/h3>\n

                    Open Firefox and navigate to:<\/p>\n

                    arduino<\/strong>
                    \nabout: networking#dns<\/em><\/p>\n

                    Click Clear DNS Cache and restart the browser to ensure changes take effect.<\/p>\n

                    7. Can I automate DNS flushing?<\/h3>\n

                    Yes! You can create aliases or include flush commands in your deployment scripts. This is useful for developers working with staging environments or switching DNS records often.<\/p>\n

                    Example alias for macOS\/Linux:<\/p>\n

                    alias flushdns=”sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder”<\/em><\/p>\n

                    8. How often should I clear my DNS cache?<\/h3>\n

                    There\u2019s no fixed rule, but clear it whenever:<\/p>\n

                      \n
                    • You change DNS settings or switch environments<\/li>\n
                    • You see outdated pages or connection errors<\/li>\n
                    • You deploy a site with updated domains<\/li>\n<\/ul>\n

                      9. Is it safe to flush the DNS cache?<\/h3>\n

                      Yes! Clearing your DNS cache is completely safe. It won\u2019t affect your files or installed software. It simply resets the list of domain-to-IP lookups stored locally.<\/p>\n

                      10. Does clearing the DNS cache improve internet speed?<\/h3>\n

                      No, flushing your DNS cache will not disrupt your internet connection; it simply forces your system to refresh its DNS resolver information.<\/p>\n

                      Conclusion<\/span><\/h2>\n

                      Clearing or flushing your DNS cache is like changing the oil in your dev environment\u2014easy to skip, but critical for performance and accuracy. Whether you’re working on staging servers, switching DNS records, or deploying a local test site, keeping your DNS cache fresh means fewer headaches and more productive coding sessions.<\/span><\/p>\n

                      Bookmark this guide and alias those commands now. Your future self will thank you.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

                      Introduction Clearing your DNS cache is a must-know move, whether you’re building a new website, switching environments, or just troubleshooting…<\/p>\n","protected":false},"author":15,"featured_media":11914,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[123,262],"tags":[92,97],"class_list":["post-11337","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-dns","category-domain","tag-dns","tag-domain"],"_links":{"self":[{"href":"https:\/\/nestnepal.com\/blog\/wp-json\/wp\/v2\/posts\/11337","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nestnepal.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nestnepal.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nestnepal.com\/blog\/wp-json\/wp\/v2\/users\/15"}],"replies":[{"embeddable":true,"href":"https:\/\/nestnepal.com\/blog\/wp-json\/wp\/v2\/comments?post=11337"}],"version-history":[{"count":14,"href":"https:\/\/nestnepal.com\/blog\/wp-json\/wp\/v2\/posts\/11337\/revisions"}],"predecessor-version":[{"id":11365,"href":"https:\/\/nestnepal.com\/blog\/wp-json\/wp\/v2\/posts\/11337\/revisions\/11365"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nestnepal.com\/blog\/wp-json\/wp\/v2\/media\/11914"}],"wp:attachment":[{"href":"https:\/\/nestnepal.com\/blog\/wp-json\/wp\/v2\/media?parent=11337"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nestnepal.com\/blog\/wp-json\/wp\/v2\/categories?post=11337"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nestnepal.com\/blog\/wp-json\/wp\/v2\/tags?post=11337"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}