Changing DNS at the router level can improve privacy, speed, filtering, and reliability for every device on your network.
This guide explains how to change DNS on router safely, with the checks that prevent lockouts, broken internet access, and hidden configuration conflicts.
What DNS does on a router
DNS, or Domain Name System, translates human-friendly domain names like example.com into IP addresses that devices can reach.
When you set DNS on the router, every connected device usually inherits those resolvers unless a device uses its own manual DNS or encrypted DNS service.
That makes router-level DNS powerful for families, small businesses, and home labs because a single change can affect phones, laptops, smart TVs, game consoles, and IoT devices.
It also means a mistake can affect the whole network, so the safest approach is to prepare before editing settings.
Before you change anything
Preparation is the most important part of changing DNS safely.
A few minutes of planning reduces the chance of losing access to the router admin page or disconnecting the network from the internet.
Record your current network settings
- Write down the router’s LAN IP address, admin username, and backup password.
- Note the current WAN and DNS settings in case you need to revert.
- Save the router model, firmware version, and ISP details.
Choose reputable DNS providers
Select a provider with a strong operational record, clear privacy policy, and geographically distributed infrastructure.
Common options include Google Public DNS, Cloudflare DNS, Quad9, OpenDNS, and ISP-provided DNS if you prioritize compatibility over filtering features.
For most users, the best DNS servers are the ones that match the goal:
- Privacy-focused: Cloudflare, Quad9
- Filtering and family controls: OpenDNS, NextDNS
- Simple, broadly available: Google Public DNS
Check whether your ISP uses special DNS requirements
Some internet service providers rely on custom DNS settings for captive portals, IPTV, VoIP, or troubleshooting workflows.
Business networks may also use internal DNS resolvers for local hostnames and shared resources.
If that applies, plan a test window and keep the ISP’s DNS addresses available as a fallback.
How to change DNS on router safely
The exact menu names vary by vendor, but the process is similar on ASUS, TP-Link, Netgear, Linksys, Ubiquiti, MikroTik, and many ISP gateways.
The safest method is to change DNS in the router’s internet or WAN settings, then confirm that clients are actually using the new resolvers.
Step 1: Log in to the router admin panel
Connect to the router using a stable device, ideally by Ethernet.
Open the router’s local management address, such as 192.168.1.1, 192.168.0.1, or the custom gateway address listed on the device label or in your network settings.
Use the admin credentials you recorded earlier.
If the router supports multi-factor authentication, enable it before making changes.
Step 2: Find the DNS settings
Look for one of these sections: Internet, WAN, Advanced, Network, DHCP, or LAN settings.
Some routers separate DNS for the WAN connection and DNS handed out to clients via DHCP.
In that case, set both if your goal is full-network coverage.
Step 3: Enter primary and secondary DNS servers
Enter the resolver IP addresses provided by your chosen DNS service.
Most routers allow two or more fields.
Use a primary and secondary server from the same provider unless the documentation recommends otherwise.
- Primary DNS: first resolver address
- Secondary DNS: backup resolver address
- Optional tertiary DNS: only if the router supports it and the provider documents one
Avoid mixing unrelated providers unless you understand the privacy and routing implications.
Different resolvers can lead to inconsistent content filtering, split geolocation results, or uneven performance.
Step 4: Save and apply carefully
Apply the change and wait for the router to restart services if necessary.
Some devices reconnect the WAN link automatically, while others require a short reboot.
During this time, do not repeatedly refresh the admin panel or power-cycle the router unless it is clearly frozen.
Step 5: Renew client connections
After the router saves the new DNS settings, refresh devices so they request updated network information.
The easiest methods are reconnecting Wi-Fi, toggling airplane mode on mobile devices, renewing DHCP leases, or rebooting clients that cache network parameters aggressively.
How to verify the new DNS is working
Verification is what separates a safe change from a guess.
A DNS change can appear successful in the router interface while some devices continue using old resolvers or hardcoded DNS values.
Use a DNS leak or resolver test
Visit a DNS test site or use command-line tools to confirm which resolvers your device is using.
If the reported servers match the ones you set, the router change is likely working as intended.
Useful commands include:
- Windows: ipconfig /all and nslookup
- macOS and Linux: dig, nslookup, or resolvectl
- Network-wide testing: browser-based DNS checker tools
Test normal browsing and local services
Open several websites, especially ones that previously loaded slowly or had certificate issues.
Then test local resources such as printers, NAS devices, smart home hubs, or internal hostnames to make sure your network still resolves local names correctly.
Common mistakes to avoid
Most DNS problems come from a few predictable configuration errors.
Avoiding them is the easiest way to change DNS safely without support calls or downtime.
- Using invalid IP addresses: DNS entries must be resolver IPs, not website URLs.
- Forgetting DHCP settings: Devices may keep old DNS unless DHCP is updated or leases are renewed.
- Mixing public and private DNS: This can break internal hostnames or filtering policies.
- Overlooking IPv6: If IPv6 is enabled, set IPv6 DNS too, or clients may continue using different resolvers.
- Changing too many settings at once: Make one change, test it, then move to the next.
When router DNS is not enough
Some devices and applications can bypass router DNS entirely.
Modern operating systems may use DNS over HTTPS, DNS over TLS, or hardcoded resolver settings.
Browsers like Chrome, Firefox, and Edge can also override network DNS if secure DNS is enabled.
If you want consistent network-wide control, review these layers:
- Browser secure DNS settings
- Operating system DNS-over-HTTPS or private DNS options
- VPN client DNS behavior
- Separate guest networks or VLANs
In managed environments, network administrators may prefer DHCP and firewall rules to enforce resolver usage, especially where compliance or content filtering matters.
How to revert if something goes wrong
If internet access fails after the change, revert to the previous DNS settings immediately.
Having the original resolver addresses written down lets you restore service quickly without resetting the router to factory defaults.
If you still cannot browse after restoring the old values, check whether the problem is actually caused by WAN connectivity, modem sync issues, IPv6 conflicts, or a failed router reboot.
In those cases, a basic reboot sequence of modem first, router second, and client devices last can restore service.
Best practices for ongoing DNS management
Once DNS is stable, treat it like any other core network setting.
Keep firmware updated, monitor provider status pages, and review settings after router upgrades or ISP hardware swaps.
- Document the chosen DNS provider and purpose.
- Keep backup resolver addresses in a safe note or password manager.
- Re-test after firmware updates or ISP changes.
- Confirm IPv4 and IPv6 DNS consistency.
- Review device-level DNS settings on new hardware.
For households with children, DNS can also support content filtering and safer browsing policies.
For remote workers, it can improve reachability and reduce lookup delays.
For privacy-conscious users, it can reduce exposure to ISP-level DNS logging, depending on the provider and browser settings used.