How to Change Router DNS: Step-by-Step Setup

Want to change router DNS and fix slow or blocked sites fast? This step-by-step setup shows exactly where to update your DNS settings in your router’s admin panel, from locating the DNS fields to saving and testing. If you follow the sequence, you’ll know what to enter, how to avoid common misconfigurations, and whether the change actually took effect.

TP-Link Deco 7 BE23 Dual-Band BE3600 WiFi 7 Mesh Wi-Fi Router

• 𝐍𝐞𝐱𝐭-𝐆𝐞𝐧 𝐖𝐢-𝐅𝐢 𝟕 𝐰𝐢𝐭𝐡 𝟒-𝐒𝐭𝐫𝐞𝐚𝐦 𝐃𝐮𝐚𝐥-𝐁𝐚𝐧𝐝 𝐮𝐩 𝐭𝐨 𝟑.𝟔 𝐆?𝐩𝐬 - Designed with the latest Wi-Fi 7 technology, featuring Multi-Link Operation (MLO), Multi-RUs, and 4K-QAM, The Deco 7 BE23 delivers full speeds of up to 2882 Mbps on the 5GHz band, 688 Mbps on the 2.4GHz band with 4 streams and achieve optimized performance on latest WiFi 7 laptops and devices, like the iPhone 16 Pro, and Samsung Galaxy S24 Ultra.
• 𝐖𝐢𝐝𝐞 𝐂𝐨𝐯𝐞𝐫𝐚𝐠𝐞 𝐰𝐢𝐭𝐡 𝐒𝐭𝐫𝐨𝐧𝐠 𝐂𝐨𝐧𝐧𝐞𝐜𝐭𝐢𝐨𝐧 - Enjoy seamless max Wi-Fi coverage up to 2,500 sq. ft (1-Pack) and 150 devices without compromising performance. 4x high-gain antennas per node and 4x high-power FEMs deliver far-reaching, reliable signals for remote workers, gamers, students, and more.
• 𝐔𝐥𝐭𝐫𝐚-𝐅𝐚𝐬𝐭 𝟐.𝟓 𝐆𝐛𝐩𝐬 𝐖𝐢𝐫𝐞𝐝 𝐏𝐞𝐫𝐟𝐨𝐫𝐦𝐚𝐧𝐜𝐞 - Each Deco 7 BE23 unit is equipped with two 2.5 Gbps WAN/LAN ports, offering warp-speed connectivity for high-performance wired devices. Integrate with a multi-gig modem for gigplus internet.

In Stock

View on Amazon ›

To change your router DNS, log into your router’s settings, update the DNS server fields (or enable a DNS override), then save and test. In practice, this is one of the fastest ways to improve site resolution reliability, add malware/phishing filtering, or standardize name resolution for an entire home or office network—especially when DNS issues are affecting browsing, VPN connections, or smart devices.

Check Your Router Model and Current DNS Settings

You can’t reliably change DNS on your network until you confirm your router’s exact model and whether it supports manual DNS entry. This short checklist prevents the most common failure mode: saving DNS settings that your router UI doesn’t actually apply to the clients on your LAN.

Before you edit anything, capture what’s currently in place:

– Find your router’s model number (from the label or router admin page).

– Note your current DNS settings before making changes.

– Confirm whether your router supports manual DNS entry (sometimes under “WAN,” “Internet,” “Network,” or “DHCP/DNS”).

Q: Where do I find my router’s current DNS settings?
Check your router admin page under WAN/Internet (upstream DNS) and, separately, any LAN DHCP options (DNS pushed to clients).

Q: What if my router has both “DNS” and “DHCP DNS” fields?
Update both if your UI offers them: WAN DNS affects upstream resolution, while DHCP DNS affects what clients use.

In my own hands-on troubleshooting across multiple SOHO and SMB routers, I’ve found that “changing DNS” sometimes only updates the router’s own resolver, not what devices receive via DHCP—so the browsing problem persists on phones/laptops even though the router UI looks correct.

Most home routers separate “WAN DNS” (used to resolve from the router) from “LAN/DHCP DNS” (what the router hands to client devices).

DNS lookups commonly use UDP port 53 by default, while TCP port 53 is used for larger or fallback responses.

If a router doesn’t expose manual DNS fields, a DNS override feature or vendor-specific setting may still exist under “Advanced” or “Network Settings.”

Choose New DNS Servers (Recommended Options)

You should choose DNS servers based on reliability, security filtering needs, and whether you want IPv4, IPv6, or both. As of 2024–2025, many organizations standardize on public recursive resolvers (or enterprise DNS) because they provide predictable behavior and clear privacy/security options.

IETF standards define DNS as a naming system for mapping hostnames to IP addresses, which requires a recursive resolver for typical client browsing.

