I diagnosed my network outage with one command, and it saved me hours of troubleshooting

Published Sep 11, 2026, 8:00 AM EDT His love of PCs and their components was born out of trying to squeeze every ounce of performance out of the family computer. Tinkering with his own build at age 10 turned into building PCs for friends and family, fostering a passion that would ultimately take shape as a career path. Besides being the first call for tech support for those close to him, Ty is a computer science student, with his focus being cloud computing and networking. He also competed in semi-pro Counter-Strike for 8 years, making him intimately familiar with everything to do with peripherals. Troubleshooting an internet connection that suddenly drops for your whole home can either be a five-second affair or be a multiple-hour waiting game, and there's rarely an in-between. The most common method is a quick router power-cycle, but against some of the more common failures, it's not often successful. One thing that can take your entire network down is a DNS failure, and if your ISP's DNS resolvers suddenly stop working, there's only one specific fix for it, and it's the setting nobody thinks to try during an outage. Your connection can be fine while nothing loads A classic symptom Almost everything you do online starts with name lookup, and that's where DNS comes into play. Before your web browser can request a page, your computer has to ask a DNS resolver what IP address that domain corresponds to, and by default, that resolver is run by your ISP. If it doesn't provide your system with an answer, your request just dies, and the page fails to load. What makes this sort of failure difficult to nail down is the error looks similar to when other unrelated things have gone wrong. Web browsers will tell you the same generic "this site can't be reached", and apps generally just show a plain "no connection" error with no further information. Your setup can be picture-perfect, but if your ISP's recursive resolvers are overloaded, misconfigured, or rebooting, you're not getting far, and it's not exactly an uncommon failure. How to tell what failure is happening You can tell the difference between a DNS failure and something else really quickly It takes one command in a terminal to figure out which kind of failure your network is having, and it's a simple ping. Pinging a raw IP address like 1.1.1.1 or 8.8.8.8 skips resolution entirely, so if you get replies there, your connection is alive and packets are routing correctly, which rules out pretty much everything that a router reboot would address. To go a bit further, you could run nslookup example.com 1.1.1.1 or, on Linux and macOS, dig@1.1.1.1 example.com. This will ask a resolver that isn't your ISP's to answer a query. If successful while normal browsing is disabled, you can safely conclude that DNS is the issue, and you know exactly why the fix will work. Changing your DNS at the router level is the fix Covers all the bases The cleanest fix is at the router, since your router hands DNS server addresses to every client via DHCP. Simply log into your router's admin panel, find the DNS fields under internet or WAN settings, and switch the allocation from automatic to manual. Set the values to a pair of public resolvers, like Cloudflare's 1.1.1.1, 1.0.0.1, or Google's 8.8.8.8 and 8.8.4.4, which are primary and secondary respectively. One small pitfall here is that your devices that get their IPs via DHCP won't have their resolvers update until they're given a new lease. Toggling Wi-Fi on and off or restarting these devices will fix that. The bigger catch is that some gateways won't let you do this, specifically ISP-supplied ones. It depends on who your ISP is, but some don't provide a DNS field to change, so if something happens in that department, you're out of luck there. You're stuck changing it per-device at that point, which is tedious, but necessary if you want to get back online. When changing per-device, caching might get in your way initially. Your OS caches results, including failed lookups, so run ipconfig /flushdns on Windows or resolvectl flush-caches on Linux if the change doesn't seem to take. If your connection is dual-stack, setting IPv4 resolvers alone may not be enough, because your device can still be using IPv6 resolver addresses advertised by your router. Linux and macOS honor those by default, and Windows behavior has changed a bit depending on version, so if the fix appears not to work, set IPv6 resolvers as well or temporarily disable IPv6 on the adapter entirely. What you give up by changing resolvers A few key things are different on a 3rd-party DNS DNS requests being fielded by your ISP allows them to see the sites you visit, and moving that to someone like Cloudflare or Google means they get to see those requests as well. Whether that additional information matters to you at all is your choice, but it's not a privacy win like some claim it is. In addition to that, any filtering your ISP applies at the resolver stops working. In many markets, parental controls and content blocks are implemented at the DNS level, so bypassing your ISP's DNS will render those null and void. A quick, underrated check for when your internet goes down Sometimes, an outage will happen and there will be no recourse, but sometimes, it can be due to a failing resolver that you never intentionally set up to begin with. A quick ping test and nslookup can give you a fast diagnosis that has an even faster fix, and if you can change your DNS at the router level, it's the best way to get everything back online at once.