504 dns look up failed ошибка

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.

Description

This article describes a technical tip to prevent and/or troubleshoot “504 DNS lookup Failed” errors in case the Explicit Web Proxy feature is configured in a non-management VDOM.

Solution

When configured as an Explicit Web Proxy server, the FortiGate typically needs to perform Domain Name resolution in order to fulfill clients’ requests. To do so, the FortiGate relies on the DNS system settings which are configured in the “config system dns” section. This works fine when the Explicit Web Proxy feature is configured in the management VDOM (‘root’ VDOM by default) since this VDOM inherits the DNS settings configured globally.

In case the Explicit Web Proxy is configured in a non-management VDOM, the DNS configuration as defined in the “config system dns” section does not apply. As a result, browsing actions issued by the clients will end by default with a “504 DNS look up failed” error such as the following:

Bypassing the issue consists in configuring the DNS settings at the VDOM level (in the VDOM the Explicit Web Proxy feature is configured) so that the FortiGate can perform Domain Name resolution successfully. This can be done by using the “config system vdom-dns” section specific to the VDOM. At the minimum, DNS needs to be enabled for the VDOM using “set vdom-dns enable”  and an IPv4 or IPv6 primary address defined using “set primary <dns_ipv4>” or “set ip6-primary <dns_ipv6>”.

config system vdom-dns

   set ip6-primary <dns_ipv6>

   set ip6-secondary <dns_ip6>

   set primary <dns_ipv4>

   set secondary <dns_ip4>

   set source-ip <ipv4_addr>

   set vdom-dns {disable | enable}

end    

The 504 Gateway Timeout error is an HTTP status code that means that one server didn’t receive a timely response from another server that it was accessing while attempting to load the web page or fill another request by the browser.

In other words, 504 errors usually indicate that a different computer, one that the website you’re getting the message on doesn’t control but relies on, isn’t communicating with it quickly enough.

Are You the Web Manager? See the Fixing 504 Errors on Your Own Site section further down the page for some things to consider on your end.

How You Might See the 504 Error

Individual websites are allowed to customize how they show «gateway timeout» errors, but here are the most common ways you’ll see one spelled out:

• 504 Gateway Timeout
• HTTP 504
• 504 ERROR
• Gateway Timeout (504)
• HTTP Error 504 — Gateway Timeout
• Gateway Timeout Error

A 504 Gateway Timeout error shows up inside the internet browser window, just like normal web pages do. There might be a site’s familiar headers and footers and a nice, English message on the page, or it could show up on an all-white page with a big 504 at the top. It’s all the same message, regardless of how the website happens to show it.

Causes of 504 Gateway Timeout Errors

Most of the time, a 504 Gateway Timeout error means that whatever other server is taking so long that it’s «timing out,» is probably down or not working properly.

Since this error is usually a network error between servers on the internet or an issue with an actual server, the problem probably is not with your computer, device, or internet connection.

That said, there are a few things you can try, just in case:

How to Fix the 504 Gateway Timeout Error

1. Retry the web page by selecting the refresh/reload button, pressing F5, or trying the URL from the address bar again.

   Even though the 504 Gateway Timeout error is reporting an error outside of your control, it might only be temporary.

2. Restart all of your network devices. Temporary problems with your modem, router, switches, or other networking hardware could be causing the 504 Gateway Timeout issue you’re seeing. Just restarting these devices could help.

   While the order you turn off these devices isn’t important, the order that you turn them back on is. In general, you want to turn devices on from the outside-in. If you’re not sure what that means, check out the link at the beginning of this step for a complete tutorial.

3. Check the proxy server settings in your browser or application and make sure they’re correct. Incorrect proxy settings can cause 504 errors.

   Most computers don’t have proxy settings at all, so if yours are empty, just skip this step.

   See Proxy.org for an updated, respected list of proxy servers that you can choose from.

4. Change your DNS servers, especially if all the devices on your network are getting the same error. It’s possible that the 504 Gateway Timeout error you’re seeing is caused by an issue with the DNS servers you happen to be using.

   Unless you’ve previously changed them, the DNS servers you have configured right now are probably the ones automatically assigned by your ISP. Others are also available to choose from. See our Free & Public DNS Servers list for options.

