DNS errors on Windows 11 startup

DrMacintosh · November 8, 2021

Hello, so I recently upgraded to Windows 11. Since doing that my system has felt smoother, especially with graphics. However there is one problem that didn't exist in Windows 10. Now every time I boot up this machine I have DNS issues. Web pages give "DNS_PROBE_STARTED", "DNS_PROBE_FINISHED", and etc error messages and other programs that connect to the internet slow/dont work for a few minutes after startup. After that initial period of nothing working suddenly everything does.

I'm connected over ethernet to my network. I do have a wifi card installed but the wifi in my rig is off. The ethernet adapter is set to automatically obtain its DNS settings from my router which is set to 1.1.1.1/1.0.0.1 as its DNS server. I've restarted the router but nothing changed. This issue also doesn't happen with my other devices so its seems to be a problem with this computer only. I've also cleared my DNS with ipconfig in terminal and the like with nothing changing.

Anyone have any ideas or possible solutions?

Jarsky · November 9, 2021

If you change the DNS to manual and set the DNS there statically, does the problem go away?

If so what router are you using? Some of the WAN Down Spoofing logic on routers such as some of Technicolors range, dont work well with network changes made in Windows 10 after I believe its the 20H2 updates and later.

DrMacintosh · November 9, 2021

11 hours ago, Jarsky said:

If so what router are you using?

I’m using the Linksys Velop AX4200. I could try setting 1.1.1.1 as a static DNS server on my PC. I tried a network reset the other day on my computer and the issue didn’t go away but it felt like it got slightly better.

Jarsky · November 10, 2021

11 hours ago, DrMacintosh said:

I’m using the Linksys Velop AX4200. I could try setting 1.1.1.1 as a static DNS server on my PC. I tried a network reset the other day on my computer and the issue didn’t go away but it felt like it got slightly better.

OK it shouldnt be a WAN spoofing issue then since thats a fairly knew product that released since they made the changes.

When you have the issue, it would be interesting to see the result of an NSLookup if you can do that. e.g open cmd prompt and run nslookup google.com

DrMacintosh · November 10, 2021

27 minutes ago, Jarsky said:

OK it shouldnt be a WAN spoofing issue then since thats a fairly knew product that released since they made the changes.

When you have the issue, it would be interesting to see the result of an NSLookup if you can do that. e.g open cmd prompt and run nslookup google.com

Actually I think the issues been fixed! I know I had restarted my router when this issue was occurring initially and nothing changed. I restarted it again today and it seems to be working fine. I guess some combination of that, plus a network reset on my machine followed by multiple ipconfig commands fixed the issue. It seems to have completely gone away. My Ethernet adapter even correctly identifies the AirPort Extreme I’m using as a switch + WAP to extend the Velop AX4200.