DNS settings choose which DNS resolvers your laptop uses to turn domain names into IP numbers, shaping speed, reliability, and filtering.
You type a site name and expect a page to load. Your laptop first has to translate that name into a numeric IP. DNS (Domain Name System) handles that translation. Your DNS settings decide which DNS resolvers your laptop asks for the answer.
If pages stall before they even start loading, a network sign-in page won’t appear, or one laptop can’t reach sites that other devices can, DNS can be part of the problem. Once you know where DNS settings live, you can check what your laptop is using, switch resolvers with care, and roll back in seconds if the change doesn’t help.
What DNS Settings Control
DNS settings are a small set of fields tied to each network connection. On most laptops you’ll see a primary DNS server and a secondary DNS server, plus IPv6 fields on networks that use IPv6.
When your laptop needs to reach a domain, it asks the first server on the list. If that server doesn’t answer, the system tries the next one. Your laptop also keeps a short-lived DNS cache so repeated lookups don’t hit the network every time.
Clues DNS Is Part Of The Mess
- Your browser says “server not found,” but your phone on the same Wi-Fi works.
- Some sites load and others fail, and the pattern changes after reconnecting.
- A hotel or airport sign-in page never shows up.
- You can reach a service in an app, yet the same site won’t open in a browser.
Where DNS Settings Come From
Most laptops get DNS automatically from the network they join. That handoff usually comes from the router through DHCP, along with your device IP, gateway, and other basics. When DNS is set to “Automatic,” your laptop is using what the network provides.
You can also set DNS manually. Manual DNS overrides the network-provided DNS for that connection. People do this when an ISP resolver is flaky, when they want family filtering, or when they’re testing a suspected DNS issue.
Automatic DNS Vs Manual DNS
Automatic DNS is hands-off and tends to “just work” across many networks.
Manual DNS gives you control. It also means one typo can break name lookups until you fix it. So, treat manual DNS as a reversible change, not a permanent badge of being “techy.”
DNS Settings On Your Laptop For Fewer Connection Errors
Changing DNS settings can help with common annoyances: long delays before a page starts, random “can’t find the site” errors, or overly strict filtering from a default resolver. It can also change what gets blocked, since some resolvers add malware or adult-site blocking.
DNS isn’t a cure-all. Weak Wi-Fi, a crowded router, or a down website won’t be fixed by swapping resolvers. Still, DNS is easy to test, and it’s easy to undo.
What Can Go Wrong
- Typing the DNS server IP wrong can stop browsing until corrected.
- Some workplaces block public DNS, so manual DNS may fail on that network.
- Family-filter DNS can block sites you still want, like forums or image hosts.
How To Find Your Current DNS Settings
The clicks change by operating system, yet the target is the same: locate the active connection (Wi-Fi or Ethernet), then view the DNS server list that connection is using right now.
Windows 11 And Windows 10
Open Settings, go to Network & Internet, pick Wi-Fi or Ethernet, then open the properties for the connection you’re using. Look for a DNS section that shows automatic vs manual and the server IPs entered. Some Windows builds also let you set encrypted DNS (DNS over HTTPS) per resolver.
macOS
Open System Settings (or System Preferences), go to Network, choose the active connection, then open the DNS tab in the more settings area. You’ll see an ordered list of DNS servers. The order matters.
Chromebook
Open Settings, choose Network, select your Wi-Fi, then open the network details. DNS is usually under a “Name servers” option where you can select automatic or enter custom servers.
Linux Laptops
Many Linux desktops use NetworkManager. Open the network settings for the active connection and check DNS under IPv4 and IPv6. Some distros also show the active resolver list in a terminal via resolvectl status.
DNS Settings Map By Laptop And Connection Type
This table links common screens to what they change. Use it when you switch between Wi-Fi and Ethernet, or when a VPN seems to override what you entered.
| Where You Change DNS | What You’ll Usually See | What That Choice Changes |
|---|---|---|
| Windows Wi-Fi profile | Automatic or Manual, IPv4 and IPv6 DNS fields | Only that saved Wi-Fi profile |
| Windows Ethernet | DNS settings separate from Wi-Fi | Only the wired connection |
| macOS Wi-Fi service | Ordered list of DNS servers | That service; order sets the try-first server |
| macOS USB/Ethernet service | DNS list per network service | Only that adapter |
| Chromebook Wi-Fi | Name servers: Automatic, Google, or Custom | That Wi-Fi and user session settings |
| Home router WAN settings | DNS server fields in the router admin page | Every device using router-provided DNS via DHCP |
| VPN client | App-managed DNS, split-tunnel rules | Traffic that goes through the tunnel |
| Browser-only secure DNS | Browser toggle and provider picker | Only that browser’s DNS lookups |
How To Change DNS Without Losing Access
This is the safest flow: write down what you have, change DNS, test, then decide whether to keep it. If anything breaks, switch back to automatic DNS for that connection.
Write Down Your Current Server IPs
Take a screenshot or note the numbers. If the page only shows “Automatic,” you can still find the active server list in the connection details view.
Choose A Resolver With Clear Docs
Two well-known public options are Google Public DNS and Cloudflare’s 1.1.1.1 resolver. Their official setup pages list the server IPs and common setup steps: Google Public DNS “Get Started” documentation and Cloudflare’s 1.1.1.1 resolver setup page.
Enter Primary And Secondary DNS
Most screens give you two fields. Enter the first resolver as primary, the second as secondary. If your laptop asks for IPv6 resolver values and your network uses IPv6, enter those too.
Reconnect And Flush Cached Lookups
Toggle Wi-Fi off and on, or unplug and replug Ethernet. If a name still fails, clear the system DNS cache. On Windows, run ipconfig /flushdns. On many Macs, a restart is the simplest cache reset.
Test In A Realistic Way
Open a few sites you trust, then try one service that uses many domains, like streaming or online docs. If only one site fails, DNS might not be the cause. If many fail, revert to automatic DNS and try again with a different resolver.
Common Resolver Choices At A Glance
This table isn’t a ranking. It’s a way to match a resolver style to what you’re trying to fix.
| Resolver Type | Typical Server IPs | When It Fits |
|---|---|---|
| Network-provided DNS | Set automatically via DHCP | Home networks where everything works and you want zero tinkering |
| Google Public DNS | 8.8.8.8 / 8.8.4.4 | When you want a widely used resolver with public setup docs |
| Cloudflare 1.1.1.1 | 1.1.1.1 / 1.0.0.1 | When you want clear setup options and encrypted DNS details |
| Family-filter resolver | Varies by provider | When you want DNS-level blocking for adult sites or malware domains |
| Work or school DNS | Set by the organization | When you need internal domains and sign-in tools to work |
Encrypted DNS Settings You May See
Some laptops and browsers can send DNS queries over HTTPS (often labeled DoH). This can reduce local network snooping of DNS lookups. It can also clash with networks that expect to see plain DNS for filtering. If you’re on a managed network and things break after turning on encrypted DNS, switch encrypted DNS off first, then retest.
You may see secure DNS controls in two places: the operating system and the browser. OS-level settings affect every app on the laptop. Browser-only settings affect just that browser, so a site might fail in one browser and work in another if the DNS paths differ. When troubleshooting, line them up: either keep both on plain DNS while you test, or keep both on secure DNS with the same resolver.
Some networks also publish their own secure DNS endpoints. On those networks, using the network’s endpoint can keep internal sites working while still using encryption. If you don’t know the network’s endpoint, stick with the network-provided DNS and skip secure DNS changes on that connection.
When The Problem Isn’t DNS
If changing resolvers doesn’t fix the issue, these checks often pin down what’s happening.
- No IP from the network: If your laptop didn’t get a valid IP and gateway, DNS won’t work. Fix the connection first.
- VPN overrides DNS: Many VPN apps set DNS inside the tunnel. Turn the VPN off for a minute and recheck active DNS.
- Captive portal sign-in: Some public Wi-Fi sign-ins behave better with automatic DNS. Switch to automatic, sign in, then decide on manual DNS.
How Long DNS Changes Take To Show Up
After you swap DNS servers, some sites may still open as they did before for a little while. That’s normal. Your laptop caches DNS replies, and routers and resolvers cache them too. Many records expire in minutes, others can last longer.
If you want to see the change right away, clear the laptop’s DNS cache, then close and reopen the browser. If a site still points to an old IP, wait a bit and test again. If a site is stuck on the wrong reply for a long time, switching back to automatic DNS and reconnecting can confirm whether the issue is local caching or a resolver problem.
A DNS Check Card For Laptops That Move Between Networks
- Check the active connection and confirm whether DNS is automatic or manual.
- Note the current server IPs before changing anything.
- Change one setting at a time: resolvers first, encrypted DNS later.
- Test across a few sites and one app that uses many domains.
- If browsing breaks, return DNS to automatic and reconnect.
References & Sources
- Google for Developers.“Get Started | Public DNS.”Lists Google Public DNS server IPs and outlines how to switch a device to use them.
- Cloudflare.“Set up Cloudflare 1.1.1.1 resolver.”Provides setup steps and server IPs for 1.1.1.1 across common operating systems.