Trying to switch your router to a different DNS can feel frustrating when every screen looks slightly different. You’ll learn how to update DNS settings in your router’s admin panel, confirm the change, and troubleshoot if pages don’t load. Plan for 15–30 minutes, and have your router model or admin login handy.
Change your router DNS by logging into your router’s admin page, updating the DNS addresses (usually under WAN/Internet and/or DHCP/Local Network), and saving the settings. After that, devices should automatically start using the new DNS—if not, you’ll need to verify the correct section and reboot the router.
This guide is designed for home users who want all connected devices (Wi‑Fi, Ethernet, smart TVs, etc.) to use different DNS servers without changing settings one device at a time.
Check where DNS settings live on your router
You get the best results by first figuring out where your router stores the DNS values that clients actually receive. In most home networks, DNS can be controlled in two places: the router’s WAN/Internet DNS (for the router itself) and the DHCP/Local Network DNS (what the router hands out to devices).
Here’s what to do before you log in:
– Look for menu labels like Internet, WAN, Connection, DHCP, or Local Network (wording varies by brand/model).
– Decide whether you want to change DNS for the router’s own internet resolution (WAN) or to hand out DNS to devices (DHCP).
– Gather your router login details (usually from the sticker or your ISP paperwork): router IP/gateway, admin username, admin password.
A quick way to think about router DNS in home setups:
– WAN/Internet DNS: “Where does the router look up domain names?”
– DHCP/Local Network DNS: “What DNS does the router tell clients to use?”
To make that clearer, the table below summarizes common public DNS resolvers and their IPv4 addresses (useful when you’re deciding what to enter into your router’s primary/secondary DNS fields).
Popular Public DNS Resolvers (IPv4)
| # | Resolver | Primary DNS | Secondary DNS | Typical Focus |
|---|---|---|---|---|
| 1 | Google Public DNS | 8.8.8.8 | 8.8.4.4 | Speed & stability |
| 2 | Cloudflare 1.1.1.1 | 1.1.1.1 | 1.0.0.1 | Privacy & performance |
| 3 | Quad9 | 9.9.9.9 | 149.112.112.112 | Threat awareness |
| 4 | Cisco OpenDNS | 208.67.222.222 | 208.67.220.220 | Filtering options |
| 5 | CleanBrowsing (Family/Security variants) | 185.228.168.168 | 185.228.169.168 | Content control |
| 6 | AdGuard DNS | 94.140.14.14 | 94.140.15.15 | Anti-tracking |
| 7 | DNS.WATCH | 84.200.69.80 | 84.200.70.40 | No logging claims |
Log into your router admin page safely
The fastest way to avoid accidental outages is to log in via the router’s gateway IP and only change DNS-related fields. Once you’re in, update router DNS settings carefully and don’t touch unrelated firewall/security profiles.
Follow these steps:
– Find your router’s gateway IP (common examples: 192.168.0.1, 192.168.1.1) and open it in a browser.
– Sign in to the admin interface, then avoid changing unrelated settings (especially firewall or security profiles).
– If you’ve forgotten the admin password, you may need a router reset to regain access (). In practice, that usually means using the router’s physical Reset button and re-entering ISP credentials afterward, so confirm your exact model’s manual.
As a sanity check, remember how DNS traffic works at the network level: according to RFC 1035, DNS queries commonly use UDP port 53 (and TCP port 53 for certain cases). If you accidentally break WAN connectivity or firewall rules, you may see symptoms that look like DNS problems even when router DNS was never misconfigured.
Change Router DNS (IPv4 and, if available, IPv6)
Change router DNS by updating the DNS server fields in the WAN/Internet area and—most importantly—any DHCP/Local Network area that hands DNS to clients. If your router supports IPv6, update IPv6 DNS too, otherwise some devices keep using IPv6 defaults even when IPv4 changes.
Use this approach:
– In the WAN/Internet area, find fields like Static DNS, DNS Server, or Primary/Secondary DNS.
– Enter the DNS addresses in the correct format:
– Primary DNS: 1.1.1.1
– Secondary DNS: 1.0.0.1
– If your router has a DHCP section, also update DHCP DNS (so connected devices get those DNS settings automatically).
– If IPv6 DNS options exist, update IPv6 DNS too (otherwise some devices may keep using IPv6 defaults).
One reason this matters is that DNS has multiple “paths” in a typical home network. Routers often resolve domains for themselves using WAN DNS, but DHCP determines what DNS resolvers clients use for browsing, streaming, and software updates.
To clarify how different menus usually behave, here’s a comparison of what changing each place affects:
| Router setting you edit | Impact on router itself | Impact on devices via DHCP |
|---|---|---|
| WAN/Internet DNS | Usually yes | Often no |
| DHCP DNS / Local Network DNS | Not always | Usually yes |
| Applies to existing clients | N/A | Often not until they renew DHCP |
| Applies to new clients | Depends | Usually yes immediately after DHCP |
| IPv6 DNS separate fields | May exist | May exist via DHCPv6/SLAAC |
| ISP can overwrite values | Sometimes | Sometimes |
| Best for “router only” changes | Yes | No |
| Best for “whole home” changes | Not sufficient alone | Yes (if set correctly) |
| Common symptom when wrong | Mixed behavior | “Internet works but sites don’t resolve” on devices |
| Common symptom when not applied | No visible change | Devices keep old DNS until reboot/renewal |
| Best For | Changing router outbound resolution | Making all clients use new DNS |
Also, as of 2026, many routers still support only standard DNS (UDP/TCP 53). If you ever compare this to modern “encrypted DNS,” remember that DNS over HTTPS uses HTTPS transport (port 443), which is specified in RFC 8484.
Save settings, reconnect, and verify DNS works
Save router DNS settings, then verify from at least one device. If DNS doesn’t change immediately, rebooting the router and refreshing DHCP on clients usually resolves it.
Follow these steps:
– Click Save/Apply, then reboot the router if the interface prompts it or if DNS doesn’t change right away.
– Verify from a device by checking DNS resolution results (options include browsing a site that shows DNS behavior, or using tools like `nslookup`/`dig` on your computer).
– If you previously cached DNS locally, flush your device’s DNS cache (exact steps depend on your OS).
Practical verification approach (router DNS specifically):
1. On a computer connected to Wi‑Fi/Ethernet, run a DNS query for a known domain (for example, a site you use often).
2. Use `nslookup example.com` and confirm the resolver behavior (some tools also show which server answered).
3. If it looks unchanged, force a client DHCP renewal (turn Wi‑Fi off/on, or “renew lease” on some systems), and reboot the router if your router DNS UI required it.
If you manage multiple devices in the home, verifying once is usually enough—router DNS is a shared network dependency. Still, in my own day-to-day troubleshooting experience helping others, I’ve seen “half working” setups where only one of WAN/DHCP/IPv6 was updated.
What can go wrong (and how to spot it fast)
When router DNS doesn’t apply, the issue is usually in the section you edited, the save/apply flow, or the ISP/connection mode. The fastest way to diagnose is to confirm which path (WAN vs DHCP vs IPv6) your clients actually use.
Common issues:
– You edited the wrong section: changing only WAN may not affect devices if the router hands out DNS via DHCP.
– Settings didn’t apply: you clicked save but the router didn’t reboot or the router UI didn’t commit the changes (look for the confirmation banner like “Settings saved” plus any “applied”/“committed” status near the top of the page, and confirm the router shows the updated values in the same screen after saving).
– Your ISP/connection type overwrites DNS: some routers/PPPoE setups can re-pull DNS from the ISP after reconnect.
– IPv6 stays unchanged: even if IPv4 works, IPv6-only traffic may still use old DNS.
– Typing mistakes: one wrong digit in the DNS IP can make browsing appear broken (double-check primary/secondary values).
A quick triage workflow:
– Step 1: Check the router UI after saving—do the fields still show the values you entered?
– Step 2: Reboot the router (if prompted or if DNS doesn’t change).
– Step 3: Refresh one client and run `nslookup` again.
– Step 4: If IPv6 is enabled, repeat the check for IPv6 DNS entries too.
Verdict / tip: when it’s worth changing router DNS
Changing router DNS is a good move when you want more control over name resolution (for reliability, filtering preferences, or privacy), because it affects many devices at once. The tradeoff is that incorrect DNS entries—or updating only one of WAN/DHCP/IPv6—can create confusing failures like “internet works but sites don’t resolve.”
Skip changing router DNS if:
– You’re not comfortable editing router settings and you can’t safely revert changes.
– Your router is managed by an ISP, employer, or a managed network where DNS changes are restricted.
– You’re troubleshooting a complex connectivity issue where DNS changes might mask the real cause (for example, a WAN authentication problem or link instability).
Quick checklist (scan/save) + FAQ
| Step | What to look for | Done? |
|---|---|---|
| 1 | Admin login page opens (router gateway IP) | ☐ |
| 2 | DNS fields found under **WAN/Internet** and/or **DHCP/Local Network** | ☐ |
| 3 | Primary + Secondary DNS entered correctly (IPv4) | ☐ |
| 4 | IPv6 DNS updated if available | ☐ |
| 5 | Click **Save/Apply** (and reboot if prompted) | ☐ |
| 6 | Verify DNS works from at least one device | ☐ |
FAQ
– Will changing router DNS affect all devices?
Usually yes—if you update the DHCP DNS (or the router distributes DNS to clients). If you only change WAN DNS, effects may be limited.
– Should I change both IPv4 and IPv6 DNS?
If your router offers both, it’s best to update both to avoid “some websites work, others don’t” behavior.
– Why did my DNS revert after a reboot?
Common reasons include ISP/connection-type behavior that reassigns DNS automatically, or the change being saved to the wrong menu.
– What if my router doesn’t let me edit DNS?
Some ISP-branded or managed routers restrict DNS changes. In that case you may need to update DNS on individual devices or use a feature supported by your specific model ().
If you follow the checklist above—especially targeting the correct WAN/DHCP section and updating IPv6 when present—you should be able to change router DNS cleanly. After applying settings, verify from a device right away; if it doesn’t work, revisit the “what can go wrong” section and adjust the exact DNS area you edited.
In short: update the right DNS menu, save/apply properly, then validate with a DNS query on a client. With those three steps, changing router DNS becomes a repeatable, home-wide improvement you can do confidently in 10–20 minutes.
Frequently Asked Questions
How do I change my router DNS settings?
Log into your router’s web interface by opening a browser and entering the router IP address (often 192.168.0.1 or 192.168.1.1). Go to a section named “DNS,” “Network,” or “WAN/LAN,” then select “Manual” or “Custom” DNS. Enter the DNS server addresses you want (e.g., Google DNS or Cloudflare) and click “Save/Apply,” then reboot the router if prompted. Afterward, check that clients are using the new DNS by viewing DNS settings on a device or running a DNS lookup.
Which DNS should I use for better speed and privacy?
Common options include Google Public DNS (8.8.8.8 and 8.8.4.4) and Cloudflare (1.1.1.1 and 1.0.0.1), both widely used for reliability and performance. For privacy-focused users, consider DNS providers that advertise no logging or encryption support, but verify their policies before switching. The “best” DNS for you depends on your region and ISP routing, so it can help to test different DNS servers and compare page load time and DNS resolution speed. Keep the DNS change consistent across the router to avoid mixed results on connected devices.
What should I do if changing router DNS doesn’t work?
First confirm you saved the settings and that the router applied them—some routers require a restart to take effect. Check whether your ISP supplies DNS settings via DHCP and if your router has an option like “Override ISP DNS” or “Use ISP DNS”—enable override if needed. On a connected device, verify the DNS server address in the network settings to ensure it matches what you entered in the router. If problems persist, try flushing local DNS on your device (e.g., via command-line) and test with a DNS lookup or by visiting a known domain.
Why is it important to change DNS at the router level instead of only on one device?
Changing DNS on the router ensures every device on your network uses the same DNS settings automatically, including phones, smart TVs, and gaming consoles. This reduces troubleshooting across devices and avoids scenarios where one device resolves slowly while another works fine. It also helps fix network-wide issues like certain websites not loading due to DNS problems. If you only change DNS on a single device, other devices may continue using the ISP’s DNS and still experience delays or lookup failures.
How can I confirm my router DNS change is active?
After saving changes, reconnect a device to the Wi‑Fi or restart the device to ensure it receives the updated DHCP settings. Then check the DNS server address shown in the device’s network details—on Windows, macOS, iOS, or Android, this is typically visible under Wi‑Fi or Ethernet settings. You can also run a DNS check by using a DNS lookup website or command (like `nslookup`) to confirm the name resolution behavior. If you don’t see the expected DNS server, revisit the router’s DNS page for “Manual/Custom” settings and ensure the router fully applied the configuration.
📅 Last Updated: November 17, 2026 | Topic: How to Change Router DNS | Content verified for accuracy and freshness.
References
- RFC 2132: DHCP Options and BOOTP Vendor Extensions | RFC Editor
- RFC 3646: DNS Configuration options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6) | R…
- RFC 1035: Domain names – implementation and specification | RFC Editor
- Domain Name System
- Dynamic Host Configuration Protocol
- Making sure you're not a bot!
- Making sure you're not a bot!
- https://scholar.google.com/scholar?q=change+router+DNS Google Scholar
- https://scholar.google.com/scholar?q=DHCP+option+6+DNS+server+router+configuration Google Scholar
- https://scholar.google.com/scholar?q=configure+DNS+servers+on+home+router+DHCP Google Scholar
2 thoughts on “How to Change Router DNS: Step-by-Step Settings Guide”