Dns error dns lookup

The DNS lookup failed message on the browser is a net connection error. The Google Chrome error message states This webpage is not available. The server at… can’t be found, because the DNS lookup failed.

The error message prevents users from accessing the website, but it, in most cases, doesn’t have to do with the website at all. Rather, the error is related to misconfigured browser settings, the presence of conflicting applications, or issues with the current DNS server.

Many came across the error in these cases:

• 504 DNS lookup failed FortiGate: Users with the FortiGate firewall have reported encountering the error frequently, and disabling the firewall did the trick.
• DNS lookup failed VPN: When encountering the error while using a VPN, switching to a reliable VPN should fix the error.

So, let’s find out how you can fix the DNS lookup failed error on your browser in the following sections, and all about the error itself.

What does it mean when DNS failed?

A DNS failed error basically indicates the inability to connect to the corresponding IP address of the website. It could be to problems with the DNS server itself, misconfigured network settings, or third-party applications conflicting with it.

In most cases, the solutions are simple and things are up and running in a jiffy. Many recommend switching to public DNS servers, such as that of Google, to eliminate errors like these.

Quick Tip:

If Google Chrome persists in showing you the error message even after you tried all troubleshooting solutions, you should try using a different browser instead. Opera is a great alternative.

Not only is it incredibly powerful and lightweight, but it is also extremely stable, receiving updates after updates that are constantly maintained in peak condition.

Opera

A web browser that balances out stability, performance, a high level of customization, and low system requirements.

Why do we need DNS?

Every website on the Internet is assigned an address, which consists of a string of numbers and characters. To simplify things for users, websites are also assigned a domain name. For instance, https://windowsreport.com/, is the domain name and not the IP address.

Now, while people understand the domain name, computers, on the other hand, use the assigned IP address.

This is where the DNS (Domain Name System) server comes into the picture. When you enter the domain name in the address bar of the browser, it locates the corresponding IP address and opens the website. And when the DNS fails, the website won’t open.

What to do if the browser stops working after DNS fail?

1. Clear cookies and cache

1. Launch the browser, and press Ctrl + Shift + Del to open the Clear browsing data utility.
2. Select All time from the Time range dropdown menu.
3. Select the checkboxes for Browsing history, Cookies and other site data, and Cached images and files, and then click on Clear data at the bottom.

If the manual method seems like too much of a hassle, you could always opt for a third-party PC cleaner. This type of tool will scan your browser for unnecessary clutter and let you know what can be removed.

Alongside cleaning your browser, dedicated cookie cleaners generally include other PC optimization tools such as registry cleaners and startup editors.

On top of that, some browser cleaners will help you remove unwanted toolbars and plugins, remove spam/useless emails, and more.

We recommend CCleaner from the list of software we tested, which performs thorough cleaning, as one of the best tools for this task.

CCleaner makes it simple to get the most out of your computer because PC maintenance has to be at the top of the priority list. Furthermore, if you can tune up your computer on a regular basis, you’ll be more satisfied with its overall performance.

Once done, check if the DNS lookup failed error on the browser is fixed.

2. Open the Internet Connections Troubleshooter

1. Press Windows + I to open the Settings app, and click on Troubleshoot on the right.
2. Next, click on Other troubleshooters.
3. Locate the Internet Connections option here, and click on the Run button next to it.
4. Then go through the suggested resolutions from the troubleshooter.

Once done, check if the DNS lookup still fails intermittently on the browser. If that’s the case, head to the next method.

3. Change the DNS Server

1. Press Windows + S to launch the Run command, enter ncpa.cpl in the text field, and click OK.
2. Right-click the active connection to select Properties.
3. Now, select Internet Protocol Version 4 (TCP/IPv4), and click the Properties button.
4. Select the Use the following DNS server addresses radio button, and enter the following DNS server in the two fields:
   • Preferred DNS server: 8.8.8.8
   • Alternate DNS server: 8.8.4.4
5. Click the OK button at the bottom of this and other windows to save the changes.

4. Flush the DNS

1. Press Windows + S to open the Search menu, enter Terminal in the text field, right-click on the relevant search result, and select Run as administrator.
2. Click Yes in the UAC prompt.
3. Press Ctrl + Shift + 2 to open Command Prompt in a new tab.
4. Now, paste the following command and hit Enter:ipconfig /flushdns

Flushing the DNS cache is a straightforward potential resolution for the DNS lookup failed error on browsers.

