Skip to main content
All CollectionsTroubleshooting | MystNodes Help Center
How to troubleshoot your DNS settings (Windows, MacOS, Linux)
How to troubleshoot your DNS settings (Windows, MacOS, Linux)
Andzej Korkuz avatar
Written by Andzej Korkuz
Updated over 10 months ago

If your node is not working correctly, there could be a problem with your DNS configuration. Follow the suggestions in this article to resolve them.

Windows

Restart your router

Resetting your router is the easiest method to resolve DNS problems. This action refreshes your router's connection, allowing the device to rectify any minor issues.

To restart your router, simply go to your router's settings page using your web browser, navigate to Maintenance or a similar tab, and select the option to reboot the router.

If you are uncertain how to reach your router's settings page, you can simply press the Power button on the router to switch it off. Afterward, press the same button to switch the router back on. Another option is to use the power socket to unplug your router and plug it back in.

Flush the DNS cache and renew your IP address

Another way to easily solve DNS issues is by clearing the DNS cache on your PC. By doing this, you can resolve most of your DNS-related problems without losing any personal data that you have stored on your computer.

To flush the DNS cache and renew your IP address, please follow these steps:

  1. Open the start menu and search for Command Prompt;

  2. Right-click on the Command Prompt application and then press “Run as administrator”;

  3. Type in the following commands (make sure to press enter after each one):

ipconfig /flushdns
ipconfig /registerdns
ipconfig /release
ipconfig /renew
netsh winsock reset catalog
netsh int ipv4 reset reset.log
netsh int ipv6 reset reset.log

Use alternative DNS servers

If you haven't set up a third-party DNS server, your Windows PC will use the default DNS servers provided by your internet service provider. However, these servers may not always be the most effective. Therefore, when you encounter DNS issues, it is advisable to switch to different DNS servers.

There are multiple free alternative DNS servers that you can use, in this guide, we will be using Google’s DNS servers. To add these DNS servers, follow these steps:

  1. Open Control Panel, then go to Network and Internet. Afterward, open Network and Sharing Center, and finally – Change adapter settings.

  2. Right-click your network adapter and choose Properties.

  3. Press on Internet Protocol Version 4 (TCP/IPv4) and then Properties.

  4. Enable the Use the following DNS server addresses option.

  5. Enter 8.8.8.8 as the Preferred DNS server and 8.8.4.4 as Alternate DNS server.

  6. Press OK.

MacOS

Restart your router

Just as with the Windows instructions above, you should first try restarting your router.

To restart your router, simply go to your router's settings page using your web browser, navigate to Maintenance or a similar tab, and select the option to reboot the router.

If you are uncertain how to reach your router's settings page, you can simply press the Power button on the router to switch it off. Afterward, press the same button to switch the router back on. Another option is to use the power socket to unplug your router and plug it back in.

Update your browser and macOS itself

If there are any problems with certain versions of macOS, it is advisable to update to the most recent version of the macOS edition you are using. Alternatively, if you are willing to make a major update, you can upgrade to the latest macOS version that is compatible with your Mac hardware. By doing so, you should be able to resolve any DNS issues caused by known Apple bugs.

Restart mDNSResponder

When you access the macOS Activity Monitor, you will notice an application named "mDNSResponder" among the various programs running in the background of the operating system. This small software serves a significant purpose of searching for devices on the network that utilize Apple's Bonjour zero-configuration network protocol.

Sometimes, restarting this particular application can resolve all DNS issues. To restart it, follow these steps:

  1. Open the Activity Monitor by searching for it in Spotlight Search.

  2. Look for mDNSresponder in the list of running processes.

  3. Select this process and then press on the X icon to close it.

  4. Press Quit.

Flush your DNS settings

DNS flushing can also resolve potential DNS issues. The commands are different for various versions of macOS, but the initial process is the same:

  1. Open the Finder

  2. Click on Applications

  3. Scroll down until you find Utilities

  4. Open the Terminal utility

Now, based on the macOS version that you are using, type in this command:

For Ventura and Monterrey: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

For Lion, Mountain Lion, Mavericks, El Capitan, Sierra, High Sierra, Mojave: sudo killall -HUP mDNSResponder

For Yosemite: sudo discoveryutil mdnsflushcache

For Tiger: lookupd -flushcache

Linux

Restart your router

Once again, it all begins with the restart of your router.

To restart your router, simply go to your router's settings page using your web browser, navigate to Maintenance or a similar tab, and select the option to reboot the router.

If you are uncertain how to reach your router's settings page, you can simply press the Power button on the router to switch it off. Afterward, press the same button to switch the router back on. Another option is to use the power socket to unplug your router and plug it back in

Check DNS Configuration

Verify the DNS configuration in /etc/resolv.conf. Use a text editor to open the file and ensure it contains valid DNS server IP addresses.

Test DNS Resolution

Use the nslookup or dig commands to test DNS resolution.

Check Network Connectivity

Ensure that the Linux system has a working network connection. Use tools like ping or traceroute to test connectivity to DNS servers and external hosts.

Check DNS Server Reachability

Confirm that the DNS servers specified in /etc/resolv.conf are reachable. Use ping or telnet to test connectivity to these servers.

Did this answer your question?