DNS and timeout errors in the browser: what the codes mean and what to do

Instead of a page the browser shows a code: DNS_PROBE_FINISHED_NXDOMAIN, ERR_NAME_NOT_RESOLVED, ERR_CONNECTION_TIMED_OUT or “No internet connection”. The codes mean different things: in one the site’s address was not found, in another nobody answered in time, in another there is no network at all. Below: what each one means per Chrome’s help and the Chromium source, and the order to follow through the Chrome, Microsoft and Google help pages.

In short. First check whether any other site opens. If none does, it is the network (Wi-Fi, router, provider), not the site. If only one fails: DNS_PROBE_FINISHED_NXDOMAIN and ERR_NAME_NOT_RESOLVED say the site name could not be turned into an address (a typo, the site is gone, or a DNS fault), ERR_CONNECTION_TIMED_OUT says the connection could not be established in time. Then, per Chrome’s help: reload the page, check the internet connection, update and restart Chrome, open the page in Incognito, turn off extensions, delete browsing data, check the antivirus and firewall.

We make Mayak. A VPN app for Android; it does not cure browser errors, but when there is a network and something does not open, it can check the connection and say where the break is. 3 free days, no card needed.

What each code means

The meanings below are not guesses: they come from two places, Chrome’s help and comments in the Chromium source (the browser takes these texts from there). Chrome’s help does not describe every code in the table (it has nothing on DNS_PROBE_…), so we took those meanings from the source.

CodeWhat it meansSourceWhere to start
DNS_PROBE_FINISHED_NXDOMAIN After a name failure Chrome probes DNS; per a comment in the source: “the DNS servers are working fine, so the domain must not exist” Chromium source, net_error_info.h Check the address for typos, open another site
ERR_NAME_NOT_RESOLVED The site name could not be resolved; Chrome’s help: the name does not exist or now has a different IP address Chrome help; Chromium source, net_error_list.h Open another site: if none opens, it is the network or DNS
DNS_PROBE_FINISHED_BAD_CONFIG Per a comment in the source: DNS is misconfigured, or the servers are down or broken Chromium source, net_error_info.h Check the DNS servers: the Windows steps and changing DNS below
DNS_PROBE_FINISHED_NO_INTERNET Per a comment in the source: there is no internet connection Chromium source, net_error_info.h Check the network: Wi-Fi, router, cable
ERR_INTERNET_DISCONNECTED Chrome’s help: the device is not connected to the internet Chrome help; Chromium source Same: network, router, airplane mode
ERR_CONNECTION_TIMED_OUT Chrome’s help: the page took too long to connect; the internet may be too slow or the page too busy Chrome help; Chromium source Reload the page, try another network and another site
ERR_CONNECTION_RESET Chrome’s help: something interrupted the connection, for example an unstable internet; the causes it lists include an outdated browser, a VPN problem and security software that stops the page Chrome help Update Chrome, turn the VPN off for a minute, check the antivirus

In Russian-language browsers such pages are often titled with the Russian equivalents of “Cannot establish a connection to the site” or “No internet connection”. We did not match which title of which browser corresponds to which code.

First: the network or the site

Chrome’s help starts with a question that saves time: is one site affected or several. If several fail, it advises checking your internet connection. On a Windows computer Microsoft’s help says the same: if other devices on the same network fail too, the router or the provider is the likelier cause, not your computer.

  • No site opens, and other devices on the same network fail too — look at the network: “Connected, but no internet access”; for a phone, “No internet on your phone”.
  • One site does not open — read the code in the table above and follow the steps.
  • Only some sites fail, the rest are fine — the browser error cannot tell you the cause; do not guess, compare with another network, for example a hotspot from a phone.

Nine steps from Chrome’s help

Chrome’s help “Fix connection and loading errors in Chrome” gives nine steps; the order is the same as in it.

  1. Check the address and reload the page. Make sure there is no mistake in the URL.
  2. Check the internet connection. The device must be online over Wi-Fi or ethernet; reboot the modem and router or contact your provider. On a public network, such as a café’s, sign-in may be requested through a portal page.
  3. Update and restart Chrome.
  4. Open the page in Incognito mode.
  5. Turn off extensions.
  6. Delete browsing data (the cache is part of it).
  7. Check your firewall and antivirus: they must not interfere with the connection.
  8. Free up device memory: close unused tabs and tasks.
  9. Reset Chrome settings.

This help says nothing about DNS servers or proxies: we take those from the Microsoft and Google help below. For the details of each step, including menu paths, see the help itself; we give only the names of the steps.

If that did not help: Windows commands, per Microsoft’s help

Microsoft’s help on Wi-Fi problems in Windows (read on 21 November 2026) advises the following for the “no internet access” case. The commands are run in Command Prompt as administrator.

  • Turn Wi-Fi off and on, and reconnect.
  • Run ipconfig /release and ipconfig /renew, then ipconfig /flushdns. The last one clears the DNS name cache.
  • Turn off a manually set proxy: “Settings” → “Network & internet” → “Proxy”.
  • Check your address: 169.254.x.x means Windows did not get an address from the router; then check whether address assignment (DHCP) is on in the router.
  • Find the DNS server address with ipconfig /all and ping it; if there is no reply, the help advises trying a different DNS server.

