Connection issues with many sites following a restart.
Connection issues with many sites following a restart.
Hey everyone. This really got me thinking. If my PC stayed on overnight, most websites wouldn't work. The only sites that functioned were from Google (like Google.com and YouTube). Restarting the PC fixed it until morning. Honestly, I'm completely confused. The Windows troubleshooter gave confusing results and said nothing was wrong. I tried resetting the network card, uninstalling and reinstalling the drivers for my NIC, and ran SFC which helped a bit but not enough. Searching online didn't help much either. Maybe it's time to completely wipe the system and reinstall Windows.
Hey! Just a quick note—no hardware posts here, but I’ve got it in my profile. The Asus ROG B450-F runs Intel 1211 chips and a Ryzen 3600x. Might be worth checking out. Cool!
Which DNS servers are you currently utilizing? You might want to try 8.8.8.8 and observe any improvements.
Considered an outdated DNS cache as the initial concern, try using nslookup in a terminal to check FQDNs.
DNS servers typically stay stable after a reboot, though caching can play a role. It might help to check the cache and try pinging again when the issue arises. I remember Google's IP works well for me—unusual for most services. I ran an nslookup on a known problematic site and saved its IP for later use. If the problem returns, I'll test ping and nslookup first. Then I'll clear the DNS cache with /flushdns and try Google DNS as a backup. Thanks for the suggestions!
It occurred once more after 31 hours of availability. Nslookup works. Ping also functions with no lost packets and typical latency. /flushdns and /renew didn't assist. As @Allan suggested, switching to 8.8.8.8 then using /flushdns /renew helped. It seems there might be an issue with DNS, though I'm unsure if it's local or related to my ISP...
Suggests a local browser problem since nslookup and ping work easily. I’d download Falkon Browser and keep it ready for testing—it’s lightweight, independent, and fast, though not suitable for everyday use. *Note:* It might be an incorrectly configured DNS server from your ISP, possibly setting TTLs too high, causing your local cache to think the site is up when it isn’t. Switching to 1.1.1.1 could reveal the issue.