Why Change DNS at the Router Level
By default, your router hands out your ISP's DNS servers to every connected device via DHCP. Setting DNS on the router itself — rather than on each individual device — means every device on the network inherits the new resolver automatically, including devices you can't easily configure yourself (smart TVs, IoT sensors, guest devices).
Router-level DNS is the right layer for three common goals: faster page-load times from a lower-latency resolver, ad/tracker filtering through resolvers like NextDNS or AdGuard DNS, and defending against DNS hijacking, where malware or a compromised ISP silently redirects your DNS queries. If your router's DNS settings changed and you didn't do it, treat that as a compromise signal — check for unauthorized WAN DNS entries first.
Router DNS is a WAN-side setting, distinct from DNS cache, which is a local, per-device store of resolved lookups. If you're troubleshooting stale results after switching resolvers, see How to Flush DNS Cache — a router-level change won't clear cache already held by client devices.
Before You Start
You need three things before touching router settings:
- Your router's admin IP. Most consumer routers use
192.168.1.1,192.168.0.1, or a vendor login domain (tplinkwifi.net,routerlogin.net). If you don't know yours, runipconfig(Windows) ornetstat -nr | grep default(Mac/Linux) and read the "Default Gateway" line — see Router IP Address Guide for the full lookup process. - Admin credentials. Printed on a sticker on the router, or the ISP-set default if you never changed it. Rotate this password after your first login if it's still the factory default.
- Two DNS server IPs — a primary and secondary — from the resolver you're switching to (see recommended servers below).
How to Change DNS on TP-Link Routers {#tp-link}
-
Log in. Open
http://tplinkwifi.netor192.168.0.1in a browser and sign in with your admin credentials. -
Navigate to the DNS field. On the newer TP-Link web UI, go to Advanced → Network → Internet. On the classic UI, go to Network → WAN.
-
Switch off automatic DNS. Select Use the following DNS addresses and enter your Primary DNS and Secondary DNS.
-
Save and reboot. Click Save, then power-cycle the router so DHCP re-issues the new DNS to connected clients.
Per TP-Link's official DNS FAQ, the router must be rebooted after saving for the new DNS servers to take effect on already-connected devices.
How to Change DNS on Netgear Routers {#netgear}
-
Log in at
192.168.1.1orrouterlogin.net. -
Open Internet settings. Genie-style firmware: Advanced → Setup → Internet Setup. Newer Nighthawk apps use Advanced → Advanced Setup → Internet Setup.
-
Set DNS manually. Under Domain Name Server (DNS) Address, select Use These DNS Servers and enter your Primary and Secondary DNS.
-
Apply. Click Apply; most Netgear firmware applies WAN DNS changes without a full reboot, but a reboot is the safe default if devices don't pick up the change within a few minutes.
How to Change DNS on Asus Routers {#asus}
-
Log in at
192.168.1.1orrouter.asus.com. -
Go to WAN. Navigate to WAN → Internet Connection → WAN DNS Setting.
-
Disable automatic DNS. Set Connect to DNS Server automatically to No. Two fields appear for DNS Server 1 and DNS Server 2.
-
Apply. Click Apply.
Per Asus's official support article, this WAN-level setting overrides the DNS the router would otherwise pull from your ISP via DHCP or PPPoE.
How to Change DNS on Linksys Routers {#linksys}
-
Log in at
192.168.1.1or through the Linksys app. -
Open Internet Settings. In the web UI: Connectivity → Internet Settings → Internet Connection type. In the app: Menu → Router Settings → Internet Settings.
-
Enter static DNS. Toggle from Automatic DNS to Manual/Static DNS Settings and enter your Primary and Secondary DNS.
-
Save. The Linksys app applies changes without requiring a manual reboot in most cases; classic firmware may prompt one.
How to Change DNS on D-Link Routers {#d-link}
-
Log in at
192.168.0.1ordlinkrouter.local. -
Open WAN settings. Go to Setup → Internet → Manual Internet Connection Setup, or Advanced → DNS depending on model.
-
Enter DNS manually. Uncheck/disable "Get DNS Server Address Automatically" and fill in Primary and Secondary DNS.
-
Save Settings, then reboot if the new servers aren't picked up by clients within a few minutes.
Recommended DNS Servers
| Provider | Primary | Secondary | Notable for |
|---|---|---|---|
| Cloudflare | 1.1.1.1 | 1.0.0.1 | Speed, privacy (no query logging) |
| Google Public DNS | 8.8.8.8 | 8.8.4.4 | Reliability, wide global anycast |
| Quad9 | 9.9.9.9 | 149.112.112.112 | Malware/phishing domain blocking |
| OpenDNS (Cisco) | 208.67.222.222 | 208.67.220.220 | Content filtering, family shield option |
| AdGuard DNS | 94.140.14.14 | 94.140.15.15 | Ad and tracker blocking |
Any pair here works as a drop-in replacement for your ISP's default. If you specifically want router-side ad blocking, use AdGuard or NextDNS instead of the general-purpose resolvers.
Verify the Change Took Effect
After saving and rebooting, confirm the router — not just one device — is actually using the new resolver:
- From a connected device, run a lookup and check which server answered:
nslookup example.com
If the "Server" line in the output still shows your old ISP resolver's IP, the router hasn't pushed the change to DHCP clients yet — reboot the device or renew its DHCP lease.
-
Cross-check propagation and resolution independently of your own network using the DNS Lookup tool and the DNS Propagation Checker — these query public resolvers directly, so they confirm the record itself resolves correctly regardless of your router's cache state.
-
If you're troubleshooting a domain you manage (not just router DNS), use the NS Lookup tool to confirm authoritative nameservers, and Reverse DNS to confirm PTR records if that's part of what you're debugging.
Troubleshooting
DNS changes don't stick after reboot. Some ISP-supplied gateways lock WAN DNS to the ISP's servers regardless of what you enter, especially on PPPoE or DHCP WAN types tied to an ISP profile. If your router is a rented ISP gateway, ask about bridge mode or set DNS at the OS/device level instead — see How to Change DNS Servers for per-device instructions.
Devices still resolve through the old DNS server. DHCP leases cache the old DNS assignment until they expire or are renewed. Force a renewal (ipconfig /release && ipconfig /renew on Windows, or disconnect/reconnect Wi-Fi on mobile) rather than waiting out the lease.
Some sites load slowly or fail intermittently after the switch. This usually points to the new resolver being rate-limited or geographically distant, not a misconfiguration. Test with a different provider from the table above before assuming the router setting is wrong.
Router shows "DNS Server Not Responding." This is a resolver reachability issue, not a router bug in most cases — see DNS Server Not Responding: Fix Guide for the full diagnostic path, including checking whether outbound UDP/53 is being blocked by the ISP.
You didn't change DNS but it's different from default. Unauthorized WAN DNS entries are a known malware/router-hijack pattern. Change the admin password immediately, verify firmware is current, and reset DNS to a trusted provider.
Key Takeaways
- ✓ Router-level DNS changes apply to every connected device via DHCP — no per-device configuration needed.
- ✓ The setting lives under WAN or Internet settings, not LAN or Wireless settings, on every major router brand.
- ✓ A reboot or DHCP lease renewal is usually required before clients pick up the new servers (TP-Link, 2026).
- ✓ Verify with an external tool like the DNS Lookup tool rather than trusting the router UI alone — some ISP gateways silently revert custom DNS.
- ✓ Unexplained WAN DNS changes are a hijacking indicator, not routine drift.
Frequently Asked Questions
Q: How do I find my router's DNS settings page?
Log in to your router's admin panel at its gateway IP (commonly 192.168.1.1 or 192.168.0.1), then look under WAN, Internet, or Internet Setup — DNS is a WAN-side field, not under Wireless or LAN settings.
Q: Do I need to change DNS on every device if I set it on the router?
No. Router-level DNS is inherited by every device that gets its network config via DHCP from that router, which is the default for nearly all home devices.
Q: Will changing my router's DNS break my internet connection?
No, as long as you enter valid, reachable DNS server IPs. If a site stops resolving, double-check for typos in the entered addresses or revert to automatic/ISP DNS to confirm the router itself is fine.
Q: Why does my router keep reverting to the ISP's DNS servers?
Some ISP-locked gateways override manual WAN DNS on certain connection types (particularly PPPoE profiles tied to the ISP). If this happens repeatedly, set DNS at the device or OS level instead, or ask your ISP about enabling bridge mode.
Q: What's the difference between changing router DNS and flushing DNS cache?
Router DNS changes which resolver answers future queries; DNS cache is already-stored answers from prior queries held locally on a device. After a router DNS change, stale cached entries can still cause old results until they expire or are flushed — see How to Flush DNS Cache.
Q: Is it safe to use a third-party DNS provider on my router?
Yes, for reputable providers like Cloudflare, Google, or Quad9. Avoid unfamiliar "free" DNS services, since a malicious resolver can redirect traffic or log every domain you visit.
Q: How do I set separate primary and secondary DNS servers?
Nearly every router's DNS field has two boxes — Primary DNS and Secondary DNS. The secondary server is only used if the primary doesn't respond, so pair servers from the same provider (e.g., Cloudflare's 1.1.1.1 and 1.0.0.1) for consistent behavior.
Next Steps
Once your router's DNS is set, confirm it end-to-end: check the resolved record with the DNS Lookup tool, watch it propagate globally with the DNS Propagation Checker, and confirm authoritative nameservers with the NS Lookup tool if you also manage the domain itself.