5. Restart the Network Stack

1. Press Windows + X to open the Quick Access menu, and select Windows Terminal (Admin).
2. Click Yes in the UAC prompt.
3. Click on the arrow at the top, and select Command Prompt from the menu.
4. Now, paste the following command and hit Enter:netsh winsock reset catalog
5. Once done, restart the computer for the changes to come into effect.

Some users might need to restart a corrupted network stack to fix the DNS lookup failed error on the browser.

How do I find my DNS server?

1. Press Windows + R to open Run, type ncpa.cpl in the text field, and click OK.
2. Now, double-click on the active network adapter.
3. Click on Details.
4. You will now find the DNS server listed here.

The above resolutions will probably resolve the DNS lookup failed error for most users so that they can open webpages in Chrome and other browsers, whenever the error is encountered

Also, find out what to do when seeing the Your DNS server might be unavailable error message in Windows 10/11.

Tell us which fix worked for you in the comments section below.

Stuck with a Docker image DNS lookup error? Fear not, our Support Team is here with a solution.

At Bobcares, coming up with solutions for queries, big and small is a part of our Server Management Services.

Let’s take a look at how our Support Team resolved the DNS lookup error today.

About DNS lookup errors

Have you been experiencing a number of obscure errors with your applications?? This might be due to Docker’s internet connectivity issues. According to our Support Tech, this may be a result of failing DNS lookups. Resolving this issue will also help you bid adieu to the pesky docker image DNS lookup error.

Narrowing down docker image DNS lookup error

First, we will check the basic internet connectivity by pinging a public IP address. If it succeeds, you will get a similar output as seen below:

$ docker run busybox ping -c 1 192.203.230.10 # Ping a London-based NASA root nameserver PING 192.203.230.10 (192.203.230.10): 56 data bytes 64 bytes from 192.203.230.10: seq=0 ttl=53 time=113.866 ms --- 192.203.230.10 ping statistics --- 1 packets transmitted, 1 packets received, 0% packet loss round-trip min/avg/max = 113.866/113.866/113.866 ms

After that, let’s try resolving google.com domain as shown below:

$ docker run busybox nslookup google.com 
Server: 8.8.8.8 
Address 1: 8.8.8.8 nslookup: can't resolve 'google.com'

If you get a “can’t resolve” message as seen above, it indicates a problem with resolving DNS.

Why does docker image DNS lookup error occur?

Before we dive into resolving the issue, let’s take a look at why the DNS lookup errors keep occurring. In fact, a DNS server that is locally defined in the /etc/resolv.conf file, containers by default, use 8.8.8.8, Google’s public DNS server to resolve DNS.

Hence, the error occurs, then this process is interrupted. Interestingly, in some places, network administrators intentionally block public DNS servers to ensure that the network’s own DNS server is used instead.

In such cases, Docker containers that rely on the default configuration are unable to resolve DNS. Thereby making the internet unusable from within those containers.

Quick fix for docker image DNS lookup error

Our Support Engineers have come up with a quick fix to ensure that the docker container runs with a custom DNS server.

1. First, we will track down the address of the DNS server from within Ubuntu with the following command:

   $ nmcli dev show | grep 'IP4.DNS' 
   IP4.DNS[1]:                       10.0.0.2

2. Then, we will run a docker container with the DNS server obtained in the previous step. We will include the –dns flag as well with the command as seen below:

   $ docker run --dns 10.0.0.2 busybox nslookup google.com 
   Server: 10.0.0.2 
   Address 1: 10.0.0.2 
   Name: google.com 
   Address 1: 2a00:1450:4008:811::200e lhr26s02-in-x200e.1e100.net 
   Address 2: 216.58.198.173 lhr25s10-in-f14.1e100.net

Permanent fix for docker image DNS lookup error

If you prefer a more permanent fix, our Support Engineers have that covered as well.

1. First, we will change the DNS settings of the Docker daemon by creating the daemon configuration file at /etc/docker/daemon.json.
2. Then, configure the daemon configuration file with a set of two DNS, namely, the network DNS server and the Google DNS server. The latter works as a backup in case the network DNS server is not available.

   /etc/docker/daemon.json:
   {
       "dns": ["10.0.0.2", "8.8.8.8"]
   }

3. After that, restart the docker service with the following command:

   sudo service docker restart

You can test this fix by pinging google.com from any Docker container without having to override the DNS server. For instance:

$ docker run busybox nslookup google.com 
Server: 10.0.0.2 
Address 1: 10.0.0.2 
Name: google.com 
Address 1: 2a00:1450:4008:811::200e lhr26s02-in-x200e.1e100.net 
Address 2: 216.58.198.173 lhr25s10-in-f13.1e100.net

[Need a hand with another query? Give us a call today.]

Conclusion

At the end of the day, we learned how to resolve the DNS lookup error. The Support Team at Bobcares offered us a quick fix as well as a more permanent fix to resolve the issue.

Disclaimer: This post may contain affiliate links, meaning we get a small commission if you make a purchase through our links, at no cost to you. For more information, please visit our Disclaimer Page.

Have you ever encountered DNS Lookup Failed error in Google Chrome? Do you know what this error is and how to fix it?

Nowadays, Microsoft’s Windows is a popular operating system that has installed and running on billion computers and devices.

However, it also has a few annoying errors that always repeat over and over and over again, such as DNS or BSOD errors. In Google Chrome, the DNS Lookup Failed is one of the most common errors, along with Err_Connection_Reset or Err_Name_Not_Resolved.

This error occurs because something happened to your DNS servers, such as DNS servers were timed out, or could not connect to DNS servers somehow.

Sometimes, this error occurs because your computer uses wrong DNS information. Also, expired caches could also cause DNS Lookup Failed error on your Google Chrome browser.

When it happens, you can’t use your Chrome browser to load any websites. It is a very annoying error, right?

However, this error is very easy to fix with a few simple steps. In this article, I will show you a few simple solutions you can follow and resolve DNS Lookup Failed error on your Google Chrome browser.

As I said above, if DNS servers are timed out, DNS Lookup Failed error could appear on your Chrome browser.

By default, Windows PC (or any other operating systems, such as Mac OS or Linux) will automatically be pulled DNS details directly from the ISP (Internet Service Provider) and use them as default DNS servers.

However, these DNS servers are not stable and always time out. When it is timed out, it could lead to DNS errors.

In order to fix it, you just need to replace the default DNS server on your computer with a third-party DNS service, like Google’s DNS or OpenDNS. Both are excellent alternative DNS server services that recommended by many regular users and experts.

How To Change Default DNS Server On Your Computer

In order to change the default DNS server on your Windows computer, open Network and Sharing Center by right-clicking “Network icon” in the taskbar notification area, and then click “Open Network and Sharing Center”.

Next, click on the currently connected network adapter and select Properties.

