Owen Bradley Every time you type a web address, your device asks a DNS server to translate that name into an IP address before a single byte of the page loads. By default that lookup goes to whatever server your internet provider assigned, and those servers are frequently slower, less reliable, and more prone to outages than the free public alternatives. Changing DNS servers on your router applies a better resolver to every device in the house at once, from laptops to phones to smart televisions that offer no settings of their own. The change takes about five minutes, requires no new hardware, and is completely reversible. This guide walks through choosing a resolver, making the change on a typical router, verifying it worked, and rolling back cleanly if something stops resolving.
What Changing DNS Actually Does
DNS is the phone book of the internet. Loading a typical page can trigger dozens of lookups for the site itself plus its images, fonts, scripts, and analytics. If each of those takes 60 milliseconds instead of 15, the delay accumulates into something you can feel, especially on the first visit to a site before anything is cached.
Switching resolvers does not increase your connection’s bandwidth. A large download will not finish faster. What improves is the responsiveness before content starts flowing, plus reliability, since major public resolvers run globally distributed infrastructure with far more redundancy than a regional provider. Many also add security filtering that blocks known malware and phishing domains before your browser ever reaches them.
Router Level Versus Device Level
You can change DNS on an individual computer, but doing it at the router covers everything automatically. The router hands its DNS settings to each device through DHCP, so a new phone joining the network inherits the change without anyone touching it. That is especially valuable for streaming boxes, consoles, and smart home gadgets that bury or omit network settings entirely.
Choosing a DNS Provider
Pick based on what you want out of it. Broadly there are three categories:
- Speed and privacy focused resolvers that answer quickly and commit to not logging or selling query data. These are the default choice for most households.
- Security filtering resolvers that block malware, phishing, and botnet domains at the DNS layer. The protection applies before a connection is made, which helps devices that cannot run security software.
- Family filtering resolvers that additionally block adult content categories network wide, useful as a coarse first layer alongside proper parental controls.
Whatever you choose, get two addresses: a primary and a secondary from the same provider, or a secondary from a different provider for redundancy. A single entry leaves you with no fallback if that server has trouble. Write down your existing values before changing anything, since that is your rollback path.
Testing Which Resolver Is Fastest for You
Speed is geographic. The resolver that wins in one city loses in another, so a five-minute test beats any recommendation. Command line tools that time repeated lookups against several resolvers will show you actual response times from your location. Test each candidate against a handful of domains you visit often, run each a few times, and compare the averages. Differences under about 5 milliseconds are noise; differences of 30 milliseconds or more are worth acting on.
Step-by-Step: Changing DNS on Your Router
- Find your router’s address. It is usually printed on a label on the device, commonly something like 192.168.1.1 or 192.168.0.1. On a computer, the default gateway shown in your network settings is the same address.
- Log in to the admin interface. Enter that address in a browser, or open the manufacturer’s mobile app if your router uses one. Sign in with the admin credentials. If you have never changed them from the printed defaults, do that now while you are here.
- Record the current DNS values. Before editing anything, screenshot or write down the existing entries and note whether they were set to automatic. This is your undo button.
- Locate the DNS fields. The setting hides in different places by brand. Look under Internet, WAN, Network, LAN, or Advanced, often on the same page where DHCP is configured. Some interfaces label it Domain Name Server or Name Server.
- Switch from automatic to manual. There is nearly always a radio button or dropdown reading something like “Get DNS automatically from ISP” versus “Use these DNS servers.” Select the manual option, which reveals the entry fields.
- Enter the primary and secondary addresses. Type them carefully; a single wrong digit produces a network where nothing resolves and the cause is not obvious. Leave any tertiary field blank unless you have a third address.
- Save and apply. The router will usually confirm and may briefly drop the connection while it applies the change. Some models require a reboot; if there is a prompt, accept it.
- Renew addresses on your devices. Devices hold their DHCP lease and will keep using the old DNS until it renews. Toggle Wi-Fi off and on, unplug and replug ethernet, or simply reboot each device to pick up the new settings immediately.
- Flush local DNS caches. Operating systems and browsers cache lookups. Clearing the system resolver cache and restarting your browser ensures you are testing the new server rather than old cached answers.
- Verify the change took effect. Use an online DNS leak or “what is my DNS server” test page from a device on the network. It should report your new provider rather than your ISP. Then browse normally for a while and watch for anything that fails to load.
When the Router Will Not Cooperate
Some ISP-supplied routers lock the DNS fields, greying them out or ignoring changes. You have three options. First, check whether the device can run in bridge or modem-only mode, letting your own router handle routing and DNS. Second, set DNS in the DHCP or LAN section rather than the WAN section, since many locked routers still allow you to specify what gets handed to clients even when the router’s own upstream is fixed. Third, replace the unit with your own router, which also usually improves Wi-Fi and gives you real control over the network.
If you are considering that last route, our roundup of the best Wi-Fi routers for home internet is a good starting point, and the best home internet routers covers models that pair well with common service types. Anyone who wants the setup to be genuinely simple should look at the best routers for beginners, which favour clear apps over dense admin pages.
Pairing DNS With Security and Filtering
DNS filtering is a useful layer, but it is not a complete security control. It cannot inspect encrypted traffic or stop a threat that arrives by direct IP address. Treat it as one part of a stack. Routers with built-in threat protection and automatic firmware updates add meaningful depth, and our guide to the best secure Wi-Fi routers with built-in protection compares those features. If content filtering for children is the goal, dedicated scheduling and per-device rules work far better than DNS alone; see the best parental control routers for options that combine both approaches.
Troubleshooting and Rollback
Nothing loads at all. A typo in the DNS address is the overwhelming favourite. Log back into the router, re-check every digit, or set the fields back to automatic to restore service instantly while you investigate.
Some sites work and others do not. This often points to a filtering resolver blocking a category, or to a local service that relies on your ISP’s internal DNS records. Try the secondary resolver alone, or add an exception if your provider offers a dashboard.
Devices still show the old server. The DHCP lease has not renewed. Reboot the device, or reboot the router so all leases refresh together.
Local devices stop resolving by name. Printers, NAS boxes, and casting targets sometimes rely on the router’s own resolver for local hostnames. If those break, set the router itself as the DNS server handed to clients and configure the public resolvers as the router’s upstream instead.
To roll back completely, return the setting to automatic, save, and reboot the router. Because DNS is not stored on client devices permanently, everything returns to normal as soon as leases renew.
Frequently Asked Questions
Will changing DNS make my internet faster?
It reduces the delay before pages begin loading, which feels faster during browsing, but it does not change your download or upload bandwidth. The gain is largest if your provider’s resolver was slow or overloaded.
Is it safe to use a public DNS provider?
Reputable public resolvers are widely used and generally safer than the default in terms of both uptime and malware filtering. Read the provider’s logging policy, since that is the main practical difference between them.
Do I need to change DNS on every device too?
No. Setting it once on the router covers every device that gets its network configuration automatically. Only devices with manually configured DNS need individual attention.
Can I use DNS to block ads across the network?
Some public resolvers offer ad-blocking variants that work network wide, and dedicated filtering software on a small always-on device gives finer control. Both work at the same DNS layer you just configured.
Final Thoughts
Changing DNS servers on your router is one of the few network tweaks that is quick, free, reversible, and genuinely noticeable. Record the old values, choose a primary and a secondary from providers whose priorities match yours, enter them carefully in the router’s WAN or DHCP section, then renew leases and verify with an external test rather than assuming it worked. If anything misbehaves, flipping the setting back to automatic restores the previous state within a reboot. Spend the ten minutes once and every device in the house browses a little more responsively for the rest of 2026.
