How to Change DNS Settings on Your OS or Router

If the internet is a city, DNS is the street-sign system. You can still drive without it, but you’ll spend a lot of time yelling, “WHY IS THIS ADDRESS NOT REAL?!” at your screen.

The good news: changing DNS settings is one of the easiest “small tweaks” that can improve reliability, sometimes speed, and often privacy or securitydepending on which DNS service you choose. The even better news: if you can find your Wi-Fi settings, you’re already overqualified.

What DNS actually does (in plain English)

DNS (Domain Name System) translates human-friendly names (like example.com) into IP addresses (like 93.184.216.34) that computers use to find websites. Your device typically uses DNS servers provided by your ISP (internet provider) or your router automatically via DHCP.

When you “change DNS,” you’re telling your device (or your router) to ask a different DNS resolver for directions. That can help when:

• Your ISP DNS is slow, flaky, or having a “today I choose chaos” moment
• You want security-focused DNS that blocks known malicious domains
• You want family filtering (adult content blocking) at the network level
• You’re troubleshooting weird “site won’t load” issues that smell like DNS problems

Pick a DNS provider (and write the numbers down first)

Before you start clicking around, decide which DNS service you want. Here are popular, reputable options and their IPv4 addresses (the ones you’ll most often type in). Many also support IPv6 and encrypted DNS (DoH/DoT).

Tip: Configure at least two DNS servers (primary + secondary). If the first one is down, your device can fall back instead of staring into the void.

Device vs. router DNS: which should you change?

Change DNS on your router if…

• You want every device on your home network (phones, TVs, tablets, guests) to use the same DNS
• You’re setting up filtering/security for the household
• You don’t want to repeat the same steps on five million gadgets

Change DNS on a single device if…

• You only want the change for one machine (like a work laptop)
• Your router is locked down by an ISP or you can’t access it
• You’re testing a DNS provider before rolling it out everywhere

Before you touch anything: two “don’t regret this later” steps

1. Write down your current DNS settings (or take a screenshot). That way you can undo everything in 30 seconds.
2. Know what you’re changing: DNS is not the same as Wi-Fi password, IP address, or “turning off the internet.” (But yes, a typo can feel like it.)

How to change DNS on Windows 11 (and Windows 10)

Windows 11: Settings app method (modern + easy)

1. Open Settings → Network & internet.
2. Select Wi-Fi (then your connected network) or Ethernet (your active connection).
3. Find DNS server assignment and click Edit.
4. Change it from Automatic (DHCP) to Manual.
5. Turn on IPv4, then enter your Preferred and Alternate DNS addresses.
6. (Optional) Turn on IPv6 and add IPv6 DNS addresses if your provider supports them.
7. Click Save.

Windows 10/11: Classic Control Panel method (old school, still works)

1. Open Control Panel → Network and Internet → Network and Sharing Center.
2. Click Change adapter settings.
3. Right-click your connection (Wi-Fi or Ethernet) → Properties.
4. Select Internet Protocol Version 4 (TCP/IPv4) → Properties.
5. Choose Use the following DNS server addresses and enter your DNS servers.
6. Click OK, then close out.

Quick test + cache flush on Windows

• Open Command Prompt and run: ipconfig /all (look for “DNS Servers”).
• If things seem “stuck,” run: ipconfig /flushdns.
• Test resolution: nslookup example.com (it should show the DNS server you set).

How to change DNS on macOS

On modern macOS versions, you’ll do this in Network settings. You can add multiple DNS servers and reorder themtop of the list usually gets tried first.

1. Open System Settings → Network.
2. Select your connection (Wi-Fi or Ethernet) and click Details.
3. Click DNS.
4. Use the + button to add DNS server IP addresses.
5. Remove unwanted servers with − (optional).
6. Click OK, then Apply.

Pro tip: If you’re troubleshooting, temporarily remove old entries instead of piling new ones on top. DNS lists can get “crowded,” and crowded lists make debugging… spicy.

How to change DNS on iPhone or iPad (Wi-Fi)

On iOS/iPadOS, DNS changes are typically per Wi-Fi network. That means if you change DNS at home, it won’t automatically change at the coffee shop (because your phone has boundaries).

1. Go to Settings → Wi-Fi.
2. Tap the ⓘ (info) icon next to the connected network.
3. Scroll down and tap Configure DNS.
4. Select Manual.
5. Tap Add Server and enter your DNS server IPs (example: 1.1.1.1 and 1.0.0.1).
6. Remove the old servers if needed, then tap Save.

Note: To apply DNS changes across cellular data too, you generally need a VPN or a managed profile that controls DNS system-wide. For most people, changing DNS on the router is the cleanest “set it once” approach.

How to change DNS on Android (including “Private DNS”)

Android 9+ (common): Private DNS (DNS over TLS)

“Private DNS” on Android usually means DNS-over-TLS (DoT). Instead of typing IP addresses, you often enter a provider hostname (like a URL, but for DNS).

1. Open Settings → Network & internet.
2. Tap Advanced (if needed) → Private DNS.
3. Select Private DNS provider hostname.
4. Enter a hostname (example: Cloudflare uses one.one.one.one), then tap Save.

Android Wi-Fi-specific DNS (varies by manufacturer)

Some Android versions also let you set DNS per Wi-Fi network via advanced IP settings (often by switching from DHCP to Static). This can be handybut it’s also easier to accidentally change other settings, so Private DNS is usually safer.

How to change DNS on ChromeOS (Chromebooks)

ChromeOS exposes DNS per network connection. You can choose provider presets or enter custom servers.

1. Open Settings.
2. Go to Network and select your active connection (Wi-Fi or Ethernet).
3. Expand the network details and find Name servers.
4. Select a preset (like Google name servers) or choose Custom name servers.
5. Enter your DNS servers (example: 8.8.8.8 and 8.8.4.4) and click/tap away to apply.

How to change DNS on Linux (Ubuntu and friends)

Many desktop Linux distributions use NetworkManager, so you can change DNS in the GUI or via terminal tools like nmcli. Servers sometimes use /etc/resolv.confbut be careful, because NetworkManager may overwrite it.

GUI method (NetworkManager / Ubuntu desktop)

1. Open Settings → Network (wired) or Wi-Fi (wireless).
2. Open the connection’s settings (gear icon / details).
3. Look for IPv4 or IPv6 settings.
4. Set DNS servers (comma-separated), then save/apply.

Terminal method: nmcli (fast and script-friendly)

Example workflow:

1. List connections: nmcli con
2. Set DNS for a connection (IPv4 example): nmcli con mod "YOUR_CONNECTION_NAME" ipv4.dns "1.1.1.1 1.0.0.1"
3. (Optional) Ignore DNS from DHCP if you want your custom DNS to “win”: nmcli con mod "YOUR_CONNECTION_NAME" ipv4.ignore-auto-dns yes
4. Reconnect: nmcli con down "YOUR_CONNECTION_NAME" && nmcli con up "YOUR_CONNECTION_NAME"

How to change DNS on your router (recommended for whole-home changes)

Router interfaces vary, but the logic is almost always the same: log in, find Internet/WAN settings, switch DNS from automatic to manual, enter primary/secondary, save, reboot if needed.

Generic router steps (works as a mental map)

1. Connect to your home network (Wi-Fi or Ethernet).
2. Open your router admin page or app (often something like 192.168.0.1 or 192.168.1.1).
3. Log in with the admin credentials.
4. Find Internet, WAN, or Network settings.
5. Locate DNS settings (sometimes under “Advanced” or “IP settings”).
6. Turn off “Get DNS automatically” (wording varies) and enter your DNS servers.
7. Save/apply. Reboot the router if prompted (or if devices don’t pick up the change).

Examples by popular brands

TP-Link routers (common path)

• Go to Advanced → Network → Internet → Advanced Settings.
• Select “Use the following DNS addresses,” enter DNS, then Save.

NETGEAR routers

• Open the router admin page (NETGEAR often uses a router login portal).
• Go to Internet / Internet Setup.
• Under DNS Address, choose Use these DNS Servers, then enter primary/secondary and apply.

Linksys (especially mesh systems)

• In the Linksys app: go to Advanced Settings → Local Network Settings (menus can vary).
• Set your DNS servers, then save/apply.

Router note: Some ISPs lock DNS settings on their equipment. If your router refuses to cooperate, set DNS on each device, or use your own compatible router.

How to verify your DNS change actually worked

Your device might “remember” old DNS answers for a bit (caching), so verification matters. Here are practical checks:

On Windows

• ipconfig /all → confirm the DNS server lines show your chosen resolver
• nslookup example.com → see which server answered the query

On macOS / Linux

• scutil --dns (macOS) or resolvectl status (systemd-based Linux) to inspect resolvers
• dig example.com or nslookup example.com to test

On phones

• Toggle airplane mode on/off after changes, or reconnect to Wi-Fi to refresh network settings.
• If you changed router DNS, restart Wi-Fi on the phone so it picks up new DHCP info.

Troubleshooting: when DNS changes go sideways

1) “The internet is broken” (right after you changed DNS)

• Double-check for typos (8.8.8.8 is not 8.8.8.88ask me how your keyboard tries to sabotage you).
• Set it back to Automatic to confirm DNS is the cause.
• Restart the device or reconnect to the network.

2) Some sites work, some don’t

• Try a different DNS provider (rare, but some resolvers handle certain edge cases differently).
• If you enabled filtering (family/security DNS), a blocked site may be intentional.

3) Your browser seems to ignore your DNS

Some browsers can use DNS-over-HTTPS (DoH) inside the browser, which may bypass your OS DNS settings depending on how it’s configured. If you’re troubleshooting, temporarily disable DoH in the browser (or set it to “use system DNS”) so you’re testing one thing at a time.

4) Corporate or school devices won’t behave

Managed devices may enforce DNS settings via policy. If your DNS keeps “snapping back,” it may not be youit may be IT.

Real-world experiences: what changing DNS feels like (500-ish words from the trenches)

You rarely wake up and think, “Today, I will re-architect my name resolution strategy.” DNS changes usually happen because something is annoying you. Here are some common, very real scenariosand what people typically learn from them.

Experience #1: The “Why won’t this site load?” spiral

A site won’t load on your laptop, but it loads on your phone. You clear cookies, reboot, glare at your modem, and start bargaining with the universe. Then someone says, “Try changing DNS,” and you roll your eyes… until it works. What happened? Your ISP’s DNS might have cached a bad record, struggled with routing, or temporarily failed. Switching to a different public resolver can bypass that failure path. The lesson: DNS isn’t glamorous, but it’s a real failure point, and changing it is a clean troubleshooting stepespecially when the rest of the internet seems fine.

Experience #2: The “household internet rules” upgrade

Many households start with device-by-device controls, then realize that kids have more devices than socks. Changing DNS at the router level to a security or family-filtering service becomes the “one setting to rule them all.” Suddenly, the TV, tablet, and guest phone all inherit the same baseline protection. The surprise: it’s not perfect. DNS-based filtering can reduce exposure, but it won’t replace device-level parental controls or content settings in every app. The win is the simplicity: you get broad coverage with minimal babysitting.

Experience #3: The gamer’s ping myth (and the reality)

Gamers often hear “change DNS to reduce lag.” Sometimes it helps, but not because DNS speeds up every packet in a match. DNS affects how quickly your device finds the server addressusually at connection time, not during gameplay. Where it can help: faster, more reliable resolution can reduce slow “connecting…” screens, and some resolvers may route you to slightly better CDN endpoints for downloads or updates. The lesson: DNS isn’t a magic turbo button for ping, but it can reduce friction around connecting, patching, and service stability.

Experience #4: The remote-work reliability play

Video calls drop, corporate portals feel sluggish, and “it’s probably the Wi-Fi” becomes the default diagnosis. But in some cases, DNS timeouts are the hidden villainespecially if your ISP’s resolver is overloaded or inconsistent. People who switch their router DNS to a reputable public resolver often report fewer “random” glitches: fewer delays opening web tools, fewer temporary site failures, and less time doing the IT equivalent of turning it off and on again. The lesson: reliability is the underrated DNS benefit. Even if speed gains are small, consistency can be noticeable when you live in web apps all day.

Conclusion

Changing DNS settings is one of those rare tech tasks that’s both low-effort and genuinely useful. If you want one change that benefits every device, update DNS on your router. If you’re testing or working around restrictions, change DNS on a single OS or device. Either way, write down your old settings first, enter at least two servers, and verify the results.