CyberNing

Learn, Share and Grow

Flush DNS

Flush DNS

Most operating systems and DNS clients will automatically cache IP addresses and other DNS results, this is done in order to speed up subsequent requests to the same hostname. Sometimes bad results will be cached and therefore need to be cleared from the cache in order for you to communicate with the host correctly. All major operating systems allow you to force this process. Outlined below are the common steps you will need to follow in order to flush your DNS cache.

Flushing the DNS cache on Windows 10 is a very easy process. Due to system security permissions, you must ensure that you run the command prompt as an administrator user.

  1. Ensure that you’re on the Windows 10 desktop.
  2. Right click on the start menu and choose Command Prompt (Admin) from the menu.
  3. Type in the command ipconfig /flushdns
Windows 10 Flush DNS - Step 1 - Begin on the Windows 10 desktop Windows 10 Flush DNS - Step 2 - Right click on the start menu and choose 'Command Prompt (Admin)' Windows 10 Flush DNS - Step 3 - Command Prompt will open Windows 10 Flush DNS - Step 4 - Type 'ipconfig /flushdns' Windows 10 Flush DNS - Step 5 - The DNS is now flushed Windows 10 Flush DNS - Step 6 - Type 'exit' to close the Command Prompt

Flushing the DNS cache on Windows 8 and Windows 8.1 is a very easy process. Due to system security permissions, you must ensure that you run the command prompt as an administrator user.

  1. Ensure that you’re on the Windows 8 Start Screen.
  2. Simply type cmd and the Windows search bar will appear on the right hand side with search results.
  3. Right click on Command Prompt and click Run as administrator
  4. Type in the command ipconfig /flushdns
Windows 8 / Windows 8.1 Flush DNS - Step 1 - Begin on the Windows 8 Start Screen Windows 8 / Windows 8.1 Flush DNS - Step 2 - Type 'cmd' Windows 8 / Windows 8.1 Flush DNS - Step 3 - Right click 'Command Prompt' and choose 'Run as administrator' Windows 8 / Windows 8.1 Flush DNS - Step 4 - Command Prompt will open Windows 8 / Windows 8.1 Flush DNS - Step 5 - Type 'ipconfig /flushdns' Windows 8 / Windows 8.1 Flush DNS - Step 6 - The DNS is now flushed Windows 8 / Windows 8.1 Flush DNS - Step 7 - Type 'exit' to close the Command Prompt

Flushing DNS on newer versions of Windows is almost as easy as the earlier versions but due to Microsoft’s security additions you must run the command prompt with administrator privileges.

  1. Click the start button and navigate to the command prompt (Start > All Programs > Accessories > Command Prompt)
  2. Make sure that you right click on the command prompt application and choose “Run as Administrator”
  3. Type in the command ipconfig /flushdns
Windows Vista / Windows 7 Flush DNS - Step 1 - Click Start and click All Programs Windows Vista / Windows 7 Flush DNS - Step 2 - Click Accessories Windows Vista / Windows 7 Flush DNS - Step 3 - Click Command Prompt Windows Vista / Windows 7 Flush DNS - Step 4 - Command Prompt will open Windows Vista / Windows 7 Flush DNS - Step 5 - Type 'ipconfig /flushdns' Windows Vista / Windows 7 Flush DNS - Step 6 - The DNS is now flushed Windows Vista / Windows 7 Flush DNS - Step 7 - Type 'exit' to close the Command Prompt

Note: It is also possible to type in cmd into the Windows Vista / Windows 7 start menu search field and then right click on the cmd.exe result instead of having to navigate through the various sub menus.

Flushing the DNS in Mac OS X is an easy process, but the steps taken will depend on which version of OS X you are running.

 

macOS Catalina

If you are running Mac OS X 10.15, you need to follow the below steps:

  1. Open up the command terminal.
  2. Run the command sudo killall -HUP mDNSResponder

 

macOS Mojave

If you are running Mac OS X 10.14, you need to follow the below steps:

  1. Open up the command terminal.
  2. Run the command sudo killall -HUP mDNSResponder

 

macOS High Sierra

If you are running Mac OS X 10.13, you need to follow the below steps:

  1. Open up the command terminal.
  2. Run the command sudo killall -HUP mDNSResponder

 

macOS Sierra

If you are running Mac OS X 10.12, you need to follow the below steps:

  1. Open up the command terminal.
  2. Run the command sudo killall -HUP mDNSResponder

 

Mac OS X El Capitan

If you are running Mac OS X 10.11, you need to follow the below steps:

  1. Open up the command terminal.
  2. Run the command sudo killall -HUP mDNSResponder

 

Mac OS X Yosemite

If you are running Mac OS X 10.10, you need to follow the below steps:

  1. Open up the command terminal.
  2. Run the command sudo discoveryutil udnsflushcaches

 

Mac OS X Mavericks

If you are running Mac OS X 10.9, you need to follow the below steps:

  1. Open up the command terminal.
  2. Run the command sudo killall -HUP mDNSResponder

 

Mac OS X Mountain Lion

If you are running Mac OS X 10.8, you need to follow the below steps:

  1. Open up the command terminal.
  2. Run the command sudo killall -HUP mDNSResponder

 

Mac OS X Lion

If you are running Mac OS X 10.7, you need to follow the below steps:

  1. Open up the command terminal.
  2. Run the command sudo killall -HUP mDNSResponder

 

Mac OS X Snow Leopard

If you are running Mac OS X 10.6, you need to follow the below steps:

  1. Open up a command terminal.
  2. Run the command sudo dscacheutil -flushcache

 

Mac OS X Leopard and below

If you are running Mac OS X 10.5.1 or below, you need to follow the below steps:

  1. Open a command terminal.
  2. Run the command sudo lookupd -flushcache

NSCD – Name Server Cache Daemon

If you are running the nscd Name Service Cache Daemon and wish to flush your DNS cache, then you will need to do the following.

  1. Open up a command terminal (either as root or run step 2 with sudo).
  2. Run the command /etc/init.d/nscd restart

systemd

If you are running a system that uses systemd, in order to flush your DNS cache then you will need to run the following.

  1. Open up a command terminal (either as root or run the following with sudo).
  2. Run the command systemd-resolve --flush-caches
  3. Optional. You can verify that this ran correctly by running the command: systemd-resolve --statistics
Scroll to top