How to Change Wi-Fi Router DNS Settings for Faster Browsing

Every time you open a website, your device first has to find out where that site lives on the internet. That lookup is handled by a DNS server, and if the one your network uses is slow or unreliable, pages can hesitate before they even start loading. Learning how to change your Wi-Fi router’s DNS settings for faster browsing lets you switch every device on your home network to a better resolver at once, without configuring each phone, laptop, and smart TV separately.

This guide explains what DNS actually does, how to choose and benchmark a provider, where to find the DNS fields in your router admin panel, and how to confirm the change worked. It also covers the limitations, because a new DNS server can make browsing feel snappier, but it cannot fix every kind of slowdown.

Key Takeaways

• DNS affects how quickly a page starts loading, not your overall internet bandwidth
• Public resolvers like Cloudflare, Google, and Quad9 differ in privacy, filtering, and speed by location
• Benchmark resolvers from your own network before switching
• DNS fields usually sit under WAN, Internet, or DHCP settings, depending on the router brand
• Reconnect devices, flush caches, and verify the active resolver, since some devices and browsers bypass the router

What DNS Does and How It Affects Browsing Speed

DNS, the Domain Name System, translates human-friendly names like todaytechtips.com into the numeric IP addresses computers use to connect. When you type a web address, your device asks a DNS resolver for the matching IP address. Only after it receives an answer can your browser begin connecting to the website’s server.

The time this takes is called lookup latency. A fast resolver might answer in a few milliseconds, while a slow or overloaded one can take far longer, and occasionally time out entirely. A single modern web page often pulls content from many different domains, such as image hosts, font services, and analytics providers, so slow lookups can add up before the page appears.

How DNS Caching Works

DNS answers are cached at several levels: in your browser, your operating system, often your router, and the resolver itself. Once a name has been looked up, repeat visits can skip most of the delay until the cached record expires. This is why switching resolvers tends to make the biggest difference on sites you visit for the first time or less frequently, and less difference on sites you open all day.

What DNS Cannot Do

It is important to set expectations correctly. Changing DNS does not increase your internet bandwidth. Your download speed, streaming quality, and large file transfers depend on your internet plan, your Wi-Fi signal, and network congestion. A better resolver helps pages start loading sooner and can reduce “server not found” hiccups, but it will not turn a 50 Mbps connection into a 500 Mbps one.

Choosing a DNS Provider

By default, most routers use the DNS servers supplied automatically by your internet service provider (ISP). These are often perfectly adequate, and because they sit inside your ISP’s network, they can be very close to you. However, some ISP resolvers are slow, unreliable during peak hours, or redirect mistyped addresses to search or advertising pages. That is when a public DNS resolver becomes appealing.

Popular Public DNS Resolvers

• Cloudflare 1.1.1.1: Primary 1.1.1.1, secondary 1.0.0.1. Cloudflare markets this service around speed and privacy. It also offers filtered variants: 1.1.1.2 and 1.0.0.2 block known malware, while 1.1.1.3 and 1.0.0.3 block malware and adult content.
• Google Public DNS: Primary 8.8.8.8, secondary 8.8.4.4. A long-established, widely used resolver with a large global network. It does not filter content.
• Quad9: Primary 9.9.9.9, secondary 149.112.112.112. Run by a nonprofit foundation, Quad9 blocks domains associated with malware and phishing by default, which adds a layer of protection for every device on your network.
• OpenDNS FamilyShield: 208.67.222.123 and 208.67.220.123. A free option from Cisco designed to block adult content, useful for households with children.

Privacy, Filtering, and Family-Safe Options

Whoever runs your DNS resolver can see which domains your network looks up, so privacy policies matter. Read each provider’s published policy on logging and data retention before you commit. Some people prefer a nonprofit like Quad9; others are comfortable with a large company that publishes clear commitments. Your ISP, by comparison, can typically see your traffic metadata regardless of which DNS you use, so changing DNS is only one piece of privacy.

Filtering is another key difference. Malware-blocking resolvers can stop devices from reaching known malicious sites, which is especially valuable for smart home gadgets and other devices you cannot install security software on. Family-safe resolvers go further by blocking adult content. If you are already working on protecting your network, pair this with the steps in our guide on how to secure your home Wi-Fi network.

Why the Fastest Choice Depends on Your Location

No single resolver is fastest everywhere. Performance depends on how close the provider’s nearest server is to you and how well your ISP connects to that provider’s network. A resolver that tops speed charts in one city may be middling in another, and your ISP’s own resolver may beat them all. This is exactly why the next step, testing from your own network, matters.

Testing DNS Speed Before You Make Changes

Rather than relying on someone else’s rankings, measure lookup speed from your own home. Test at a couple of different times of day, because resolver performance can change during busy evening hours.

Using DNS Benchmarking Tools

Dedicated benchmarking utilities query a list of resolvers repeatedly and report average response times. Gibson Research Corporation’s DNS Benchmark, a long-standing free Windows tool, is a popular example. It compares your current resolver against many public ones and shows cached and uncached lookup times. Make sure you download any such tool from the developer’s official website.