The same help has more drastic steps too: netsh winsock reset and netsh int ip reset, reinstalling the adapter driver and “Network reset”, which Microsoft calls a last resort: afterwards you may have to reinstall VPN software.

Changing the DNS server: what Google says

If it turned out that the DNS server does not answer, one step is to change it. What that looks like is shown by the Google Public DNS page (read on 21 November 2026):

  • the IPv4 addresses are 8.8.8.8 and 8.8.4.4; configure at least two, and not the same address twice;
  • first write down your current settings so you can revert if something goes wrong;
  • Windows (the page covers only Windows 10): “Control Panel” → “Network and Internet” → “Network and Sharing Center” → “Change adapter settings” → the connection’s properties → IPv4 → “Use the following DNS server addresses”;
  • Android 9 and later: “Settings” → “Network & internet” → “Advanced” → “Private DNS”, provider hostname dns.google;
  • a check: open a site by name and by address; if it opens by address but not by name, the cause, in Google’s words, is most likely your DNS configuration.

This is an example of what changing DNS looks like, not our advice: we did not measure Google Public DNS and do not know how it behaves from your network. Private DNS on Android and VPNs have an article of their own: “Private DNS not accessible on Android”.

If the error appears only with a VPN on

Chrome’s help lists a VPN problem among the causes of ERR_CONNECTION_RESET. Microsoft’s documentation of the Windows connectivity indicator adds that VPNs and third-party software can intercept, misroute or delay the check Windows uses to decide whether there is internet. The simplest test is a comparison: turn the VPN off for a minute and open the same page.

If it opens without the VPN and not with it: “VPN connects but there is no internet”, “Private DNS not accessible on Android” and “How to check that a VPN works and does not leak DNS”. We have no measurements of our own for these browser codes.

The error only with a VPN on? Test what a VPN does with your network: 3 free days, no card needed. When there is a network and something does not open, the app can check the connection and say where the break is.

What happens next.

  1. Create an account in the dashboard: email and password, no card.
  2. Install the app: from Google Play or as a file from our site. On the first connection Android shows a connection request window: that is how it should be.
  3. Press one button. If something does not open, tap “Check connection”: the app asks the network itself.

What we do not promise

  • That the steps from the help pages will bring back your particular site: some causes sit on the site’s side or the provider’s, and we cannot see them.
  • That changing DNS will help: it cures only a DNS fault, and that is checked by comparing opening by name and by address.
  • That Google Public DNS is reachable from your network and will suit you: we did not measure it and do not recommend it.
  • That a VPN, ours included, will open some particular site.

What we checked

  • Chrome’s help “Fix connection and loading errors in Chrome” and the descriptions of codes in Chrome’s help — read on 21 November 2026.
  • The Chromium source: net/base/net_error_list.h (the ERR_… descriptions) and components/error_page/common/net_error_info.h (the DNS_PROBE_… descriptions) — 21 November 2026.
  • Microsoft’s help on Wi-Fi problems in Windows and Microsoft’s documentation of the Network Connectivity Status Indicator (NCSI) — 21 November 2026.
  • Google’s Public DNS page “Get Started” — 21 November 2026.

What we do not know

  • What the error pages look like in your browser and which title stands for which code: we did not match them.
  • What share of cases is DNS, what share the network and what share the site itself: we have no such measurements, neither for these codes nor from the app’s reports.
  • The phrase “DNS server not responding” is most often searched for Windows; the Microsoft help we read does not contain that exact phrase, but it has the step “find the DNS server and ping it”.
  • We did not walk through the help steps in a live browser or on a computer; menu items rendered in Russian are our translation of the English help.

Short answers

What does DNS_PROBE_FINISHED_NXDOMAIN mean? Per a comment in the Chromium source: the DNS servers are working, so the domain apparently does not exist. Check the address for typos and open another site.

What does ERR_NAME_NOT_RESOLVED mean? The site name could not be resolved. Chrome’s help: the name does not exist or now has a different IP address.

What does ERR_CONNECTION_TIMED_OUT mean? The page took too long to connect: the internet may be too slow or the page too busy (Chrome’s help).

“DNS server not responding”: what to do? Find the DNS server address with ipconfig /all and ping it; if there is no reply, try a different DNS server (Microsoft’s help).

Will changing DNS help? Only if the cause is DNS. A check: open a site by name and by address; if it opens by address but not by name, DNS is the likelier cause.

Try Mayak

A secure connection for Android, and articles where other people’s words come with a publication and a date, and our own numbers come with a measurement. 3 days free, no card needed.

The account is created right in the app. 3 free days once you sign up with your email.