How to Fix DNS_PROBE_FINISHED_NXDOMAIN in Chrome
Aug 14, 2023
How to Fix DNS_PROBE_FINISHED_NXDOMAIN in Chrome
The DNS_PROBE_FINISHED_NXDOMAIN error is not uncommon if you’re a Chrome user. https://www.youtube.com/c/Kinsta?sub _…https://kinsta.com/blog/ https://kinsta.com/newsletter/ https://twitter.com/kinsta https://instagram.com/kinstahosting https://facebook.com/kinstahosting https://kinsta.com/ https://kinsta.com/knowledgebase/dns _…https://kinsta.com/knowledgebase/dns _…https://kinsta.com/knowledgebase/what …https://kinsta.com/knowledgebase/dns/
Content
0.27 -> - Hey, Mike here.
1.61 -> Today, we're going to talk
about how to fix the error code
4.52 -> DNS_PROBE_FINISHED_NXDOMAIN in Chrome.
8.909 -> (upbeat music)
14.33 -> All right, for those of
you working with WordPress
16.65 -> on a regular basis, errors
specific to the CMS,
19.49 -> such as the white screen of death
21.54 -> or database connection errors
23 -> are somewhat common occurrences.
25.23 -> Another subset of errors
26.84 -> you will probably stumble upon
28.62 -> are those tied to your
internet connection and DNS.
31.86 -> The very common error that
Google Chrome users get
34.38 -> when trying to browse a webpage is.
36.393 -> (computer beep)
37.95 -> If you're seeing this error
39.02 -> while trying to get to
your WordPress site,
41.16 -> don't worry, this is fairly easy to fix.
43.59 -> DNS is short for domain name system
46.9 -> which helps direct traffic on the internet
48.75 -> by connecting domain names
with actual web servers.
51.82 -> When a user enters a
URL in the web browser,
54.2 -> DNS gets to work to connect that URL
56.74 -> to the IP address of the actual server.
59.24 -> This is called DNS name resolution
61.78 -> and involves the DNS recursor
querying various name servers
66.19 -> to figure out the actual
IP address of a server.
69.27 -> If DNS fails to resolve
the domain name or address,
72.2 -> then you might receive the...
73.207 -> (computer beep)
74.049 -> The NX domain part stands
for non-existent domain.
78.22 -> There are a couple different
variations of this error,
80.35 -> depending upon the browser you're running.
82.77 -> In Google Chrome, it looks like this.
85.17 -> In Mozilla Firefox, it looks like this.
87.32 -> In Microsoft Edge, you'll see this.
89.27 -> In Safari, it'll look like this.
91.61 -> So now let's dive into eight
of the most common fixes
95.17 -> to this error.
97.9 -> First, release and renew the IP address.
101.1 -> Due to the fact
101.933 -> that this is usually a
client-side DNS issue,
104.8 -> the very first thing you should do
106.11 -> is to try to release
and renew the IP address
108.72 -> on your computer.
110 -> This also includes flushing
your local DNS cache,
113.18 -> which is similar to browser cache.
115.4 -> In Windows, simply open
up the command prompt
117.7 -> by pressing the Windows logo key and R.
121.06 -> Then type CMD and hit Enter.
124.11 -> Type in ipconfig/release and hit Enter.
128.44 -> This will release your current IP address.
131.26 -> Then type in ipconfig/flushdns,
all one word, and hit Enter.
136.52 -> This will flush your local DNS cache.
139.04 -> You should see a "successfully flushed
140.987 -> "the DNS Resolver Cache"
message, if it worked.
144.58 -> Then type in ipconfig/renew and hit Enter.
148.41 -> This will renew your IP address.
150.22 -> An alternative way to
flush and renew your DNS
152.59 -> is by disabling your network
adapter and re-enabling it.
155.85 -> To release and renew
your IP address on a Mac,
158.18 -> go to System Preferences,
click on the Network icon,
161.41 -> and then click Advanced.
163.17 -> Click the TCP/IP tab if you
aren't already in there.
167.16 -> Then click on the Renew DHCP Lease button.
170.93 -> Just like we did in Windows,
172.83 -> Mac users can also clear
their local DNS cache,
175.88 -> although this is done
in a different place.
177.93 -> Go to Utilities and
then click on Terminal.
182.859 -> Enter in the following command.
186.67 -> On a Mac, however, keep in mind
there is no success message.
190.58 -> If you're on Windows, the
next solution you can try
193.02 -> is restarting the DNS client service
195.08 -> which resolves and
caches DNS domain names.
199.77 -> Open up command prompt
200.86 -> by pressing the Windows logo key and R,
203.72 -> then type services.msc and hit Enter.
207.8 -> Scroll down to DNS
Client, right-click on it
210.52 -> and select Restart.
212.43 -> If the restart option
is grayed out for you,
214.36 -> as it was for us, an
alternative way to do it
216.77 -> is via the command prompt.
220.06 -> Open up command prompt
221.11 -> by pressing the Windows logo key and R,
223.55 -> then type CMD and hit Enter.
227.12 -> Then enter the following commands,
229.21 -> net stop dnscache
231.29 -> and net start dnscache.
234.28 -> Depending on the version
of Windows you're running,
236.24 -> you might get an error
237.18 -> saying "the requested
pause, continue or stop
240.177 -> "is not valid for this service."
242.21 -> This is most likely
because you need to run CMD
245.23 -> as a network service to issue the command.
247.84 -> If you're running into this error,
249.08 -> we suggest trying some of our
remaining solutions first.
253.86 -> Some prefer to use Google's
public DNS long term,
257.05 -> due to them sometimes being more reliable.
259.27 -> CloudFlare has a secure
and blazing fast DNS
262.77 -> which we will be using in this example.
265.3 -> If you want to use Google's,
the steps are the same.
268.2 -> You simply replace the DNS
server addresses with Google's.
271.97 -> One quick side note.
273.1 -> If you're already using a free
DNS server and having issues,
276.51 -> removing it and defaulting
back to your ISP's DNS servers
280.32 -> also sometimes fixes things.
282.47 -> Google and CloudFlare aren't
perfect 100% of the time.
285.65 -> And there have been a few instances
287.21 -> where we've noticed switching
back has resolved the issue.
289.84 -> To change the DNS server in Windows,
291.7 -> simply open up command prompt
293.33 -> by pressing the Windows logo key and R,
296.27 -> then type control panel and hit Enter.
299.14 -> Click on Network and Internet,
300.9 -> and then Network and Sharing Center.
303.67 -> On the left hand side, click
on Change Adapter Settings.
307.26 -> Right-click on your current connection,
309.3 -> and this will either be
local area connection
312.04 -> or wireless network connection,
314 -> based on how you're connecting.
315.97 -> Then click on Properties.
317.9 -> Make a note of any existing settings
319.59 -> in case you need to revert back.
321.55 -> Click Use the following
DNS server addresses.
324.61 -> Enter the following,
325.5 -> or replace the existing with these.
331.34 -> Click okay, then Close,
and restart your browser.
335.37 -> To change DNS servers on a Mac,
337.07 -> go to System Preferences.
338.7 -> Click on the Network icon
and then click Advanced.
341.9 -> Click on the DNS tab.
343.61 -> Then add Cloudflare's
DNS server addresses.
348.46 -> Sometimes Chrome settings
or experimental features
351.34 -> can get accidentally changed or messed up.
353.94 -> This is an easy one to fix.
355.55 -> You can reset these back to default
357.24 -> by entering chrome://flags
361.54 -> into your browser and clicking
on Reset all to default.
365.31 -> Then restart your browser.
368.6 -> The next potential solution involves VPNs
371.4 -> and antivirus software
372.88 -> which can conflict or override
your network settings,
375.48 -> including your DNS servers.
377.36 -> If you have any running,
try temporarily closing them
379.94 -> to see if it resolves
this DNS issue in Chrome.
384.73 -> If none of the other options
385.87 -> that we've mentioned worked for you,
387.31 -> it's worth double-checking
your local host file
389.69 -> to ensure the website you're trying
391.33 -> to access isn't in there.
392.89 -> The host file typically
requires additional access.
395.81 -> So the first step is to
open up your text editor
398.37 -> as an administrator.
399.94 -> Click on your Start menu,
search for your text editor.
403.28 -> Right-click on it and
select Run as administrator.
406.58 -> This can be done in any text editor,
408.49 -> such as Notepad,
Notepad++, Atom, or others.
412.29 -> With your text editor,
click File then Open
415.13 -> and browse to the following location.
418.65 -> Click on the host file and then Open.
421.23 -> Double check and make sure the website
423.09 -> you're trying to visit
isn't listed in there.
425.13 -> If it is, remove it.
426.8 -> You can edit your host
file on Mac manually.
429.81 -> Go to Utilities, then click on Terminal.
432.87 -> Enter in the following
command and press Enter.
435.74 -> You'll most likely to be prompted
437.05 -> for your administrator password as well.
439.7 -> Double check and make sure the website
441.1 -> you're trying to visit isn't
listed in your host file.
443.89 -> If it is remove it.
447.35 -> If you're only getting this
DNS error on a single domain,
450.08 -> even after checking your host file,
452.23 -> you might need to check the DNS settings
453.99 -> on the domain name itself.
455.59 -> If you're a Kinsta client,
we have an in-depth post
458.18 -> on how to point your domain
and/or DNS to Kinsta.
461.3 -> We'll make sure to link that
post in the description below.
464.35 -> If you recently migrated your website
465.95 -> to a new hosting provider,
467.42 -> it could be the DNS was cached
incorrectly on your computer.
471.01 -> In which case, the second
option we previously discussed
474.4 -> would have resolved that.
477.31 -> Now I know it's annoying,
but it has to be mentioned.
480.1 -> If none of the above
options have worked for you,
482.54 -> try restarting your computer
and even your router.
486.11 -> We realize many of you
probably have hundreds of tabs
488.99 -> or applications open,
490.09 -> and that's why we made
this the last option.
492.61 -> But restarting devices
actually clears out a lot
495.27 -> of the temporary cache.
497.01 -> Even though it's
frustrating, this DNS error
499.44 -> is usually pretty easy to get resolved.
501.57 -> So between flushing your DNS cache,
503.66 -> renewing your IP and trying
different DNS servers,
506.73 -> you should hopefully be back up
508.11 -> and surfing the web in no time.
511.72 -> Kinsta's WordPress hosting
can speed up your website
514.13 -> by up to 200%, and you'll get 24/7 support
517.54 -> from our expert WordPress engineers.
519.58 -> Let us show you the Kinsta difference.
521.62 -> Try a free demo of our dashboard at...
526.13 -> Thanks for watching.
527.12 -> And don't forget to
subscribe for more tutorials,
529.46 -> explainers and helpful content like this.
532.04 -> See you soon.
533.015 -> (upbeat music)
Source: https://www.youtube.com/watch?v=AgeJhUvEezo