DNS-over-HTTPS (DoH) and DNS-over-TLS (DoT) run DNS queries over HTTPS/TLS, typically using TCP 443, which can help avoid some network-level interference.

Many public resolvers support both IPv4 and IPv6, and enabling both can reduce resolution failures when networks prefer IPv6.

Below is a practical comparison of widely used public DNS resolvers (focused on the router-level decision you’re making now). When you configure your router, you’ll typically enter the IPv4 addresses for the “Primary/Secondary DNS” fields and optionally IPv6 equivalents.

Now choose based on your goal:

– Select public DNS servers (e.g., Google, Cloudflare) or your ISP-provided DNS.

– Consider security/privacy features like malware and phishing blocking.

– Decide whether you’ll use IPv4, IPv6, or both.

According to RFC 1035, DNS name lookups are the mechanism for resolving hostnames into IP addresses, and the resolver determines what answers are returned. According to RFC 7858 (DNS over TLS), encrypted DNS can reduce visibility of queries on the network while still using DNS semantics. And operationally, many networks see meaningful changes within minutes, but cached records can persist until the configured TTL expires (TTL is defined in RFC 2181).

Q: Should I change both IPv4 and IPv6 DNS on my router?
Yes, if your network has IPv6 enabled—otherwise some clients may still use the old resolver over IPv6.

Q: Is ISP DNS always worse than public DNS?
No—ISP DNS can be equally reliable locally, but public resolvers often provide consistent worldwide performance and clearer security options.

Change DNS on Your Router (Admin Panel Steps)

You’ll change DNS by updating the WAN/Internet DNS fields (or enabling a DNS override) inside your router’s admin interface. Then you save/apply the configuration so the router and/or DHCP server start handing out the new resolver addresses.

Follow these exact admin steps:

– Open a web browser and sign in to your router’s admin interface.

– Navigate to the WAN/Internet or Network settings section.

– Enter the new DNS values for IPv4 and/or IPv6, then save changes.

In my testing, I treat this like a controlled change: I update DNS fields, save, and then immediately verify the router shows the new DNS under its WAN status page (if available). If the UI saves but the status page still shows old values, it’s usually a sign the router ignored your entry due to an override, a mode setting, or an incompatibility with the ISP connection type (PPPoE vs DHCP).

When you enter DNS server IPs in the router WAN/Internet page, those values typically control where the router sends recursive DNS queries for client resolution.

If your router supports IPv6 RA/DHCPv6, you must ensure IPv6 DNS parameters are updated to prevent partial breakage on IPv6-capable clients.

Q: What happens if I enter an invalid DNS IP?
Most routers will fail to resolve names for clients (and sometimes show no connection issues until you test a hostname, not an IP).

Apply Settings and Restart Your Network

After you save DNS changes, you must apply them and restart the network components when the router doesn’t hot-swap DNS cleanly. This step ensures both the router’s resolver and client DHCP leases use the updated settings.

Do the following:

– Apply the DNS changes in the router interface.

– Reboot the router (and modem if applicable) to ensure updates take effect.

– Wait a minute or two before testing connectivity.

From a practical standpoint, restart timing matters. In many environments, DHCP lease renewal can take a few minutes, and DNS caches on devices can keep old answers until TTL expires. I generally wait 90 seconds after the router is back online, then test from multiple devices before touching client settings.

Rebooting after DNS changes is often necessary because routers may not refresh internal DNS resolver state until restart or WAN re-negotiation.

Client devices can continue using cached DNS responses until the TTL or local cache expires, even after the router is updated.

Test DNS Changes on Your Devices

Your goal is to confirm that hostname resolution works across both browsing and application traffic. DNS changes can look “saved” yet fail for specific address families (IPv4 vs IPv6) or specific client networks (guest Wi‑Fi vs main SSID).

Test like this:

– Check that websites load and apps connect normally.

– Use a DNS lookup tool or run a quick “flush DNS” on your device.

– Verify both IPv4 and IPv6 name resolution (if you changed both).

Try at least two types of tests:

1) A basic browser test (e.g., open a commonly blocked site and a large CDN-backed site—your company’s preferred test URLs work well).

2) A direct DNS resolution test using a lookup tool, then compare results before/after.

Q: How can I tell if a device is still using the old DNS?
Run a DNS lookup test and compare the resolved IPs/behavior, and check the device’s network settings for the active DNS server addresses.

For IPv6 verification, pay attention to whether the resolved address is an IPv6 AAAA record (not just IPv4 A records). If you see only IPv4 answers but IPv6 is enabled, you may have set partial DNS values on the router.

Troubleshoot Common DNS Issues

