Dns lookup failed что значит
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.
Solutions Detail
5) Find Local DNS Server
If you still have not discovered the cause, then it is possible you have a local DNS server that is intercepting requests and at fault.
As root, run:
this will tell you if any program is responding to DNS requests.
If the output is:
If you want to explore further, there may be other programs listening for UDP requests on your hosts. This command, run as root will show you these:
Initial Steps Overview
Solution 9: Disable Proxy (Firefox Users only)
Firefox users who encounter DNS Failure error can follow the method below to resolve the issue:
Hopefully, by following all of the above fixes you might be able to get rid of the error easily but if it continues to stay then you may Contact Us here for further help.
Matthew is a freelancer who has produced a variety of articles on various topics related to technology. His main focus is the Windows OS and all the things surrounding it. He is passionate about. Read more
- Users reported getting DNS lookup failed errors when using their browsers.
- If you too encountered this error message, check out the solutions we have written for you below.
- To learn more about common browser issues, visit our dedicated Browser Errors Hub.
- If you need to know everything there is to know about browsers, visit our Browser section.
Strugling with your current browser? Upgrade to a better one: Opera You deserve a better browser! 350 million people use Opera daily, a fully-fledged navigation experience that comes with various built-in packages, enhanced resource consumption and great design. Here's what Opera can do:
- Easy migration: use the Opera assistant to transfer exiting data, such as bookmarks, passwords, etc.
- Optimize resource usage: your RAM memory is used more efficiently than in other browsers
- Enhanced privacy: free and unlimited VPN integrated
- No ads: built-in Ad Blocker speeds up loading of pages and protects against data-mining
- Gaming friendly: Opera GX is the first and best browser for gaming
- Download Opera
The DNS lookup failed error 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. Consequently, users can’t open any website pages in Chrome.
Learn how to fix this below.
3. If Nothing Works, Clearing Cache & Cookies Will-
- Press Ctrl+Y (Windows) & CmD+Y (MAC)
- Click on the Clear browsing data button on the left-hand side.
- Select Browsing history, Cached Images and Files and Cookies and other site data.
- Click on clear.
Solution 2: Reset Your IP Address
Turn off your Modem and turn it back on after 30 seconds. This should change your IP Address and possibly resolve the DNS Lookup Failed issue as well. While waiting to turn the modem back on, you should restart your computer as well.
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:
- Click on Start logo.
- Type cmd.exe in the Run dialog box.
- Right-click on the cmd.exe.
- Choose “Run as Administrator” to open Command Prompt program with administrator privilege.
- In Command Prompt program, type ipconfig /flushdns and press Enter.
To view this video please enable JavaScript, and consider upgrading to a web browser that supports HTML5 video
DNS Lookup Failed is actually quite a common error that is being faced by a lot of Chrome users. However, the error isn’t restricted to just Chrome, there have been instances on Mozilla Firefox and other browsers as well. In this article, we have compiled solutions, workarounds, and fixes that will help you to completely get rid of the error message.
Also, we have acquired some information as to why it occurs in the first place and have also listed the reasons below. Make sure to read through the reasons why it occurs and then start implementing the solutions one-by-one until one of them fixes this error message for you.
A) Edit /etc/hosts
Comment out the identified entry in /etc/hosts and go to Check Resolution.
Check RunBook Match
If your application is pausing when a network request happens, this runbook may be a match.
This failure might be intermittent (due to caching of DNS responses in the application), or consistent.
If the DNS response is delayed, but returns a correct IP address see the DNS lookup delay runbook.
This runbook assumes you are on a Linux machine.
Solution 5: Reset the Winsock Catalog
If the above fixes did not work for you, try resetting your Network Stack by following the steps below:
If you want to have your PC related issues fixed automatically and diagnose, list, and rectify any registry errors, we recommend that you try using the Restoro Repair Tool that can easily do all of this at a single click. It has been rated Great by Trustpilot so you don’t have to worry about anything.
- In the search bar near the Start menu type in “Run” and press “Enter”.
- In the Run dialogue box, type in “cmd” and on your keyboard press and hold the following buttons in order: “Ctrl + Shift + Enter”.
- This should run the Command Prompt window as “Administrator”.
- Once the Command Window opens up, type in the following command and press “Enter”.
- Press “Enter” and then “Restart” your computer.
What to do if the browser stops working after DNS fail?
4. Change the DNS Server
- Right-click the Start button and click Run to launch that accessory.
- Input ‘ncpa.cpl’ in the Open box.
- Right-click the active connection to select Properties.
- Then select Internet Protocol Version 4, and press the Properties button.
- Select the Use the following DNS server addresses radio button.
- Input ‘8.8.8.8’ in the Preferred DNS server text box.
- Then enter ‘4.2.2.2’ in the Alternative DNS server box.
- Click the OK button on the Internet Protocol Version 4 window.
3) Determine DNS lookup method
There are numerous ways DNS lookups can be performed. We now need to gather some facts about your host to determine what is doing the DNS lookup.
3.1) nsswitch config
Run this command:
If you see the output:
then note that you are not using nsswitch.
Otherwise you see output like this:
Note down the words after ‘‘hosts:’’ as your ‘nsswitch methods’
3.2) nsswitch host: /etc/hosts
If you are using nsswitch, and if host was in your nsswitch methods , then check whether the host that’s failing is in your /etc/hosts file.
If it is, then go to Solution A and edit your /etc/hosts file.
3.3) nsswitch dns: /resolv.conf
If you are using nsswitch, and dns was not in your ‘nsswitch methods’ then its absence may be the problem. Try adding it to see if that resolves your issue.
If you are using nsswitch, and dns was in your ‘nsswitch methods’, then run this command:
Note the output as ‘dns servers in resolv.conf’ in the order they are seen in the ‘'/etc/resolv.conf’' file.
3.4) Check Nameserver
For the first item in your ‘dns servers in resolv.conf’ list, determine:
Is your DNS server IP address (‘DNSSIPA’) pointed to the localhost network?
Is your DNSSIPA pointed to your local network?
Is your DNSSIPA pointed to the internet?
To determine the answer to the above, follow the instructions below:
If the DNSSIPA matches: 127.0.0.x , where x is any number between 0 and 255 , then your DNS server is running locally. Proceed to Find local DNS server
If your DNSSIPA is in any of the following ranges: 10.0.0.0-10.255.255.255 , 172.16.0.0-172.31.255.255 , or 192.168.0.0-192.168.255.255 , then your DNSSIPA is pointed to a local network. Otherwise, it’s likely to be pointed at an internet address. If you’re still unsure run: dig +short @8.8.8.8 -x DNSSIPA , where DNSSIPA should be replaced with the actual IP address. If the output is empty then the IPA is pointed to your local network. If it is not empty, then it is pointed to the internet.
If your DNSSIPA is pointed at the internet, then proceed to the solution here. If that solution does not resolve, continue.
What Causes the DNS Lookup Failed Error?
After going through certain solutions and workarounds, we came to the conclusion as to why this error is triggered in the first place.
If you want to have your PC related issues fixed automatically and diagnose, list, and rectify any registry errors, we recommend that you try using the Restoro Repair Tool that can easily do all of this at a single click. It has been rated Great by Trustpilot so you don’t have to worry about anything.
- Network Issue: It is possible that your Network is being glitched or it is bugged due to which the DNS lookup Failed error is being triggered. Therefore, we suggest that you try and fix the network issues by running the troubleshooter as mentioned below.
- IP Address: Sometimes, the IP address might be blocked on the DNS server or it might have gotten blacklisted due to suspicious activities. Therefore, we suggest that you try and get around this error by trying to change your IP address.
- DNS cache: The DNS cache being stored on your computer can sometimes be corrupted which can end up causing the DNS loop failed issue. Therefore, we strongly suggest that you try and clear it out by flushing it completely.
- Chrome Extensions: The Chrome browser might have some faulty extensions installed due to which the connection might get derailed. Therefore, we suggest that you try and disable the Chrome extensions as mentioned below. The same goes for other browsers as well, you can try to block extensions and then check if doing so fixes the issue.
Now that we have taken you through almost all the listed reasons, it is about time that we start implementing the solutions.
Learn How To Fix DNS Lookup Failed Error
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.
Opera
A web browser that balances out stability, performance, a high level of customization, and low system requirements.
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 gladly 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.
Solution 4: Change the DNS Server
Another possible fix is to change the DNS Server address. To do this you must follow the below-indexed steps:
- Press the “Window + R” keys together to open up the “Run” dialog box.
- In the Run prompt, type in “ncpa.cpl” and press “Enter” to open up the Network Connections window.
- Your current network connection will now be visible to you, right-click on it and select “Properties”.
- Now select “Internet Protocol Version 4 (TCP/IPv4)” and click on “Properties”.
- Choose the option that says “Use the following DNS server addresses” and type in the fields below.
- Type in “8.8.8.8” in the Preferred DNS Server and “8.8.4.4” in the Alternative DNS Server box.
- Click on the “OK” button and close the other windows.
- Check to see if the DNS lookup Failed error is fixed.
Solution 7: Clear Chrome’s Browsing Data
The other thing that you can try is to clear Chrome’s data as chances are it might resolve the issue as well.
- Click on the 3 dots at the top-right corner in Google Chrome that says, “Customize and Control Google Chrome”
- From the drop-down menu hover your mouse over to the option “More Tools” and then click on “Clear Browsing Data”
- Now go to the “Advanced” tab and change the time range to “All Time”.
- Tickmark “Browsing History”, “Cookies” and “Cached Images and Files” checkboxes.
- Now click on the “Clear Data” button.
1. FLUSH DNS CACHE –
Table of Contents
Most of the operating system store the DNS data in their cache, It helps in establishing a connection to the ISP fluidly. Along with DNS records, an Operating system also stores information about sites that you have visited before in the form of cache. By flushing the DNS cache, we remove all the entries made by the Operating system
-> Procedure to Flush DNS Cache in Windows –
- Press Windows Key + R
- Type CMD and press Enter
- Type ipconfig /flushdnsand press enter.
This is the procedure to flush DNS cache in your Windows computer.
-> Procedure to Flush DNS Cache in MAC OS –
- Open Terminal Application
- Type sudo killall -HUP mDNSResponder(For MAC OS High Sierra and Sierra)
Solution 6: Disable Chrome’s Extensions
Some extensions might mess up your browser function. To rule out the possibility of an extension causing the error, we are going to disable all the extensions by following the procedure below:
If this resolved your issue, this means there is an extension that is causing the DNS Lookup Failure error. To figure out the culprit, enable the extensions one by one again until you come up with the issue again.
Solution 8: Change Your Browser
Once all the above fixes fail and the issue persists you should consider changing your browser. We would suggest switching to “Opera” as it is a very stable browser and has tons of built-in features and tools that can prove useful at times.
B) Disable iptables
Use systemctl disable (or whichever method of disabling services exists on your system) to disable iptables .
If it works (see Check Resolution), then it may be that IPTables is redirecting your requests to a different location.
In this case, you will need to determine why this IPTables rule exists and fix accordingly. The fix will be context-dependent.
Examples of legitimate reasons for doing this include:
1) Determine whether the Internet is accessible
First, check whether you have internet access at all. Surprisingly often, this is the root cause.
To determine this without relying on DNS lookups, run:
If you see output similar to this:
then you have internet access.
If you do not, then the root cause is that you don’t.
2. Change Default DNS Server Address –
Sometimes flushing the DNS cache is just not enough for fixing DNS lookup failed error. Alternatively, you can modify the DNS address of your network connection to Google’s DNS. Make sure to restart the computer after changing DNS details.
-> Procedure to change DNS in Windows –
- Open Control Panel
- Click Network and Internet > Network and Sharing Center > Change adapter settings.
- Select the connection for which you want to configure Google Public DNS. For example:
- To change the settings for an Ethernet connection, right-click Local Area Connection >Properties.
- To change the settings for a wireless connection, right-click Wireless Network Connection >Properties.
-> Procedure to change DNS in MAC OS –
- Open System preferences
- Click the network icon
- Click on the advance button on your currently connected network.
- Click on DNS and add DNS records there as shown in the image below.
- Click on OK and then click on Apply and You are done.
1. Consider using a different browser
Solution 1: Use Network Troubleshooter
Running the Network Troubleshooter might very well resolve the issue. Follow the steps below to access it:
- Press the “Windows + I” buttons on your keyboard simultaneously to open the settings.
- Once in the Windows Settings, click on the “Network & Internet” option.
- Now select “Network Troubleshooter” under Advanced Network Settings. After diagnosing is complete, the troubleshooter should display solutions in case any problems were found.
This should help resolve any possible issues with network settings and might resolve the DNS Lookup Failure error.
End Of The Line –
These were the methods you can use to fix the DNS Lookup Failed error on your computer. If these methods weren’t able to fix your problem, Restart your router or Reset your router, If it still does not work then Verify if your ISP is up and running, You can reach your IPS support team for that.
If you liked our post, PLEASE 🙏🏽 share it with your friends. Don’t forget to comment if you have any query or If you faced any problem while following the methods.
This issue happens when a DNS lookup is performed on a Linux system, and an IP address is not returned.
2) Determine whether all DNS lookups are failing
Run a DNS lookup against a stable site:
The output should look similar to this:
Now run this command:
Compare the output of the two dig commands you just ran.
The first two numbers in the IP address in the last line ( 216.58 in the above example output) should match in your output.
If they match, then DNS lookup is working for at least some DNS entries.
If they do not match, then DNS lookup is not working on your host.
Note the above outcome down as ‘DNS not working for all’ or ‘DNS working for some’, as it will be used later.
4) Check IPTables / Netfilter
Run this script:
If this produces any output lines at all, it may be that IPTables/NetFilter is diverting the DNS request and causing the issue. Try going to Solution B to see if that works.
If you are unsure whether IPTables/NetFilter are in place at all on your system, see here.
Your IPTables output might suggest that requests to port 53 are being diverted to another local DNS server (Vagrant’s landrush plugin does this, for example). See the next step for more on this.
Check Resolution
Try running dig or curl against any domains that caused issues before, eg
If they appear to work now, then retry your original application.
If your original application still fails, it may have cached the bad lookup. A restart of the application may help.
Whether this fully resolves your issue will depend on the intention behind the design of the network you run on. If you are not fully responsible for it, then you will need to take the information you have gathered here to whoever is responsible for it.
Solution 3: Flush the DNS Cache
Flushing the DNS cache can potentially fix the DNS lookup failure error, follow the method below to do so:
3. Open the Internet Connections Troubleshooter
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.
If you’re a fan of Chromium-based browsers like Google Chrome and Microsoft Edge, then we recommend you switch to Opera.
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.
It also comes with extremely useful tools, such as a built-in ad-blocker, or a VPN, allowing not just an error-free browsing experience, but also a private one.
Fixing the DNS Lookup Failed Issue:
C) Change DNS Server in /etc/resolv.conf
As root, replace the IP address of the DNS server on the first line beginning nameserver with a public DNS server that is likely to be available, eg Google’s DNS server on: 8.8.8.8 .
6. Restart the Network Stack
- Enter Command Prompt in the search box.
- Right-click Command Prompt in Cortana and select Run as administrator.
- Input netsh winsock reset catalog in the Command Prompt and press Enter.
- Enter netsh winsock reset catalog in the Prompt, and press the Return button.
- Close the Command Prompt, and restart Windows.
Some users might need to restart a corrupted network stack to fix the DNS lookup failed error.
The above resolutions will probably resolve the DNS lookup failed error for most uses so that they can open webpages in Chrome. Some of the above resolutions might also fix other DNS error messages.
Still having issues? Fix them with this tool:
DNS Lookup Failed is one of those errors which you might have faced ample of times while using Google Chrome browser. DNS Lookup Failed is one of the issues which arise due to improper functioning of your Internet Service provider or If the DNS Server stops responding. Whatever may be the cause, Today through this post we will be giving all answers to the question – How to fix DNS Lookup Failed?
The guide we are publishing will work on all Windows and MAC OS.
These are the actionable procedures which you can follow to fix the DNS Lookup failed error in your web browser –
Solutions List
Detailed Steps
5. Flush the DNS
- Click the Type here to search button on Windows 10’s taskbar.
- Enter ‘cmd’ as the search keyboard.
- Right-click the Command Prompt and select Run as administrator.
- Input ‘ipconfig /flushdns’ in the Command Prompt as shown below, and press the Enter key.
Flushing the DNS cache will clear that cache, which is a straightforward potential resolution for the DNS lookup failure error.
Читайте также: