Windows 10: DNS_PROBE_FINISHED_NXDOMAIN browser errors after router factory reset

I factory reset my router (and updated firmware to latest) in attempt to solve a monthly router freeze (Netgear R8000 router). At one point, I had DSL internet and switched to cable internet, and with DSL I changed some router settings specific to DSL (dialing/login). I had these freezes with DSL too. With DSL I had ipv6 enabled with my router. After the factory reset, the router is set to ipv4, instead of ipv6, and I consistently see DNS_PROBE_FINISHED_NXDOMAIN or ERR_NAME_NOT_RESOLVED type browser error messages now. If refresh the page, or close the tab and retry the address, it almost always resolves. But, it seems like addresses I've went to before or even those that resolved before will often get the messages. My guess is it's related to switching from ipv6 to ipv4 in my router, but I'm inclined to use my router's default ipv4 as maybe my previous ipv6 tinkering in the router settings is related to the router freezes. The thought is to minimize the router changes from default to debug the router freezes. My Windows 10 Pro (Version 20H2 Build 19042.1110) network DNS is set to automatically obtain, that hasn't changed. I've tried the following cmd (admin) commands so far, with reboots: ipconfig /release ipconfig /flushdns ipconfig /renew netsh winsock reset Thanks!

:)

 

How to factory reset Cisco 1700 Router

Hopefully I can help you here....its a very common thing to happen.


First, I take it you dont know the passwords for console access or telnet/ssh?

I will assume that these devices belong to you.

step 1. Plug a cisco console cable into a serial port on your pc
step 2. Plug other end into Cisco console port
step 3. Using hyperterm or putty or similar connect to the serial port
step 4. boot router, and make sure you clearly can see the output (this confirms you have good serial comms)
step 5. if this fails, adjust the comm port settings (9600, 8,1,n are the default)
step 6. now you have to do the only hard part...send the break command:

Break command list: Break Commands

Go down the list and match your OS and SW and try the sequence suggested.

If this fails several times do what I do: Install putty (free) and then to send a break so you can get into rommom just hit "ctrl-a b".

 

DNS_PROBE_FINISHED_NXDOMAIN on all browsers… but I can NSLOOKUP fine

For a few days, I've been occasionally getting DNS_PROBE_FINISHED_NXDOMAIN in Chrome. The most recent issue is with accessing a Web page on fs.cibc.com.

• My DNS server is 192.168.1.1, my router, whose DNS servers are 8.8.8.8 (and 169.53.182.124; the secondary is irrelevant, since the router can reach 8.8.8.8)
• On my router UI's network tools, I can both ping 8.8.8.8 and do an nslookup on cibc.com.
• Same on my PC: opening up a command window, I can successfully ping 8.8.8.8 and do an nslookup on cibc.com.
• However, the issue occurs in all browsers.

Here's what I've done:

• I've reset Chrome's experimental flags.
• I've disabled/enabled my network connection. I rebooted afterwards.
• I've rebooted my router (but not my cable modem).
• I restarted the DNS Client service (from the command line—"Restart" is greyed in the Services window.)
• I've checked my hosts file.

Since I can lookup the domain's IP manually, and on the router, I'm at my wit's end. What else should I do?

 

dns_probe_finished_nxdomain

Hello Diana,

If you could not fix the issue, the steps I am mentioning will help you fix it. If you already fixed it, I hope it will help out other people who are facing similar error every day.

So the DNS_PROBE_FINISHED_NXDOMAIN is the DNS error faced by mostly Chrome users. You can fix it just by changing DNS server address in your active network connection.

1. Go to Network connection properties.

2. Select the option which is about IPv4 and then go to its properties.

3. Change DNS to 8.8.8.8 (preferred) and 8.8.4.4 (alternate).

It should be fixed now. If not, then I will suggest you try other solutions like Flush Cache, Reset Chrome etc. depending on your device whether it is Windows or Mac.

You can refer this article -
How to fix DNS_PROBE_FINISHED_NXDOMAIN