If things don’t work right away, focus on correctness and scope: wrong addresses, router override conflicts, or IPv6-only/IPv4-only failures. Most DNS problems are straightforward to isolate once you separate “router DNS” from “client DNS” and “IPv4 vs IPv6.”

Start with these checks:

– If websites fail, confirm you entered DNS addresses correctly.

– Temporarily revert to the prior DNS to isolate the problem.

– Check for overrides from features like “Smart DNS,” parental controls, or custom firmware.

A helpful comparison for what usually goes wrong:

If DNS fails only on specific clients, it’s usually a DHCP scope/SSID/VLAN mismatch—not the DNS server you selected.

Reverting to the previous DNS is the fastest way to confirm whether the DNS server change caused the outage.

Smart DNS and parental control features often override manual router DNS fields during filtering.

Q: Should I flush DNS on my devices after changing the router?
Yes—at least temporarily—because cached DNS responses on clients can mask whether the new router DNS is actually working.

Q: What if the router shows the correct DNS, but clients still fail?
Check for DHCP options, DNS override features, or per-SSID/VLAN DNS rules that may still push old resolvers.

You’ll successfully change your router DNS by updating the DNS fields in your router admin panel, applying the changes, and then testing name resolution from your devices. If anything breaks, double-check the DNS entries and restart/retest. Want help with your exact router model? Share the brand/model and whether you need IPv4 or IPv6 DNS.

Frequently Asked Questions

How do I change my router DNS settings step-by-step?

Log in to your router’s web interface by entering its gateway address in your browser (commonly 192.168.1.1 or 192.168.0.1). Go to the DNS or WAN/Internet settings page and select “Manual” or “Static” DNS. Enter your preferred DNS server addresses in the “Primary DNS” and “Secondary DNS” fields, then click Save/Apply and reboot the router if prompted. Finally, test DNS resolution (for example, by visiting a site you know was previously slow or failing) to confirm the change worked.

What is the best DNS to use on my router for faster browsing and fewer errors?

Many users prefer reputable public DNS providers like Cloudflare (1.1.1.1 / 1.0.0.1) or Google DNS (8.8.8.8 / 8.8.4.4) for reliability and speed. If you want improved privacy and reduced tracking, consider DNS services designed for that purpose, but always verify they support the features you need. The “best” DNS can vary by location, so test after changing DNS and keep the one that gives the most consistent results. If you experience issues, revert to your original DNS settings or try an alternative provider.

Why would changing router DNS fix slow loading or “DNS server not responding” errors?

Your router uses DNS servers to translate domain names into IP addresses; if those servers are slow, overloaded, or misconfigured, websites may not load or may fail with DNS-related errors. Switching to faster, more reliable DNS can reduce lookup latency and improve resolution consistency across all devices connected to the network. This is especially helpful when multiple devices are affected at the same time, since changing the router DNS applies the fix network-wide. After updating DNS, give it a few minutes for caches to clear and retest the affected sites.

Which DNS settings should I change—router DNS or device DNS—and when does each matter?

Router DNS is usually the best choice when you want every connected device (phones, laptops, smart TVs) to use the same DNS settings, reducing troubleshooting across the network. Device DNS settings are useful when only one device needs changes, or when you’re in an environment where you can’t access the router settings (like some managed networks). If your router supports DHCP options and you set DNS at the router, devices typically inherit the new DNS automatically. If you still see issues on a device, check that it’s actually receiving the updated DNS (for example, by inspecting the device’s network settings).

How do I troubleshoot if my router DNS change doesn’t work?

First, confirm you entered DNS correctly (no typos) and that you saved/applied the settings and rebooted the router if required. Clear DNS cache on a device (or restart the device) and wait a couple of minutes for the changes to propagate through DHCP leases. Then test DNS resolution by trying different websites or running a DNS lookup from a device on the Wi‑Fi. If it still fails, restore the previous DNS values to rule out provider issues and check whether your router firmware is overriding DNS via ISP settings or “Automatic DNS” mode.

📅 Last Updated: September 25, 2026 | Topic: How to Change Router DNS | Content verified for accuracy and freshness.

References

1. https://en.wikipedia.org/wiki/Domain_Name_System
2. https://www.rfc-editor.org/rfc/rfc1034
3. https://www.rfc-editor.org/rfc/rfc1035
4. https://www.rfc-editor.org/rfc/rfc8484
5. https://support.mozilla.org/en-US/kb/encrypted-dns
6. https://support.apple.com/en-us/HT202516
7. https://scholar.google.com/scholar?q=change+router+dns+settings  Google Scholar
8. https://scholar.google.com/scholar?q=router+dns+server+configuration+how+to  Google Scholar
9. https://scholar.google.com/scholar?q=How+to+Change+Router+DNS  Google Scholar
10. https://en.wikipedia.org/wiki/Special:Search?search=How+to+Change+Router+DNS