Using Command-Line Lookups

You can also run quick manual tests with built-in tools.

On macOS or Linux, open Terminal and use dig, which reports a “Query time” in milliseconds:

• dig @1.1.1.1 example.com
• dig @8.8.8.8 example.com
• dig @9.9.9.9 example.com

On Windows, nslookup is built in. Running nslookup example.com 1.1.1.1 confirms whether a resolver answers correctly, though it does not display timing by default. For timing on Windows, PowerShell’s Measure-Command { Resolve-DnsName example.com -Server 1.1.1.1 -DnsOnly } gives a rough measurement.

Run each test several times and ignore the first result, which may include setup delays. Try a few less popular domain names too, since well-known sites are almost always already cached. If your ISP’s resolver consistently matches or beats the public options, switching may bring little benefit, and that is a useful result in itself.

Logging In to Your Router’s Admin Panel

To change DNS for the whole network, you need access to your router admin panel. That starts with finding the router’s address, known as the default gateway IP address.

Finding the Default Gateway IP Address

• Windows: Open Command Prompt, type ipconfig, and press Enter. Look for “Default Gateway” under your active Wi-Fi or Ethernet adapter.
• macOS: Open System Settings, select Network, choose your Wi-Fi connection, click Details, and open the TCP/IP tab. The address next to “Router” is your gateway.
• iPhone and iPad: Go to Settings, tap Wi-Fi, tap the information icon next to your network, and look for “Router.”
• Android: Menu locations vary by manufacturer, but you can usually tap your connected network in the Wi-Fi settings and look for a gateway or router entry, sometimes under advanced details.

Common gateway addresses include 192.168.0.1, 192.168.1.1, and 10.0.0.1, but always use the one your device reports.

Signing In Through the Web Interface or App

Type the gateway address into your browser’s address bar while connected to your home network. Your browser may show a security warning because many routers use a self-signed certificate; on your own home network, this is expected. Some routers, particularly mesh systems, are managed mainly or entirely through a manufacturer’s mobile app instead of a web page.

Admin credentials are often printed on a label on the router itself. If you changed them and forgot them, a factory reset is usually the only way back in, but it erases all your settings, including your Wi-Fi name and password, so treat that as a last resort. If you are still using the default admin password, change it now.

A Note on ISP-Supplied Gateways

Combined modem-router units provided by ISPs sometimes lock or hide DNS settings, or reset them during automatic updates. If you cannot find or save DNS options, that is likely the reason. The troubleshooting section below explains your alternatives.

Changing the DNS Server Settings on Your Router

Before changing anything, take a screenshot or write down the current settings. That makes it easy to revert if something goes wrong.

Where to Find the DNS Fields

Router manufacturers label and place DNS options differently, and menus can change with firmware updates. Look in sections with names like these:

• WAN, Internet, or Internet Connection: Often contains an option to obtain DNS automatically from your ISP or to enter DNS servers manually. Changing it here sets the resolver the router itself uses.
• LAN or DHCP Server: Some routers let you specify DNS servers that are handed directly to devices when they join the network.
• Advanced, Network, or Advanced Networking: Many brands tuck these settings under an advanced menu, so expand it if you do not see DNS on the main screens.

The difference matters slightly. With the WAN setting, devices usually send queries to the router, which forwards them to your chosen resolver. With the DHCP setting, devices query the public resolver directly. Either approach works for most homes; if your router offers both, the WAN setting is the more common starting point.

Entering Primary and Secondary DNS

1. Switch the DNS option from automatic to manual. It may be labeled “Use these DNS servers” or similar.
2. Enter your chosen primary DNS, for example 1.1.1.1.
3. Enter the secondary DNS from the same provider, for example 1.0.0.1. The secondary acts as a backup if the primary is unreachable.
4. If there are IPv6 DNS fields and your connection uses IPv6, enter the provider’s IPv6 addresses (listed below).
5. Save or apply the changes.

A common beginner mistake is mixing providers, such as a filtering resolver as primary and an unfiltered one as secondary. Devices may use either, so filtering becomes inconsistent. Keep both entries from the same service.

Handling IPv6 DNS Fields

If your ISP provides IPv6 and you only change the IPv4 DNS, devices may continue to use your ISP’s IPv6 resolver for some lookups. To avoid this, fill in the IPv6 fields where your router provides them:

• Cloudflare: 2606:4700:4700::1111 and 2606:4700:4700::1001
• Google Public DNS: 2001:4860:4860::8888 and 2001:4860:4860::8844
• Quad9: 2620:fe::fe and 2620:fe::9

Google maintains an official reference for its addresses and setup in the Google Public DNS documentation. Double-check addresses against each provider’s official site, since a single mistyped digit will break name resolution.

Save and Reboot

Some routers apply DNS changes immediately, while others need a restart. Rebooting is a safe way to make sure the new settings take effect. If you are unsure of the correct way to do this without losing settings, see our guide on how to restart a Wi-Fi router.

