3.13. Flushing the DNS cache

Caching DNS provides quick access to any domain and reduces the load on DNS-server by reducing the number of calls to it. However, caching has its drawbacks, which is expressed in the impossibility of opening a site when changing the IP address to which the domain refers. To update information from the system DNS cache clearing may be required DNS. Information can be cached both locally and on used DNS-servers (for example, Cloudflare/Google).

  • Clearing local cache
  • Clearing the public DNS cache

Local cache is a cache stored directly on the device being used.

  1. Open command prompt.
  2. Enter the command:
     ipconfig /flushdns

  3. Clickon Enter and wait for the command to complete:

If the message “ The requested operation needs to be promoted ", Then you need to run the command line as administrator.

If the message “ Can't clear resolver cache DNS: Function execution error "Means your service is disabled. DNS-client. In this case, clearing the cache DNS not required as it doesn't work.

Linux does not cache DNS-requests if you are not using local DNS-server. If such is used, you need to determine which one DNS-Server is running on the computer, and restart it. Typically, this is BIND or nscd. Depending on the used DNS-server, in the terminal you need to run one of the commands:

  • For BIND:
      / etc / init.d / named restart
  • For nscd:
      / etc / init.d / nscd restart
  1. Open terminal.
  2. Run the command corresponding to the OS version you are using:
    • macOS 10.12 Sierra and later:
        sudo  killall  -HUP mDNSResponder; sudo  killall mDNSResponderHelper; sudo dscacheutil  -flushcache 

    • OS X 10.11 El Capitan:
       sudo  killall  -HUP mDNSResponder
    • OS X 10.10 Yosemite:
      • Versions 10.10.4 and higher:
          sudo dscacheutil  -flushcache ; sudo  killall  -HUP mDNSResponder
      • Versions 10.10.1-10.10.3:
          sudo discoveryutil udnsflushcaches
    • OS X 10.9 Mavericks:
       dscacheutil -flushcache ;  sudo  killall  -HUP mDNSResponder
    • Mac OS X 10.7 Lion and 10.8 Mountain Lion:
       sudo  killall  -HUP mDNSResponder
    • Mac OS X 10.5 Leopard and 10.6 Snow Leopard:
       dscacheutil -flushcache 
    • Mac OS X 10.4 Tiger:
       lookupd -flushcache 

Public cache DNS- cache stored on used devices DNS-servers. Clearing the public cache DNS only affects those who use them. If your device uses non-public DNS, and, for example, DNS-server of your provider, then clearing the cache of public DNS will not affect the information given DNS-servers of your provider. To rectify the situation and quickly update your domain data, set up public DNS.

  1. Openup  this page.
  2. Fill in the fields and click " Purge Cache »:
    • « Domain Name "- specify the name of the domain for which you want to clear the cache.
    • « Record Type "- select the entry for which you want to remove information from the cache.
  3. Repeat the operation for each record for which you want to update information.
  1. Openup  this page.
  2. Fill in the fields, check the box next to " I am not a robot " and press " Flush cache »:
    • « Domain name "- specify the name of the domain for which you want to clear the cache.
    • « RR type "- select the entry for which you want to remove information from the cache.
  3. Repeat the operation for each record for which you want to update information.
  1. Openup  this page.
  2. In field " Enter a domain name to check "Specify the domain name and click" CHECK THIS DOMAIN »:
  3. Scroll down the page and click " REFRESH THE CACHE »:
  • 0 Users Found This Useful
Was this answer helpful?

Related Articles

3. Domains

In chapter "Domains»Domains are managed, their records and settings are changed.

3.1. Domain management

3.1.1. Domain setting 3.1.1.1. Adding a DNS record 3.1.1.2. Changing the DNS record...

3.2. Domain registration

3.2.1. Domain order and registration 3.2.2. New orders for domain registration...

3.3. Domain contacts

Domain contacts - information about the owner (registrant) of the domain name, registrar,...

3.4. Domain transfer

Full transfer of domain rights to another user within our system. Please note: using the...