5. If nothing has worked up to this point, contacting the website is probably the next best thing to do. There’s a good chance the website administrators are already working to fix the root cause of the 504 Gateway Timeout error, assuming they’re aware of it, but there’s nothing wrong touching base with them.

   Most major sites have social networking accounts they use to help support their services and some even have telephone numbers and email addresses.

   If it’s starting to look like the website might be giving a 504 error for everyone, searching Twitter for real-time information about the site’s outage is often helpful. The best way to do this is to search for #websitedown on Twitter. For example, if Facebook might be down, search #facebookdown.

6. Contact your internet service provider. It’s very likely at this point, after following all the troubleshooting above, that the 504 Gateway Timeout that you’re seeing is a problem caused by a network issue that your ISP is responsible for.

   How to Talk to Tech Support

7. Come back later. You’ve exhausted all your options at this point and the 504 Gateway Timeout error is either in the hands of the website or your ISP to correct. Check back with the site regularly. No doubt it’ll start working again soon.

Fixing 504 Errors on Your Own Site

A lot of times this isn’t your fault at all, but it’s not the user’s either. Start by checking that your server can properly resolve all the domains that your applications require access to.

Very heavy traffic might result in your server serving a 504 error, even though a 503 would probably be a bit more accurate.

In WordPress specifically, 504: Gateway Timeout messages are sometimes due to corrupted databases. Install WP-DBManager and then try the «Repair DB» feature, followed by «Optimize DB,» and see if that helps.

Also, make sure your HTACCESS file is correct, especially if you have just reinstalled WordPress.

Finally, consider contacting your hosting company. It’s possible that the 504 error that your website is returning is due to an issue on their end that they’ll need to resolve.

More Ways You Might See a 504 Error

A Gateway Timeout error, when received in Windows Update, generates a 0x80244023 error code or the message WU_E_PT_HTTP_STATUS_GATEWAY_TIMEOUT.

In Windows-based programs that inherently access the internet, a 504 error might show up in a small dialog box or window with the HTTP_STATUS_GATEWAY_TIMEOUT error and/or with a The request was timed out waiting for a gateway message.

A less common 504 error is Gateway Time-out: The proxy server did not receive a timely response from the upstream server, but the troubleshooting (above) remains the same.

Errors Like 504 Gateway Timeout

A number of error messages are similar to the 504 Gateway Timeout error because they all occur on the server side. A few include the 500 Internal Server Error, the 502 Bad Gateway error, and the 503 Service Unavailable error, among a few others.

There are also HTTP status codes that aren’t server-side, but instead client-side, like the commonly seen 404 Not Found error. Several others exist as well, all of which you can see in our HTTP Status Code Errors page.

Thanks for letting us know!

The 504 Gateway Timeout error is an HTTP status code that means that one server didn’t receive a timely response from another server that it was accessing while attempting to load the web page or fill another request by the browser.

In other words, 504 errors usually indicate that a different computer, one that the website you’re getting the message on doesn’t control but relies on, isn’t communicating with it quickly enough.

Are You the Web Manager? See the Fixing 504 Errors on Your Own Site section further down the page for some things to consider on your end.

How You Might See the 504 Error

Individual websites are allowed to customize how they show «gateway timeout» errors, but here are the most common ways you’ll see one spelled out:

• 504 Gateway Timeout
• HTTP 504
• 504 ERROR
• Gateway Timeout (504)
• HTTP Error 504 — Gateway Timeout
• Gateway Timeout Error

A 504 Gateway Timeout error shows up inside the internet browser window, just like normal web pages do. There might be a site’s familiar headers and footers and a nice, English message on the page, or it could show up on an all-white page with a big 504 at the top. It’s all the same message, regardless of how the website happens to show it.

Causes of 504 Gateway Timeout Errors

Most of the time, a 504 Gateway Timeout error means that whatever other server is taking so long that it’s «timing out,» is probably down or not working properly.

