Что такое dns probe finished nxdomain как исправить

• 
  Помощь

• 
  Хостинг

• 
  Сайт не работает

• 
  Ошибка DNS PROBE FINISHED NXDOMAIN
  

Ошибка «DNS PROBE FINISHED NXDOMAIN» связана с работой DNS-сервера вашего интернет-провайдера. Возможно, служба DNS работает нестабильно, некорректно указаны адреса DNS-серверов или возникла проблема с сетевым оборудованием на физическом уровне.

Устранение ошибки

Для устранения ошибки следуйте инструкции ниже:

1. 1.

   Очистите кеш браузера. Браузер мог закешировать страницу вашего сайта в момент, когда он был недоступен, и показывает устаревшую информацию. Для этого перейдите по адресу вашего сайта и нажмите «Ctrl» + «F5».
   Если очистка кеша не помогла, перейдите к следующему шагу.

2. 2.

   Проверьте, активен ли ваш домен в Личном кабинете:

   
   

   Зеленый значок означает, что домен активен.

   Если домен активен, но сайт недоступен, перейдите к следующему шагу.
3. 3.

   Проверьте доступность вашего сайта через сайт croxyproxy. Введите имя сайта и нажмите GO. Если сайт доступен, значит проблема возникла на стороне интернет-провайдера. Подождите, пока обновятся DNS-серверы провайдера. Обычно это происходит раз в 24 часа. DNS-серверы интернет-провайдеров обновляются с разной периодичностью. То есть с одного интернет-провайдера ваш сайт может открываться, а с другого — быть недоступен.

   Также рекомендуем проверять доступность сайта с разных точек мира при помощи сервиса Бесплатная проверка доступности сайта из различных частей мира.

   Важно: Чтобы проверить IDN-домен (например: ваш-сайт.рф), переведите его в Punycode (в формат XN—-7SBBF2B7BJ7B.XN–P1AI) и только затем вводите в строку на сайте croxyproxy.

4. 4.

   Если ваш сайт недоступен через сайт croxyproxy, проверьте, корректные ли DNS указаны для домена. Узнать, какие DNS прописаны для домена можно по инструкции: Как узнать, какие DNS-серверы прописаны для домена? Узнать, какие DNS-серверы следует использовать в REG.RU, можно по инструкции: Какие DNS-серверы прописать для домена?

   Если для домена прописаны некорректные DNS, измените их по инструкции: Как прописать DNS для домена в личном кабинете REG.RU?
5. 5.

   Если вы не хотите ждать, рекомендуем прописать DNS-серверы компании Google в настройках сетевого подключения. Для этого на 6 шаге инструкции поставьте галочку Использовать следующие адреса DNS-серверов и пропишите два DNS-сервера: 8.8.8.8 и 8.8.4.4.

   Для быстрой проверки доступности сайта укажите DNS-серверы компании Google, обычно они обновляются быстрее других (3-4 часа).

   После этого очистите кеш браузера.

Готово, после обновления DNS-серверов сайт должен отображаться корректно.

Спасибо за оценку!
Как мы можем улучшить статью?

Нужна помощь?
Напишите в службу поддержки!

• Как исправить ошибку 

В статье мы расскажем, из-за чего появляется «ошибка dns probe finished nxdomain» и как исправить эту ошибку.

Ошибка DNS-сервера

Ваш браузер показывает ошибку «dns probe finished nxdomain»? Что это значит? Чаще всего ошибка возникает на локальном уровне или из-за нарушений в работе DNS-серверов интернет-провайдера. В первом случае скорость решения проблемы зависит от действий пользователя. Во втором случае после исправления ошибки придется подождать обновления DNS-серверов.

Возникновение ошибки может быть связано со следующими причинами:

• браузер закешировал страницу вашего сайта в момент, когда он был недоступен, и теперь показывает устаревшую информацию;

• случайный баг в операционной системе;

• блокировка ресурса антивирусом или брандмауэром;

• проблемы с сетевым оборудованием: например,с работой Wi-Fi роутера;  

• неверно указаны DNS-серверы для домена;

• нестабильная работа службы DNS;

• проблема с DNS-серверами на стороне хостинг-провайдера сайта и др.

«Dns probe finished nxdomain» может встретиться при работе с любым популярным браузером (Google Chrome, Яндекс, Mozilla Firefox и др.), а также на любой версии операционной системы Windows. 

Рассмотрим способы, которыми можно устранить ошибку. 

Как исправить ошибку 

В зависимости от причины нарушения работы DNS-серверов, для устранения «dns error» подойдет один из способов. С первого взгляда определить, в чём кроется причина ошибки сложно, поэтому попробуйте каждый способ:

1. Очистите кеш браузера: перейдите по адресу вашего сайта и нажмите «Ctrl» + «F5». Если этот способ не помог, переходите к следующему.

2. Откройте сайт через другой браузер. Если он по-прежнему недоступен, переходите к способу №3.

3. Перезагрузите компьютер и вновь зайдите на нужный ресурс. Если ошибка не устранилась, перейдите к следующему способу.  

4. Перезагрузите Wi-Fi маршрутизатор: отключите его от питания на несколько минут и снова подключите обратно. Если сайт не работает, переходите к следующему способу.

5. Отключите антивирус и брандмауэр, если у вас ОС Windows. Если это помогло решить проблему, добавьте браузер в исключения антивируса и брандмауэра, и проблема не повторится. Если нет, попробуйте следующий способ.

6. Проверьте активность вашего домена. Для этого в Личном кабинете найдите ваш домен. Если домен активен, перейдите к следующему способу.

1. Проверьте доступность сайта через сайт cameleo: укажите адрес вашего сайта и кликните GO. Если система покажет, что сайт доступен, значит проблема возникла на стороне интернет-провайдера. В этом случае дождитесь обновления DNS-серверов провайдера. Обычно DNS обновляются один раз в сутки, проверьте доступность сайта через 24 часа с обнаружения проблемы.

Проверить доступность помогает не только один сайт cameleo.xyz, но и сервис бесплатной проверки доступности сайта из различных частей мира. Если сайт недоступен и через этот ресурс, переходите к шагу №8.  

1. Проверьте, какие DNS-серверы прописаны для домена. Для этого:

1. Перейдите на страницу сервиса Whois. Затем введите имя вашего домена и нажмите Проверить:

1. Пара DNS-серверов домена указана в строках «nserver»:

 

Если для домена прописаны некорректные DNS, выберите один из двух способов:

• Измените их по инструкции Как указать (изменить) DNS-серверы для домена. DNS-серверы обновятся в течение 24 часов.

• Если вам нужно, чтобы сайт начал работать как можно быстрее, настройте DNS-серверы компании Google: 8.8.8.8 и 8.8.4.4. DNS обновятся в течение 3-4 часов. 

Если у вас операционная система Windows, это можно сделать через параметры подключения TCP/IP по инструкции.

Готово. Когда DNS-серверы хостинг-провайдера обновятся, сайт должен отображаться корректно.

Если вы попробовали все способы, но сайт не заработал — вам поможет служба поддержки 2domains. 

For those of you working with websites on a regular basis, errors specific to the CMS such as the white screen of death or database connection errors are somewhat common occurrences. But another subset of errors you will probably stumble upon are those tied to your internet connection and DNS.

A very common error that Google Chrome users get when trying to browse to a web page is “This site can’t be reached – Server IP address could not be found,” together with DNS_PROBE_FINISHED_NXDOMAIN. This can be downright frustrating as suddenly you can’t browse to your website or perhaps even anywhere at all. 😫

If you’re seeing this error while trying to get to your site, don’t worry, this is fairly easy to fix. Check out the recommendations below on how to get connected again. This can also work for other browsers, such as Firefox, Edge, etc.

Check Out Our Video Guide To Fixing The DNS_PROBE_FINISHED_NXDOMAIN Error

What Is DNS_PROBE_FINISHED_NXDOMAIN?

The reason for DNS_PROBE_FINISHED_NXDOMAIN is typically due to a misconfiguration or problem with your DNS. DNS is short for Domain Name System, which helps direct traffic on the internet by connecting domain names with actual web servers. Essentially, it takes a human-friendly request – a domain name like kinsta.com – and translates it into a computer-friendly server IP address – like 216.3.128.12.

When a user enters a URL in their web browser, DNS gets to work to connect that URL to the IP address of the actual server. This is called DNS name resolution and involves a DNS recursor querying various nameservers to figure out the actual IP address of a server.

If DNS fails to resolve the domain name or address then you might receive the DNS_PROBE_FINISHED_NXDOMAIN error. The NXDOMAIN part stand stands for Non-Existent Domain. Read more about DNS and how it works.

Error Code	DNS_PROBE_FINISHED_NXDOMAIN
Error Type	DNS error
Error Variations	This site can’t be reached Hmm. We’re having trouble finding that site Hmmm… can’t reach this page Safari Can’t Find the Server
Error Causes	Internet connection error Firewall is blocking access DNS misconfiguration DNS not yet propagated Unresponsive server

What Does the DNS_PROBE_FINISHED_NXDOMAIN Error Look Like on Browsers?

There are a couple different variations of this error depending upon the browser you’re running.

Google Chrome

In Google Chrome this error will show as DNS_PROBE_FINISHED_NXDOMAIN (as seen below), highlighting that this site can’t be reached, followed by server IP address could not be found.

This site can’t be reached or This webpage is not available.

Mozilla Firefox

In Mozilla Firefox it will simply show as Hmm. We’re having trouble finding that site (as seen below).

We can’t connect to the server at domain.com.

Microsoft Edge

In Microsoft Edge, it will simply show as Hmmm… can’t reach this page (as seen below). Which isn’t very helpful.

Make sure you’ve got the right web address: domain.com.

Safari

In Safari, it will simply show as Safari Can’t Find the Server (as seen below).

Safari can’t open the page “domain.com” because Safari can’t find the server “domain.com”.

Main Causes of the DNS_PROBE_FINISHED_NXDOMAIN Error

As mentioned, this error happens when the Domain Name System cannot resolve a website’s URL into an IP address. The causes for this could be:

• You typed the site name incorrectly into the search bar.
• There is an internet connection error preventing your access.
• Your firewall is blocking access to the website.
• An antivirus or a VPN is interfering with your network settings.
• The domain has expired or is not registered.
• Your DNS settings are not configured the right way.

How to Fix DNS_PROBE_FINISHED_NXDOMAIN on Desktop

Here are some recommendations and things to check to fix the error (sorted in order by most common reasons we see):

1. Release and Renew IP Address

Due to the fact that this is usually a client-side DNS issue, the very first thing you should do is try releasing and renewing the IP address on your computer. This also includes flushing your local DNS cache, which is similar to browser cache.

Windows

In Windows simply open up Command Prompt by pressing the Windows logo key and R. Then type “cmd” and hit Enter.

Type in ipconfig /release and hit Enter. This will release your current IP address.

Then type in ipconfig /flushdns and hit Enter. This will flush your local DNS cache. You should see a “Successfully flushed the DNS resolver Cache” if it worked.

Then type in ipconfig /renew and hit Enter. This will renew your IP address.

You might also try resetting your IP settings and Winsock catalog with the following commands: netsh int ip set dns and netsh winsock reset.

An alternative way to flush and renew your DNS is simply by disabling your network adapter and re-enabling it.

Mac

To release and renew your IP address on a Mac, go to System Preferences…

Click on the network icon and then click “Advanced.”

Click the TCP/IP tab heading if you aren’t already in there. Then click on the “Renew DHCP” lease button.

Just like we did above in Windows, Mac users can also clear their local DNS cache. Although this is done in a different place. Go to Utilities and then click on “Terminal.”

Enter in the following command:

dscacheutil -flushcache

Note: There is no success message on Macs.

2. Restart DNS Client Service

If you’re running Windows you can try restarting the DNS client services which resolves and caches DNS domain names.

Simply open up Command Prompt by pressing the Windows logo key and R. Then type “services.msc” and hit Enter.

Scroll down to “DNS Client,” right click on it, and select “Restart.”

If the restart option is greyed out for you (as it was for us), an alternative way to do it is via the command prompt.

Open up Command Prompt by pressing the Windows logo key and R. Then type “cmd” and hit Enter.

Then enter the following commands:

net stop dnscache
net start dnscache

Depending on the version of Windows you’re running you might get an error saying:

The requested pause, continue, or stop is not valid for this service.

This is most likely because you need to run CMD as a network service to issue the command. If you’re running into this error, we suggest trying the other alternatives below first.

3. Change DNS Servers

The next thing you can try is changing your DNS servers. By default, DNS servers are automatically assigned by your ISP. But you could try temporarily changing these to a public DNS server, such as Google or Cloudflare.

• Some prefer to use Google’s public DNS (8.8.8.8 and 8.8.4.4) long-term due to them sometimes being more reliable.
• Cloudflare also just launched their new secure and blazing fast free DNS (1.1.1.1 and 1.0.0.1) which we will be using in this example. If you want to use Google’s the steps are the same, you simply replace the DNS server addresses with Googles.

Tip: If you’re already using a free DNS server and having issues, removing it and defaulting back to your ISP’s DNS servers also sometimes fix things. Google and Cloudflare aren’t perfect 100% of the time and there have been a few instances where we’ve noticed switching back has resolved the issue.

Windows

In Windows simply open up Command Prompt by pressing the Windows logo key and R. Then type “control panel” and hit Enter.

Click on “Network and Internet” and then “Network and Sharing Center.” On the left-hand side, click on “Change Adapter Settings.”

Right click on your current connection, this will either be Local Area Connection or Wireless Network Connection based on how you’re connecting. Then click on “Properties.”

Select Internet Protocol Version 4 (or IPv6 if desired) and click on “Properties.”

Make a note of any existing settings in case you need to revert back. Click “Use the following DNS server addresses.” Enter the following, or replace the existing with these:

For IPv4: 1.1.1.1 and 1.0.0.1
For IPv6: 2606:4700:4700::1111 and 2606:4700:4700::1001

Click OK, then Close. Restart your browser.

Mac

To change DNS servers on a Mac, go to System Preferences…

Click on the network icon and then click “Advanced.”

Click on the “DNS” tab.

Then add Cloudflare’s DNS server addresses.

For IPv4: 1.1.1.1 and 1.0.0.1
For IPv6: 2606:4700:4700::1111 and 2606:4700:4700::1001

4. Reset Chrome Flags

Sometimes Chrome settings or experimental features can get accidentally changed or messed up. You reset these back to default by entering chrome://flags into your browser and clicking on “Reset all to default.”

Then restart your browser.

5. Disable VPN and Antivirus Temporarily

Sometimes VPNs and Antivirus software can conflict or override your network settings, including your DNS servers, etc. If you have any running, try temporarily disabling them (closing them) to see if it resolves the DNS probe finished nxdomain error in Chrome.

6. Check Your Local Hosts File

Every computer has what they call a local hosts file. This is a file that contains manual DNS entries which are mapped to specific IP addresses. Typically this is only edited when you want to preview your DNS before switching over domains to a new host.

However, there is a multitude of different ways this file could have been changed or edited. Therefore, if none of the above options worked for you, it’s worth double checking your local hosts file to ensure the website you’re trying to access isn’t in there.

Windows

The hosts file typically requires additional access. So the first step is to open up your text editor as an administrator. Simply click on your start menu, search for your text editor, right-click on it and select “Run as administrator.” This can be done in any text editor such as Notepad, Notepad++, Atom, etc. We are using Sublime in our example below.

Within your text editor click File → Open and browse to the following location:

C:WindowsSystem32driversetc

Click on the hosts file and “Open.”

Double check and make sure the website you’re trying to visit isn’t listed in there. If it is, remove it.

Mac

To check your hosts file on a Mac, we recommend getting Gas Mask. It’s a free application which can be used as hosts file manager, hosts files editor, and switch between them. It makes everything quick and easy! Otherwise, you can follow the steps below to edit your hosts file on Mac manually.

Go to Utilities and then click on “Terminal.”

Enter in the following command and press Enter (you will most likely be prompted for your administrator password as well).

sudo nano /private/etc/hosts

Double check and make sure the website you’re trying to visit isn’t listed in your hosts file. If it is, remove it.

7. Check DNS of Your Domain

If you’re only getting the DNS_PROBE_FINISHED_NXDOMAIN error on a single domain, even after checking your hosts file, you might need to check the DNS settings on the domain name itself.

If you’re a Kinsta client we have an in-depth post on how to point your domain and or DNS to Kinsta. If you recently migrated your website to a new hosting provider, it could be the DNS was cached incorrectly on your computer. In which case, Step 2 above should have resolved that.

8. Restart Your Computer

We know it’s annoying, but it has to be mentioned. 😬 If none of the above options work, trying restarting your computer and even your router. We realize many of you probably have hundreds of tabs or applications open and that’s why we made this the last option. But rebooting devices actually clears out a lot of temporary cache.

How to Fix DNS_PROBE_FINISHED_NXDOMAIN on Mobile (Android & iOS)

These are the most common ways to fix this error on your mobile device:

1. Restart Your Device

You know that famous tech support question “Have you tried turning it off and back on again?”

Well, the phrase is popular for a reason: A reboot does often fix the problem! Before attempting any of the other solutions on this list, start first with a simple device restart.

Android

To restart your Android device, press and hold your device’s power button to bring up the Options menu, then tap on the Restart option:

Wait for your device to restart, then open the Chrome app and check for the error.

iPhone/iOS

To restart your iPhone or other iOS device, begin by pressing and holding the power button and either of the two volume buttons:

Keep these held down until the power-off slider appears on the screen:

Drag the slider from one side to the other, then wait for the device to turn off.

Once it’s completely off, press and hold the device’s power button to turn it back on. Then check to see whether you’re still encountering the error.

2. Check for Chrome App Updates

The next step is to make sure that you’re using the very latest version of the Google Chrome app on your Android device

You can check for any Chrome updates and install them by following these steps:

1. Open the App Store app (this is called Google Play Store on Android devices).
2. Tap your profile icon at the top right (in the search bar).
3. Tap the Manage apps and device menu option.
4. Tap the Updates available button.
5. Look for Google Chrome in the list. If you see it, tap the Update button next to it.

After the update has finished installing, relaunch the Chrome app and check to see if you’re still getting the error. If you are, move on to the next solution below.

3. Clear Chrome’s Browser and App Data

Caches are useful because they speed up your browsing experience. In fact, our tests show that Edge Caching reduces the time it takes to deliver full pages to browsers by more than 50%.

However, this cached data can also frequently be the source of errors like DNS_PROBE_FINISHED_NXDOMAIN.

Luckily, you don’t actually need this cached data, and clearing it out may fix the error.

You can clear your mobile device’s Chrome cache and app data with just a few taps:

1. Open the Chrome app.
2. Tap the hamburger menu icon (⋮ or ⋯) at the top or bottom.
3. Tap History > Clear browsing data.
4. Check Browsing history and Cached images and files. Leave the other options unchecked.
5. If prompted with a “Also clear data from these sites?” message, confirm by tapping Clear.
6. Wait for Chrome to finish clearing the data, then tap the OK, got it confirmation message.

Now, try visiting the page again to see if the error has vanished. If it hasn’t, don’t lose heart! Just move on to the next option below.

4. Check for System Updates

As with Chrome, you’ll want to be sure you’re running the latest version of the Android operating system (OS) that’s available for your device.

Android

Here’s how to see if your Android device has any pending system updates:

1. Navigate to Settings > System.
2. Tap System Update.
3. This screen may tell you that your system is up to date. Regardless, tap the Check for update button at the bottom.
4. Wait for the system to look for any available OS updates.
5. If an update is found, agree to install it, then follow any further prompts to complete the installation.
6. Restart your device if the update process doesn’t do so automatically.

iPhone/iOS

You can check for pending updates on your iPhone or other iOS device with these steps:

1. Navigate to Settings > General > Software Update.
2. Review the screen to see if there’s an update available. If there is, tap the Download and install button.
3. Tap Install Now when prompted.
4. Restart the device.

Once your device’s system has been updated and rebooted, check again for the error in the Chrome app. If it’s still there, try the next solution on this list.

5. Change Your Mobile Device’s Network Settings

We talked earlier about modifying desktop devices’ DNS settings to fix the DNS_PROBE_FINISHED_NXDOMAIN error. This same approach can also work with mobile devices.

Android

To change the DNS settings on your Android, follow these steps:

1. Navigate to Settings > Network & Internet > Internet.
2. Make sure Wi-Fi is toggled “On.”
3. Press and hold your Wi-Fi network connection, then tap Modify.
4. Under Advanced options, locate the DNS 1 and DNS 2 fields and enter this information:
   • DNS 1: 8.8.8.8
   • DNS 2: 8.8.4.4
5. Tap Save.

After saving your new settings, re-open the Chrome app and check to see if the error’s gone.

iPhone/iOS

You can change the DNS settings on your iPhone or other iOS device with these steps:

1. Navigate to Settings > Wi-Fi.
2. Tap on your network in the menu.
3. Tap Configure DNS > Manual.
4. Remove the current listings under DNS Servers and add the following listings instead:
   • 8.8.8.8
   • 8.8.4.4
   • 2001:4860:4860::8888
   • 2001:4860:4860::8844

Now, restart the Chrome app and check again for the error message.

Summary

Even though it’s frustrating, the DNS_PROBE_FINISHED_NXDOMAIN error is usually pretty easy to get resolved. Between flushing your DNS cache, renewing your IP, and trying different DNS servers, you should hopefully be back up and surfing the web in no time.

Suggested reading: How to Fix the DNS_PROBE_FINISHED_BAD_CONFIG Error Code.

---

FAQ

What Is DNS_PROBE_FINISHED_NXDOMAIN?

The DNS_PROBE_FINISHED_NXDOMAIN error indicates that the Domain Name System (DNS) failed to resolve the domain name or address. NXDOMAIN stands for Non-Existent Domain.

What Causes DNS_PROBE_FINISHED_NXDOMAIN?

The DNS_PROBE_FINISHED_NXDOMAIN is typically caused by a misconfiguration or problem with your DNS.

How Do You Fix DNS_PROBE_FINISHED_NXDOMAIN?

Here are some recommendations and things to check to fix the error (sorted in order by most common reasons we see):

1. Release and Renew IP Address
2. Restart DNS Client Service
3. Change DNS Servers
4. Reset Chrome Flags
5. Disable VPN and Antivirus Temporarily
6. Check Your Local Hosts File
7. Check DNS of Your Domain
8. Restart Your Computer

How Do You Fix DNS_PROBE_FINISHED_NXDOMAIN on Mobile?

These are the most common ways to fix this error on your mobile device:

1. Restart Your Device
2. Check for Chrome App Updates
3. Clear Chrome’s Browser and App Data
4. Check for System Updates
5. Change Your Mobile Device’s Network Settings