Applying and Verifying the New DNS Settings

Your devices will not necessarily switch to the new DNS server right away. Many keep their existing network configuration until their DHCP lease renews.

Renew Leases and Reconnect Devices

The simplest approach is to turn Wi-Fi off and back on, or forget and rejoin the network. On Windows, you can also run ipconfig /release followed by ipconfig /renew in Command Prompt. Restarting a device works too.

Flush DNS Caches

• Windows: Run ipconfig /flushdns in Command Prompt.
• macOS: In Terminal, run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder and enter your password.
• iPhone and Android: Toggling airplane mode on and off, or restarting the phone, clears the cached records.
• Chrome: Visit chrome://net-internals/#dns and select the option to clear the host cache. Clearing general browser data is a separate task, covered in our guide on how to clear Chrome cache.

Confirm the Active Resolver

Online resolver check tools show which DNS servers your device is actually reaching. DNS leak test sites list the resolvers responding to your queries. If you chose Cloudflare, its 1.1.1.1 help page confirms whether you are connected through its service. If results still show your ISP, the change has not reached that device yet, or something is overriding it.

Devices and Browsers That Bypass the Router

Two common situations cause devices to ignore the router’s DNS setting:

• Manually set DNS on the device: If someone previously configured DNS directly on a computer or phone, that setting wins. Android’s Private DNS feature, for example, sends lookups to a specified provider regardless of the router.
• DNS over HTTPS (DoH) in browsers: Browsers such as Chrome, Edge, and Firefox can send encrypted DNS queries to a provider configured in the browser’s settings, bypassing the router entirely. This improves privacy but means your router’s filtering or resolver choice may not apply inside that browser.

VPN apps and Apple’s iCloud Private Relay can also route DNS through their own servers. None of these are problems as such; just be aware of them when results do not match what you set on the router.

Troubleshooting Problems and Knowing the Limitations

Sites Won’t Load After the Change

If nothing loads, first check for typos in the DNS addresses, especially the IPv6 entries. Confirm you saved both primary and secondary values. If a filtering resolver is blocking a site you need, it may be a false positive; switch to the provider’s unfiltered option or report the site. Some work or school portals and ISP-specific services rely on internal DNS records and may only work with the ISP’s resolver.

Lookups Feel Slower

Occasionally a public resolver performs worse than your ISP’s, or certain content networks route you to a more distant server. Re-run your benchmark. If your original DNS was faster, switching back is a perfectly reasonable outcome.

Settings Revert After a Reboot

If DNS keeps resetting, make sure you pressed Save or Apply on every relevant page and check for a firmware update. ISP-managed gateways are sometimes reconfigured remotely, which can overwrite your changes.

ISP-Locked Routers and Per-Device DNS

When your router does not allow DNS changes, you have three main options: change DNS on individual devices in their network settings, put the ISP gateway into bridge mode (if supported) and use your own router, or add your own router behind the gateway. Per-device changes are also handy when you only want one computer or phone to use a different resolver.

Restoring the Default Automatic DNS

To undo everything, return to the same router screen, switch the DNS option back to automatic or “Get from ISP,” clear any manual entries, save, and reboot. Then reconnect devices and flush their caches as described above. This is where your earlier screenshot of the original settings pays off.

When Slow Browsing Isn’t a DNS Problem

If pages start loading quickly but crawl to finish, videos buffer, or speeds drop in certain rooms, the cause is usually Wi-Fi signal strength, interference, congestion, or your plan’s bandwidth. Run a speed test near the router and again from where you usually browse to compare. Our guide on why your Wi-Fi is slow walks through these causes and fixes in detail.

Frequently Asked Questions

Is it safe to change my router’s DNS settings?

Yes, as long as you use a reputable resolver and record your original settings. Changing DNS does not affect your Wi-Fi password or other devices’ data, and you can switch back to automatic DNS at any time. Avoid unknown DNS providers, since a malicious resolver could send you to fake websites.

Will a new DNS server improve gaming or streaming?

Usually not in a noticeable way. DNS only affects the initial lookup when connecting to a server. In-game ping and streaming quality depend on your connection’s latency, bandwidth, and stability, not on DNS.

Should I change DNS on the router or on each device?

Changing it on the router covers every device on your network, including smart TVs and other gadgets with no DNS settings of their own. Per-device changes are better when your router is locked, or when one device needs a different resolver from the rest of the household.

Conclusion

Switching your router to a faster, more reliable DNS server is one of the quickest network tweaks you can make, and it applies to every device at once. The best results come from a careful process: understand what DNS can and cannot improve, benchmark resolvers from your own connection, enter matching primary and secondary addresses (including IPv6 where relevant), and verify the change on your devices.

If pages load sooner and lookups stop timing out, the change has done its job. If browsing is still sluggish once a page starts loading, look at your Wi-Fi coverage and bandwidth instead. And if a public resolver turns out no faster than your ISP’s, you can restore automatic DNS in a minute, knowing you made the decision based on real results.