What the DNS setting on your router does, and when to change it

Short answer: DNS (domain name system) is what turns a name like example.com into the IP address your device actually connects to. Your router’s DNS setting controls which DNS service handles that lookup for every device on your network, and the usual reasons to change it from your ISP’s default are speed, privacy, or built-in filtering.

What DNS actually does

Every time a device loads a site, it first asks a DNS server “what’s the address for this name?” The DNS server answers with an IP address, and only then does the device connect to that address. This happens before almost everything else on the page, which is why a slow DNS server can make browsing feel sluggish even on a fast connection — the delay is in the lookup, not the download.

Your router hands out DNS settings to your devices automatically as part of the same process that assigns them a local IP address. Unless you’ve changed anything, that DNS setting usually just forwards to your ISP’s own DNS servers.

Where the DNS setting lives on your router

Look for it under the WAN or internet connection settings, sometimes under a general “DNS” tab, sometimes grouped with DHCP settings. Most routers let you enter a primary and a secondary DNS server by IP address. Leaving both fields blank, or set to “automatic,” means the router uses whatever DNS your ISP assigned it.

If you can’t find your router’s admin page at all, start with finding your router’s IP address; the DNS setting is nearly always a few clicks past the login screen described in logging into your router.

The real reasons to change it

Speed. Some public DNS resolvers answer faster than a given ISP’s servers, particularly for sites outside your ISP’s own network. The gain, if any, is usually small and depends entirely on your ISP and location, so it’s worth testing rather than assuming.

Privacy. Every DNS query is a record of a domain you looked up. Switching away from your ISP’s resolver moves that record to whichever provider you pick instead — it doesn’t delete the record, it relocates it. Read a provider’s actual privacy policy before trusting a privacy claim.

Filtering. Some DNS providers block known malware or ad-serving domains at the lookup stage, before your device ever connects to them. Family-filtering DNS services work the same way, refusing to resolve categories of sites. Because this runs at the router, it applies to every device on the network without installing anything on each one — unlike a VPN set up on the router, which changes your traffic’s path instead of just the lookup.

What changing it doesn’t do

DNS only affects name lookups. It has no effect on your download or upload speed once a connection is made, and it doesn’t hide your traffic from your ISP the way a VPN does — your ISP still sees the IP addresses you connect to, just not necessarily the domain names, depending on whether your chosen DNS supports encrypted queries.

It also doesn’t change your NAT behavior or anything about how devices on your own network find each other. If a site resolves to the wrong address, or won’t resolve at all, DNS is the first thing to check, but a working DNS setting isn’t a substitute for correct routing elsewhere on the network.

If something breaks after changing it

Most DNS problems after a change come down to a typo in the IP address field, or a DNS provider that’s temporarily down. If sites stop loading, set the fields back to automatic and confirm the connection works again before trying a different provider. If devices still can’t resolve anything at all, check that your router’s DHCP is still handing out the setting correctly — how many devices can connect to your WiFi covers how DHCP and addressing interact more broadly.

If you’re trying to confirm which devices picked up a DNS or address change, run a scan from who’s connected to my WiFi, or look up an unfamiliar device’s manufacturer with the MAC vendor lookup tool.