When your ISP's resolver is the broken part, pointing your PC at a large public DNS server is a five-minute repair. Here is the exact setting, both Windows routes, and the honest limits of what it can do.
Every PC is normally told which DNS server to use by the router, and that is usually the ISP's resolver. When that resolver is slow, stale or down, websites fail while the connection itself is perfectly healthy. The fix shown in the video is to set the DNS server manually on the network adapter — Google DNS in the video, with Cloudflare as the other common choice. The setting takes five minutes, is completely reversible, and only affects this one PC. This page walks through it on Windows 11 and the classic Control Panel route, and then says plainly what the change will and will not do for you.
( • ) Use the following DNS server addresses:
Preferred DNS server: 8.8.8.8
Alternate DNS server: 8.8.4.4
[ OK ] [ Cancel ]
With this setting, your PC stops asking the router's chosen resolver and asks Google or Cloudflare directly, every time it needs to translate a name. Nothing else about your connection changes — same router, same line, same IP address from the router's point of view.
That narrow scope is what makes the change both safe and diagnostic. If websites spring back to life the moment you switch, you have proven the old resolver was the fault. If nothing improves, the fault was never DNS at the server level, and you have lost only five minutes finding out.
8.8.8.8 — Alternate DNS: 8.8.4.4ping google.comFor Cloudflare, the pair is 1.1.1.1 and 1.0.0.1. Always fill in both fields — the alternate is what keeps you online if the preferred server ever hiccups.
The older route reaches the exact dialog in the panel above and still works on Windows 10 and 11:
ncpa.cpl and press EnterChange the adapter you actually use. Many PCs list Ethernet, WiFi and old VPN adapters side by side; editing a disconnected adapter changes nothing and is a classic reason this fix appears not to work.
Both are large, free, professionally run public resolvers, and either one is a sound repair for a broken ISP resolver. Google DNS, 8.8.8.8, is the pair used in the video and the most widely tested. Cloudflare, 1.1.1.1, publishes a privacy-leaning policy and is the popular alternative.
What neither does: raise your download speed, fix a weak WiFi signal, or make a down line come back. A resolver only translates names. Replacing a failing translator makes pages start loading again — which can feel dramatic — but the pipe itself is exactly as fast as it was yesterday.
Reversing the change takes the same path: return the setting to Automatic (DHCP) in Settings, or select Obtain DNS server address automatically in the IPv4 dialog. Do this if you take the PC onto a network that manages its own name resolution — above all, an office network with a domain, where manual public DNS breaks logins and internal names.
A manual DNS entry is also invisible in daily use, which is its one real danger: months later, nobody remembers it is there. If you set it as a temporary test, note it down or undo it once the test is finished.
See every step on a real Windows PC — the tests, the commands and the DNS change, in order.
▶️ Watch Full VideoYes. Google DNS and Cloudflare DNS are public services offered free for anyone to use, and setting them on your own computer is a normal, documented Windows configuration. You are simply choosing a different phone book for name lookups — nothing about your connection or accounts is altered.
The alternate is a fallback. Your PC asks the preferred server first; if it does not answer in time, the alternate is asked instead. With only one address filled in, a single resolver outage takes your browsing down with it, so always enter the complete pair.
On the PC when you are testing or only one machine is affected — it is quick and reversible. On the router when every device in the house has the same problem, because one router change then repairs all of them at once. There is a dedicated page in this series on choosing between the two.