How to Fix DNS_PROBE_FINISHED_NXDOMAIN Error

Sdílet
Vložit
  • čas přidán 25. 07. 2024
  • In this video, we will go over solving the DNS_PROBE_FINISHED_NXDOMAIN error. Get web hosting for your website 👉 bit.ly/3lP0I3X 👈 use coupon code: HA10 to get 10% OFF.
    There are quite a few different steps we can take to try and solve the DNS_PROBE_FINISHED_NXDOMAIN error. While some general tips apply to any internet related issue, in this video tutorial we will take a deeper dive into Operating System specific solutions such as clearing your cache and changing your DNS server.
    ____________________________________________
    📌 Handy links on fixing the DNS_PROBE_FINISHED_NXDOMAIN error:
    Hostinger Tutorial on fixing the DNS_PROBE_FINISHED_NXDOMAIN error:
    www.hostinger.com/tutorials/f...
    Flush DNS cache:
    www.hostinger.com/tutorials/h...
    ____________________________________________
    ⭐ Follow Us ⭐
    TikTok: / hostingeracademy
    Twitter: / hostinger
    Facebook: / hostinger
    WordPress Explained Group: / wpexplained
    Hostinger Tutorials: www.hostinger.com/tutorials
    Subscribe to our channel: czcams.com/users/HostingerAc...
    ____________________________________________
    🕒 Timestamps
    00:00 - Intro
    00:50 - General: 1 - Restarting your router
    01:10 - General: 2 - Reset Chrome flags
    01:35 - General: 3 - Disable VPS/Antivirus
    01:57 - Windows: 1 - Flush DNS Cache
    02:18 - Windows: 2 - Release and Renew IP address
    02:55 - Windows: 3 - Change DNS servers
    03:59 - Windows: 4 - Restart DNS Client Service
    05:24 - Windows: 5 - Check Local Hosts File
    06:12 - macOS: 1 - Flush DNS Cache
    06:46 - macOS: 2 - Release and Renew IP address
    07:06 - macOS: 3 - Change DNS servers
    07:53 - macOS: 4 - Check Local Hosts File
    08:32 Final tips
    ____________________________________________
    🟣 Sometimes you might find that sites do not want to load even though your internet connection is fine, and the URL is written correctly. In Google Chrome, this usually occurs in a form of DNS_PROBE_FINISHED_NXDOMAIN error message. Lucky for us, there are multiple steps we can try and take to get the DNS_PROBE_FINISHED_NXDOMAIN error resolved. Starting with simple stuff like restarting your router and then working our way up to more complicated tasks such as checking your Local Hosts file, this video has got you covered.
    ____________________________________________
    ▶ Want to see more awesome tutorials like this one in the future? Consider subscribing 😁
    czcams.com/users/HostingerAc...
    ▶ If you have questions, don’t hesitate and join our Facebook group for more help: / wpexplained
    ____________________________________________
    Thank you for watching! Let us know in the comments below if you have any questions. Good luck on your online journey. 🚀
    #DNS_PROBE_FINISHED_NXDOMAIN #HowtoFixDNS_PROBE_FINISHED_NXDOMAIN #HostingerAcademy

Komentáře • 124

  • @HostingerAcademy
    @HostingerAcademy  Před 2 lety +3

    Do you want to get an amazing deal for your web hosting plan?
    Follow this link and use the coupon code *HA10* to get *10% OFF* 👉 bit.ly/3lP0I3X 👈

    • @queen.6861
      @queen.6861 Před rokem

      ٢١١
      ق٢٢ ٢٢د٢دص١ممحططجج٠٠٨٨٩٩من كسدظظ١ضضخضخضحط٩٠٦حنهنشهشبعبتينينسسمشمشظسوونسظميننينينينينذننهثص

  • @christopherturban9875
    @christopherturban9875 Před 9 měsíci +1

    The ''Change DNS servers''really solved the problem, thumbs up!

  • @patrickcarlcachuela3495
    @patrickcarlcachuela3495 Před 11 měsíci

    Thank you so much for this wonderful video. I tried some of the steps and the one that works is when I placed the Google Public DNS in Network Sharing.

  • @deadmonsterhr7209
    @deadmonsterhr7209 Před rokem +1

    Thank you so much man, the amount of frustration I had these days, the 5th helped me fix it

  • @bklynbeef
    @bklynbeef Před rokem

    Step 5 worked for me. Thank you so much!!

  • @farhanfarooq9847
    @farhanfarooq9847 Před 2 lety +3

    Thank you for the help. 3rd step did it for me. Thanks again

    • @HostingerAcademy
      @HostingerAcademy  Před 2 lety

      Hey Farhan, we're glad this video helped solving your problem 😊

  • @Picolo221
    @Picolo221 Před rokem

    Thank you very much. The 5th method worked for me.👍👍

  • @TehRedBoy
    @TehRedBoy Před rokem +1

    FINALLY BROOOOO THANK YOU SO MUCHTHE LOCAL HOSTS HELPED ME STEP 5 LKETSGOOO

  • @pritoshthomas9495
    @pritoshthomas9495 Před rokem +2

    Thank you so much! Changing DNS server worked!

  • @demon-gamer7038
    @demon-gamer7038 Před rokem

    Thnak you so much I was dealing with this problem for 1 day. Finally the step 5 really solved my problem.

  • @TheMentik78
    @TheMentik78 Před rokem

    Release + renewing IP address fixed my issue, thank you!

  • @mxgamer124
    @mxgamer124 Před měsícem +1

    If i recntly clicked a suspicios link for free stuuf and i get this error on all of my devices connected to the network, does it mean that someone is trying to get my information, especially i get this error on login pages like the xbox mobile app login works with a vpn but not with this network, pls respond im worried.
    Like the first time i clicked that link i thought everything was fine and then when i tried to search for something this error poped up and then i refreshed a couple of times and dissapeared and now its on my phone too and my other pc.

  • @YoyocraftsOffical
    @YoyocraftsOffical Před rokem +1

    amazing vid. thanks soo much for the help!:D

  • @opaquegrief196
    @opaquegrief196 Před rokem

    the first step worked for me :) ty so much

  • @geezy-s2y
    @geezy-s2y Před rokem

    deleting all the hosts and ip's in step 5 worked for me ty!

  • @mahmoudnabil6762
    @mahmoudnabil6762 Před rokem

    Thank you so much. You saved me. Really

  • @kingsmo
    @kingsmo Před 4 měsíci

    STEP 5 YOU'RE THE GOAT!!!

  • @RuleYourLife
    @RuleYourLife Před 2 lety +1

    thanx a lot. problem rectified.

  • @mohammedfarhanshaikh7072
    @mohammedfarhanshaikh7072 Před 9 měsíci

    changing isp's dns to google's dns worked ... thanks....

  • @ReyesZepedaGarcia
    @ReyesZepedaGarcia Před rokem

    I've never commented on a yt vid before but you just helped me solve my issue after 5 whole hours spent going back and forth between dns. records for my site. Thank you so much

  • @zurichzb
    @zurichzb Před rokem

    THAZNK U SO MUCH HELPED A LOT!!!!!

  • @tuguini99
    @tuguini99 Před rokem

    Thank you very much man it worked for me :DD

  • @0RainLove0
    @0RainLove0 Před rokem

    Thanks for your good suggested tips, but unfortunately none of helped me. Seeking your help. Thanks again.

    • @HostingerAcademy
      @HostingerAcademy  Před rokem

      Hey Tareef, consider checking this article for more methods to fix the error: www.hostinger.com/tutorials/fix-dns_probe_finished_nxdomain 🙏🏻

  • @quotationandpoetry786

    Very informative

  • @jonnathanzhindon2992
    @jonnathanzhindon2992 Před rokem

    On a 2016 server, do these steps work as well? All computers connected to the server received this error

  • @Coomerings
    @Coomerings Před 2 lety

    Thank you so much!!

  • @reaperhubcrim
    @reaperhubcrim Před rokem

    LOCAL HOST WORKED I LOVE u

  • @policegasetcherla9308
    @policegasetcherla9308 Před 2 lety

    Thank you for the help

  • @shx3dow
    @shx3dow Před rokem

    thx bro, really helped alot

  • @cooperu2194
    @cooperu2194 Před 2 lety

    when unchecking DNS client in system configuration it doesn’t let me apply this change. when i click apply it just rechecks the box

    • @HostingerAcademy
      @HostingerAcademy  Před 2 lety

      Hey there, if you find any issue with your hosting account, please get in touch with us directly by sending an email at support@hostinger.com. Our Customer Success specialists are available 24/7 and ready to give you in-depth assistance 🙏🏻

  • @PabloGonzalez-ou2zj
    @PabloGonzalez-ou2zj Před rokem

    It worked when I added "#" to the site that was being blocked, thanks! but why was it blocked in the first place? What does that?

    • @HostingerAcademy
      @HostingerAcademy  Před rokem

      Hey Pablo, glad this video helped you fix the issue! DNS_PROBE_FINISHED_NXDOMAIN can happen for several reasons:
      - A web browser cannot locate the target website because the domain is not registered or has expired
      - The domain is not pointing to any IP address
      - There is a misconfiguration in the DNS settings of the user’s computer, so it cannot resolve the domain
      - A VPN or antivirus software interferes with the network settings
      - The issue comes from the internet provider 😊

  • @factbymm
    @factbymm Před rokem

    thanku sir
    you are great

  • @jefft5854
    @jefft5854 Před 7 měsíci

    Thanks!!!

  • @factbymm
    @factbymm Před rokem

    5th step did it for me thanku sir

  • @markm_koko
    @markm_koko Před 18 dny

    Thanks, this actually works

  • @mysticmiji7363
    @mysticmiji7363 Před rokem +3

    THANK YOU SO MUCH! THIS ONE WORKED FOR ME!: 5:24

  • @NoobViperYT
    @NoobViperYT Před rokem

    5th Method Solved My all Problems. Literally, I have seen upto 100 video, Only This Video Helped me. I am Subscribing To You

    • @HostingerAcademy
      @HostingerAcademy  Před rokem

      Glad this video helped you! 🚀

    • @NeilGrant-sy3eq
      @NeilGrant-sy3eq Před měsícem +1

      ​ 9:11 😂 9:11 9:11 @HostingeDNS_PROBE_FINIS 9:11 😂😂 9:11 HED_NXDOMAIN rAcademy 😂

  • @miktara4019
    @miktara4019 Před 2 lety +1

    restarting router works... 10 times a day... why though? what's getting stuck?

    • @HostingerAcademy
      @HostingerAcademy  Před 2 lety

      Hey, Mik. Could you please send our Customer Success team a message? They will gladly help you out with your issue 👉support.hostinger.com/en/articles/1583780-how-to-contact-live-support

  • @abbasraxa5416
    @abbasraxa5416 Před 2 lety

    thanks brother helpful

  • @anaangelinecanos2545
    @anaangelinecanos2545 Před 2 lety

    thank you for the help

  • @AhmadAli-tw9km
    @AhmadAli-tw9km Před rokem

    Changing dns worked for me❤

  • @yunitaandella3818
    @yunitaandella3818 Před 2 lety

    thankyou sm!

  • @The2x00
    @The2x00 Před rokem

    thanks 💯

  • @HashirHome-wj7wl
    @HashirHome-wj7wl Před 16 dny

    okay so my website is opening on my laptop now after changing DNS IP but not on others without changing their DNS Network Ip

  • @joelokongwu3143
    @joelokongwu3143 Před 4 měsíci

    you helped me a lot

  • @bertrandahishakiye3051
    @bertrandahishakiye3051 Před 9 měsíci

    Its showing the error message .. for one site only and again i am on my phone help

    • @HostingerAcademy
      @HostingerAcademy  Před 9 měsíci

      Hello 👋
      Drop us a message at support@hostinger.com, and we'll check everything out together 👀

  • @medievalsoothing
    @medievalsoothing Před rokem

    You are great buddy

  • @mohammedalam635
    @mohammedalam635 Před 2 lety

    Thanks for your useful post

  • @barthngumbi
    @barthngumbi Před měsícem

    I have mistakenly changed my domain name, now I can't access the admin panel, they are showing me this error please kindly help

    • @HostingerAcademy
      @HostingerAcademy  Před měsícem

      Hello 👋 Please contact our support at support@hostinger.com from the email you have registered with Hostinger, and they'll be happy to investigate your particular case and help 🚀

  • @rohitshn4
    @rohitshn4 Před 6 měsíci +1

    I follow all the rule but problem not solved

    • @HostingerAcademy
      @HostingerAcademy  Před 5 měsíci

      Hey there 👋
      We're sorry to hear that the provided solutions did not help. Could you drop us a message at support@hostinger.com? We'll figure it out together 💜

  • @intervillagesports
    @intervillagesports Před rokem

    thanks it works for me. 3_00 was my solution

  • @minhalkazim7624
    @minhalkazim7624 Před 2 měsíci

    does that mean anyone who want to visit my website need to solve this first? smh. In my case, hoststinger domain not working if the user try to access via mobile connection.

    • @HostingerAcademy
      @HostingerAcademy  Před 2 měsíci

      Hey there!
      Usually, this error relates to domain's DNS zone, so in this case, we'd highly recommend firstly checking if your domain is properly pointing and propagated. After that, the website will open for everyone 😊

  • @arjunbishnoi154
    @arjunbishnoi154 Před 3 měsíci

    2:55 this method resolves everything

  • @UOGIGotchu-ex5su
    @UOGIGotchu-ex5su Před 11 měsíci

    Helpful yes, but I am still lost and need help, can you help me?

    • @HostingerAcademy
      @HostingerAcademy  Před 11 měsíci

      Hello 👋
      Our team is always here to help you out. Please reach out to us at support@hostinger.com, and we'll figure it out together 🚀

  • @karbonkilo
    @karbonkilo Před rokem

    Didn’t work for sadly.

    • @HostingerAcademy
      @HostingerAcademy  Před rokem

      Hello!
      Our Customer Success Team is ready to advise you! Please follow this link: hpanel.hostinger.com/help and get in touch with us 📩

  • @CasperSallee
    @CasperSallee Před 12 dny

    but what do you do when it happens on an Android phone?!?!?!?!?

    • @HostingerAcademy
      @HostingerAcademy  Před 6 dny

      Hey there!
      Drop our team a message at support@hostinger.com, and we'll figure it out together 💜

  • @faisal-wf9yl
    @faisal-wf9yl Před měsícem

    my love ''Change DNS servers'' solved

  • @Mrazamat888
    @Mrazamat888 Před rokem

    how fix dns_probe_finished_nxdomain

  • @louasfi
    @louasfi Před rokem

    I did everything is not working 😭

    • @HostingerAcademy
      @HostingerAcademy  Před rokem +1

      Hey there, if the steps in this video didn't work, consider checking other methods in the written version of this tutorial: czcams.com/video/XsLO_lgpnyA/video.html 🙏🏻

  • @darvml2464
    @darvml2464 Před rokem

    Still I am faces the issue

    • @HostingerAcademy
      @HostingerAcademy  Před rokem

      Hey there, if the steps in this video didn't work, consider checking other methods in this article: www.hostinger.com/tutorials/fix-dns_probe_finished_nxdomain 🙏🏻

  • @PabloJFerri
    @PabloJFerri Před 2 lety

    nothing of this helped me, another solution? i want to see my webpage in another device, in my computer it opens, in another device doesnt, what's the problem?¿

    • @HostingerAcademy
      @HostingerAcademy  Před 2 lety

      Hey there, if the methods in this video didn't work, consider checking this article to find other ways to fix this error: www.hostinger.com/tutorials/fix-dns_probe_finished_nxdomain 🙏🏻

  • @usama_Ibrahim
    @usama_Ibrahim Před 2 lety

    Its not working 😔

    • @HostingerAcademy
      @HostingerAcademy  Před 2 lety

      Hey Usama, if the steps in this video didn't work, consider trying other methods in this article: www.hostinger.com/tutorials/fix-dns_probe_finished_nxdomain 💜

    • @usama_Ibrahim
      @usama_Ibrahim Před 2 lety

      Thanks sir 😀but sir now is my website is open, not open in my mobile and others etc… plzz answer me plzz explain or help me

  • @JavierAlvarez-ry7hn
    @JavierAlvarez-ry7hn Před 2 lety

    Alguien que me tradusca al español

    • @HostingerAcademy
      @HostingerAcademy  Před 2 lety

      Hey Javier, you can go to this page for the Spanish version of this tutorial: czcams.com/video/P1plAm5tOwg/video.html 😊

  • @umut58tr
    @umut58tr Před 8 měsíci

    Linux Debian? PARDUS

  • @Coveringaxe
    @Coveringaxe Před 6 měsíci

    Why is this so complicated? I spend so much time making the website from scratch, you advertise a seamless experience, i purchased the hosting AND DOMAIN from HOSTINGER, but when i was trying to solve the error for domain not pointing to or DNS. YOU DO NOT HAVE HOSTINGER AS AN OPTION TO SELECT AS YOUR DOMAIN PROVIDER!? Now after doing all these steps, the website is working on my system, but cannot be accessed by my phone or other devices, what is the point of making a website that only I can visit? YOU NEED TO BE VERY CLEAR ABOUT YOUR SUPPORT AND FEATURES

    • @HostingerAcademy
      @HostingerAcademy  Před 5 měsíci

      Hey there,
      We're truly sorry for the frustration you've encountered, and we appreciate your patience in reaching out.
      We understand the importance of a seamless experience, and it seems we fell short in this instance. We're committed to resolving your concerns.
      To assist you better, could you please fill in the form below? It will help us locate your Hostinger account, check everything behind the scenes, and provide the support you deserve - hstn.gr/HelpForm
      Our goal is to ensure your website is accessible on all devices, and we're here to guide you through the process. Let's work together to get this sorted out! 💜

  • @dausenmoore
    @dausenmoore Před rokem

    Damn. None of this worked. I'm starting to worry I'll teed to completely rest my whole computer...

    • @HostingerAcademy
      @HostingerAcademy  Před rokem

      Hey there, if the steps in this video didn't work, consider checking other methods in the written version of this tutorial: www.hostinger.com/tutorials/fix-dns_probe_finished_nxdomain 🙏🏻

  • @dailychow7880
    @dailychow7880 Před 10 měsíci

    bro, does not speak clearly

  • @DavidJones-tx4yf
    @DavidJones-tx4yf Před rokem

    What if Chrome is the only browser on my Mac that is generating the DNS_PROBE_FINISHED_NXDOMAIN error for the web site? Safari, Edge and Firefox all load the web site without any problems. I've reset the chrome://flags.

    • @HostingerAcademy
      @HostingerAcademy  Před rokem

      Hi, David!
      If you are experiencing the "DNS_PROBE_FINISHED_NXDOMAIN" error specifically on Google Chrome on your Mac, while other browsers like Safari, Edge, and Firefox are loading the website correctly, it suggests that the issue may be related to Chrome's DNS cache or settings.
      Here are a few troubleshooting steps you can try to resolve the issue.
      1️⃣ Clear Chrome's DNS Cache:
      ✅ Open a new tab in Google Chrome.
      ✅ Type the following address in the address bar: chrome://net-internals/#dns
      ✅ Click on the "Clear host cache" button.
      ✅ Restart Google Chrome and try accessing the website again.
      2️⃣ Flush DNS Cache on Your Mac:
      ✅ Open the Terminal application on your Mac. You can find it in the "Utilities" folder within the "Applications" folder, or by using Spotlight search.
      ✅ In the Terminal window, type the following command and press Enter:
      sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
      Enter your admin password when prompted.
      ✅ Restart Google Chrome and try accessing the website again.
      3️⃣ Disable Chrome's DNS Prefetching:
      ✅ Open a new tab in Google Chrome.
      ✅ Type the following address in the address bar: chrome://settings/
      ✅ Scroll down and click on the "Advanced" section.
      ✅ Under the "Privacy and security" section, disable the "Use a prediction service to load pages more quickly" option.
      ✅ Restart Google Chrome and check if the issue persists.
      4️⃣ Reset Chrome to Default Settings:
      ✅ Open a new tab in Google Chrome.
      ✅ Type the following address in the address bar: chrome://settings/reset
      ✅ Click on the "Restore settings to their original defaults" button.
      ✅ Confirm the reset by clicking on the "Reset settings" button.
      ✅ Restart Google Chrome and try accessing the website again.
      If none of the above steps resolve the issue, you may consider reinstalling Google Chrome on your Mac to ensure a clean installation.
      Hope this helps! 🚀

    • @DavidJones-tx4yf
      @DavidJones-tx4yf Před rokem

      @@HostingerAcademy Thanks for your reply. I worked through all of the options you suggested. I was unable to resolve the issue after doing this. I also was not able to find the "Advanced" section in the Chrome settings, to "Disable Chrome's DNS Prefetching".
      However, I was able to resolve the issue with another setting under the Chrome settings. This is under "Privacy and Security" and is called "Use secure DNS". This had been turned on and pointed to Google's own DNS services. So, the internally hosted web services on my network, that are not publicly accessible and therefore have no public IPs or DNS records, were unable to be resolved by Google's DNS services. Switching "Use secure DNS" to "With your current service provider" means Chrome is now using the DNS settings specified in my macOS network settings, which is pointing to my internal DNS server which has DNS records set up for my internal hosts and referrals set to go to Google's servers.
      Thanks again for your help. It got me in the right place at least. 🙂

  • @angelnunez1353
    @angelnunez1353 Před 9 měsíci

    thank youuuuuuuu🥲