In the next step, click on the “Internet Protocol Version 4 (TCP/IPv4”. It will show you two boxes to enter DNS servers you want to use. Take a look at the image below.

I often use Google’s DNS service with the following IP addresses: 8.8.8.8 and 8.8.4.4. Just fill up two boxes with these IP addresses and the error should be fixed immediately.

This method can also help you to fix many other DNS errors on your Windows computer, including Dns_Probe_Finished_Nxdomain and Dns_Probe_Finished_Bad_Config.

If you are facing any DNS errors, you should also try this solution.

Clear DNS Cache On Your Computer To Fix DNS Lookup Failed Error

If you have tried the method above, but the error persists, you can try to remove all DNS caches on your Windows PC with a simple command in Command Prompt.

As I mentioned above, wrong DNS information or expired DNS caches could be a cause of this DNS error. So if you want to fix it, just flush all DNS caches on your Windows computer.

In order to remove all DNS caches:

1. Click on Start logo.
2. Type cmd.exe in the Run dialog box.
3. Right-click on the cmd.exe.
4. Choose “Run as Administrator” to open Command Prompt program with administrator privilege.
5. In Command Prompt program, type ipconfig /flushdns and press Enter.

That’s it!

To increase the successful percentage of this solution, you should also remove all caches and cookies of your Google Chrome browser. If you don’t know how to do that, read this article.

I hope you have fixed DNS Lookup Failed error on your Chrome browser with these methods. These solutions also help you to understand more about DNS errors and resolve other DNS problems.

Attention Before you read this post, I highly recommend you check out my resources page for access to the tools and services I use to not only maintain my system but also fix all my computer errors, by clicking here!

This post looks at the DNS lookup error, encompassing solutions, and a general overview of what a DNS is.

The definition of the DNS or Domain Name System is that of a hierarchical setup for services, nodes and resources that are tied to a private network or the internet. Through this system, internetworked information is distributed amongst peers using this domain name system. However, the most important aspect of its functionality is its ability to translate a meaningful domain name into binary or numerical identifiers which is better understood by network devices for the sole purpose of globally finding and addressing these specific devices.

The Domain Name System functions similarly to a phone directory or rather internet directory, in that it translates user created hostnames into IP addresses. An example of this would be the translation of www.example.com into an IP address which is constructed in the following format “XXX.XXX.XXX.XXX” where XXX donates a number from 1 to 255.

If, when attempting to access a site you receive the following message “lookup error” or “webpage is unavailable”, then there’s a good chance it is a DNS lookup error. Due to the constant DNS service halts, misconfigured firewalls and system crashes, DNS servers more often than not become unreachable. A server that is unresponsive typically results in decreased efficiency and increased lookup times. If queries made by the Domain Name System, stop receiving answers, then it can adversely affect your ability to access the internet. Thus, “This webpage is unavailable” is typically the way it manifests itself in your browser window. Anyway, continue reading for a number of techniques that you can use to fix this DNS lookup error.

Check Physical Connections

Before delving into any technical stuff, checking physical connections should be the very first thing that you do. Ensure that the cables that are connected to your modem/router are secure and that all the relevant lights on the device are flashing. There are times when the DNS lookup error is brought upon by loose cable(s), in the event that this is the case in your situation, you should reconnect your cables then immediately restart your computer.

You will also have to restart your router, which can be done through the routers settings screen. To do this, simply do the following.

1. First, ensure you’ve logged into your computer with a user profile that has administrative rights.

2. Then load up your browser windows and type either 192.168.0.1 or 196.168.1.1 into the address bar and press Enter.

Note: If you type the first IP address into your address bar and receive a “The connection has timed out” error message, then you should try the second IP address.

3. When the Authentication Required dialog box pops up, type in your routers User Name: and Password: then click on OK.

Note: If you haven’t already changed your default password then simply type admin into the User Name box and password into the Password box.

4. Once you’ve logged into your router, click on Diagnostics in the Maintenance section on the left side menu.

5. From the Diagnostics screen, click on the Reboot button within the Reboot the Router section of the page.

Flush Your DNS Server Cache

If after checking all your cable connections and restarting your router, the problem still persists, then flushing your DNS server cache may be able to do the trick. Additionally, you may want to try this method when you’re having problems accessing specific websites. Flushing your DNS cache is a fairly simple process that you can carry out at any time. Simply follow the instructions below to carry out this function.

1. First, ensure you’ve logged into your computer with administrative rights.

2. Then click on Start -> Run, type cmd and click on OK. [Windows Vista/7: Start -> Type cmd (into the Search programs and files box) and Press CTRL + Shift + Enter, then click on Continue]

3. Once Command Prompt has loaded up, type ipconfig /flushdns and hit Enter.

Renew Your IP

There are a number of reasons why you may want to renew your IP address. The most common reason why you may want to adopt this method is if you’ve lost your connection to the internet. This loss of connection could be due to your routers inability to assign IP address to computers attached to it. On the flip side, you may want to use this command to reset your internet connection as a possible fix for the DNS lookup error you’re currently faced with.

Do You Need To Renew Your IP Address?

Well, if you’ve followed my guide from the beginning and restarted your router, then renewing your IP address would be a pretty pointless endeavour. However, in the event that you opted against restarting your router, you can choose to renew your IP address without having to switch your router off, which would otherwise adversely affect other computers connected to the router. To do this, simply do the following.

1. First, ensure you’ve logged into your computer with administrative rights.

2. Then click on Start -> Run, type cmd and click on OK. [Windows Vista/7: Start -> Type cmd (into the Search programs and files box) and Press CTRL + Shift + Enter, then click on Continue]

3. From Command Prompt type ipconfig /release and press Enter.

4. Then type ipconfig /renew and press Enter.

Note: The first command will release your IP address, and the second command will assign you a new one. To double check that you’ve been assigned a new IP address, simply type ipconfig in Command Prompt.

Rebuild Your Connection to Fix DNS Lookup Error

Using the repair feature in network connections is probably a more user friendly approach to carrying out most of the functions outlined above. Anyway, in order to use this feature, simply do the following.

1. First, log into your computer with administrative rights.

2. Then click on Start, then right click on My Network Places and click on Properties.

3. From the Network Connections applet, double click on Local Area Connection.

4. This will bring up the Local Area Connection Status dialog box, from here click on the Support Tab, and then click on Repair.

Change Your DNS Servers

In most cases, simply clicking on the reload button in your browser is enough to fix a DNS lookup error. However, if the above mention techniques have seen little success, then you will definitely need to take more drastic action. The error(s) that you’re receiving could be due to the DNS servers of your Internet Service Provider (ISP). The good thing is that there are actually more reliable DNS servers out there that you can use. So changing your DNS server may be all you need to do to fix this problem. To do this, do the following.

1. First, ensure you’ve logged into your computer with administrative rights.

2. Then click on Start, then right click on My Network Places and select Properties.

3. From the Network Connections applet, right click on your Local Area Connection and select Properties.

4. This will bring up the Local Area Connection Properties page, click on Internet Protocol (TCP/IP), and then click on Properties.

5. From the Internet Protocol (TCP/IP) Properties page, click on Use the following DNS server addresses then type in the following OpenDNS Servers:

Preferred DNS Server: 208.67.222.222

 Alternate DNS Server: 208.67.220.220

Alternatively, you could put these DNS server addresses into your router, that way, the servers will be used by everyone that accesses the internet through it. To do this, do the following.

1. First, follow steps 1 – 3 of “Check Physical Connections”.

2. Once logged in, click on Basic Settings, which is in the Setup section.

3. From Basic Settings, scroll down to Domain Name Server (DNS) Address and click on Use These DNS Servers, then type the two previously mentioned OpenDNS Server IP addresses above. Then click on Apply.

Introduction

DNS (domain name system) stores information related to domain names as a distributed database. The client-server service translates domain names to IP addresses and vice versa.

Most other network services, such as Web, emails, and file transfer, use DNS. A misconfigured DNS server can lead to critical connectivity issues. Thankfully, troubleshooting DNS issues is a vital and relatively simple process to follow.

Follow this tutorial to learn the practical steps in troubleshooting DNS issues.

Prerequisites

• A stable internet connection.
• Access to the command line/terminal.
• A user account with administrator/sudo privileges.

DNS troubleshooting follows logical steps from basic network troubleshooting to more in-depth analysis. Network services often report DNS issues for reasons that do not require in-depth DNS troubleshooting.

If you are experiencing DNS issues, start by performing the following steps before going on to in-depth troubleshooting:

• Check cables

If using a wired connection, make sure everything is connected properly. On wireless networks, check if WiFi is turned on and connected. Check the router if all cables are functional. Try to switch ports for ethernet cables and test out the connection.

• Restart router

Turn the router off and wait for at least two minutes before turning it on again. Wait until the router fully boots up before rechecking the connection.

• Scan for malware

Viruses sometimes block an internet connection. Run a scan to see if anything suspicious appears and handle accordingly.

• Check the website

If the problems arise when connecting to a particular website or a part of the website, check if the connection problem is with the website itself. One way to do this is using the ping command.

The command output helps identify the reason for the connection problem:

1. If ping does not show a response, the issue is most likely on the server’s end.

2. A common cause of an error in the response is a poorly configured DNS server or firewall restrictions. Learn how to resolve the «Temporary failure in name resolution» error.

3. If the output shows a response, the problem is most likely with the DNS.

The comprehensive list below provides valuable tips for troubleshooting DNS issues.

Check TCP/IP Settings

Misconfigured DNS server addresses are a common issue. Reset the settings and check if communication is back to normal. Depending on which OS you’re using, the steps are different.

For Windows:

1. Search for Network Status in the Start menu and open the tool.

2. Select Properties under the network connection details.

3. Click the Edit button to change the IP settings.

4. If the IP assignment is Manual, double-check the IP, Preferred, and Alternate DNS addresses. Change IP assignment by selecting Automatic (DHCP) from the dropdown menu to reset back to normal.

5. Save the settings when finished.

For Linux:

1. Click the connection icon in the top-right corner.

2. Open the menu and select Wired Settings.

3. Click the gear icon in the connection pane to open the settings.

4. Navigate to the IPv4 tab in the settings menu.

5. If manually assigned, double-check the Address and DNS IP address list. Select the Automatic (DHCP) option and change the DNS switch to Automatic to reset back to normal.

Apply the settings when finished and close the window. Lastly, check the connection to ensure everything functions correctly.

Flush the DNS Cache

IP mapping to popular websites is often the target of malicious attacks. DNS caches information to improve loading speed, and it might have cached a wrong address. Clearing the DNS cache deletes all the lookup information and updates with subsequent requests.

Flushing DNS cache is a good security measure to take in general. Follow our tutorial for detailed and OS-specific instructions: How to Flush DNS Cache in macOS, Windows, & Linux.

Release and Renew DHCP Server IP

Releasing and renewing the IP address helps resolve an IP conflict and old DNS information by refreshing the cached information. The easiest way to accomplish a release and renewal is through the command prompt/terminal.

To renew the IP on Windows using the command prompt:

1. Run the following commands to release the current IP and renew the information:

IPCONFIG /RELEASE
IPCONFIG /RENEW

2. Check the new information with:

IPCONFIG /ALL

To force IP renewal on Linux via the terminal:

1. Open the terminal and release the current IP with the following command:

sudo dhclient -r

The terminal outputs a confirmation message, and the connection is closed.

2. Run dhclient without any options to renew the IP:

sudo dhclient

Change to Public DNS Servers

Change the DNS servers to public domain addresses. Some standard options are:

• Google’s 8.8.8.8 address as primary and 8.8.4.4 as secondary.
• Cloudflare’s 1.1.1.1 address as primary and 1.0.0.1 as secondary.

Public domain addresses are generally reliable and are available for free. However, use this only as a temporary resolution.

On the other hand, some public domain DNS servers block traffic from malicious websites. A public DNS might detect a flagged website as suspicious, and the public DNS you’re using might be blocking access.

Use dig

The dig command (domain information groper) provides DNS information and helps in diagnosing issues. The utility’s raw output makes it the preferred method for troubleshooting DNS issues.

The program is available on macOS and Linux by default and is free to install on Windows.

To get dig information for a domain, run the following command in the terminal:

dig <domain name or IP>

For example, to show the information for phoenixnap.com, run:

dig phoenixnap.com

• The status shows whether a query was successful.
• The ANSWER SECTION shows a response to a request sent in the QUESTION SECTION.
• The SERVER displays the address for the public DNS server.

By default, dig looks up the A record for a domain and shows which IP address the domain points to when resolving the name.

The dig tool offers many advanced options for comprehensive searches. For example, add the +trace tag to see the full path to the destination:

dig phoenixnap.com +trace

The +trace option helps pinpoint traffic drops in the route to the destination.

To check the delegated name servers, use the ns option:

dig phoenixnap.com ns

Use the ns option to help identify and troubleshoot delegation problems.

Use nslookup

The nslookup command provides functions for checking different DNS records and servers. The tool is available on macOS, Linux, and Windows operating systems by default, and it was the first tool for querying DNS.

To get nslookup information for a domain, use the following command in the command line/terminal:

nslookup <domain name or IP>

For example, run nslookup for phoenixnap.com:

nslookup phoenixnap.com

The output prints the DNS server’s address and the A record response. The nslookup command is preferable for Windows because of its availability.

Use host

The host utility is a straightforward program for performing a DNS lookup. The command is available for macOS and Linux systems.

The basic syntax for host is:

host <domain name or IP>

For example:

host phoenixnap.com

The host command is excellent for quickly checking if a domain name exists and resolves to an address. A typical use case for host is in bash scripts.

Use additional options to display more information. For example, add the -a tag to see a similar output to the dig command:

host -a phoenixnap.com

The output shows additional information in the answer section, such as the NS, SOA, MX, and other available records.

Use traceroute or tracert

The traceroute and tracert tools help trace a route from source to destination. When troubleshooting DNS issues, the commands help identify where packets stopped on the network. The traceroute command is available on macOS and Linux, while the Windows equivalent is tracert.

sudo apt install traceroute

To map the network, run the following command in the terminal:

traceroute <domain name or IP>

If using a Windows machine, run:

tracert <domain name or IP>

For more information on the traceroute/tracert command and how to read the output, check our comprehensive tutorial on How to Run a Traceroute on Linux, Windows & macOS.

Contact Your ISP

If the computer uses the ISP’s DNS, you cannot resolve the issues on your end. Contacting the ISP helps determine the problem and pinpoint the difficulties on their end.

Conclusion

At the end of this guide, you should have several tools and tricks to help you resolve DNS issues. If you’re looking to set up your DNS server at home to speed up your connection, try following our Raspberry Pi tutorial on How to Set Up Raspberry Pi as a DNS Server.