Since this error is usually a network error between servers on the internet or an issue with an actual server, the problem probably is not with your computer, device, or internet connection.

That said, there are a few things you can try, just in case:

How to Fix the 504 Gateway Timeout Error

1. Retry the web page by selecting the refresh/reload button, pressing F5, or trying the URL from the address bar again.

   Even though the 504 Gateway Timeout error is reporting an error outside of your control, it might only be temporary.

2. Restart all of your network devices. Temporary problems with your modem, router, switches, or other networking hardware could be causing the 504 Gateway Timeout issue you’re seeing. Just restarting these devices could help.

   While the order you turn off these devices isn’t important, the order that you turn them back on is. In general, you want to turn devices on from the outside-in. If you’re not sure what that means, check out the link at the beginning of this step for a complete tutorial.

3. Check the proxy server settings in your browser or application and make sure they’re correct. Incorrect proxy settings can cause 504 errors.

   Most computers don’t have proxy settings at all, so if yours are empty, just skip this step.

   See Proxy.org for an updated, respected list of proxy servers that you can choose from.

4. Change your DNS servers, especially if all the devices on your network are getting the same error. It’s possible that the 504 Gateway Timeout error you’re seeing is caused by an issue with the DNS servers you happen to be using.

   Unless you’ve previously changed them, the DNS servers you have configured right now are probably the ones automatically assigned by your ISP. Others are also available to choose from. See our Free & Public DNS Servers list for options.

5. If nothing has worked up to this point, contacting the website is probably the next best thing to do. There’s a good chance the website administrators are already working to fix the root cause of the 504 Gateway Timeout error, assuming they’re aware of it, but there’s nothing wrong touching base with them.

   Most major sites have social networking accounts they use to help support their services and some even have telephone numbers and email addresses.

   If it’s starting to look like the website might be giving a 504 error for everyone, searching Twitter for real-time information about the site’s outage is often helpful. The best way to do this is to search for #websitedown on Twitter. For example, if Facebook might be down, search #facebookdown.

6. Contact your internet service provider. It’s very likely at this point, after following all the troubleshooting above, that the 504 Gateway Timeout that you’re seeing is a problem caused by a network issue that your ISP is responsible for.

   How to Talk to Tech Support

7. Come back later. You’ve exhausted all your options at this point and the 504 Gateway Timeout error is either in the hands of the website or your ISP to correct. Check back with the site regularly. No doubt it’ll start working again soon.

Fixing 504 Errors on Your Own Site

A lot of times this isn’t your fault at all, but it’s not the user’s either. Start by checking that your server can properly resolve all the domains that your applications require access to.

Very heavy traffic might result in your server serving a 504 error, even though a 503 would probably be a bit more accurate.

In WordPress specifically, 504: Gateway Timeout messages are sometimes due to corrupted databases. Install WP-DBManager and then try the «Repair DB» feature, followed by «Optimize DB,» and see if that helps.

Also, make sure your HTACCESS file is correct, especially if you have just reinstalled WordPress.

Finally, consider contacting your hosting company. It’s possible that the 504 error that your website is returning is due to an issue on their end that they’ll need to resolve.

More Ways You Might See a 504 Error

A Gateway Timeout error, when received in Windows Update, generates a 0x80244023 error code or the message WU_E_PT_HTTP_STATUS_GATEWAY_TIMEOUT.

In Windows-based programs that inherently access the internet, a 504 error might show up in a small dialog box or window with the HTTP_STATUS_GATEWAY_TIMEOUT error and/or with a The request was timed out waiting for a gateway message.

A less common 504 error is Gateway Time-out: The proxy server did not receive a timely response from the upstream server, but the troubleshooting (above) remains the same.

Errors Like 504 Gateway Timeout

A number of error messages are similar to the 504 Gateway Timeout error because they all occur on the server side. A few include the 500 Internal Server Error, the 502 Bad Gateway error, and the 503 Service Unavailable error, among a few others.

There are also HTTP status codes that aren’t server-side, but instead client-side, like the commonly seen 404 Not Found error. Several others exist as well, all of which you can see in our HTTP Status Code Errors page.

Thanks for letting us know!