Understanding DNS settings in home network equipment helps you solve a surprising number of everyday connection problems. DNS, short for Domain Name System, is the service that turns website names such as example.com into the numeric IP addresses computers use to find each other.
Most households never touch these settings because the router and internet provider configure them automatically. Knowing where they live and how they work, however, lets you diagnose sites that will not load, choose a different resolver, and turn on encrypted lookups for more privacy.
How DNS Turns Names Into Addresses Behind the Scenes
Every device on the internet is reached through an IP address, a string of numbers such as an IPv4 address or a longer IPv6 address. People remember names far more easily than numbers, so DNS acts as a directory that matches each name to the right address.
When you type a website name, your device sends a question, called a query, to a DNS resolver. The resolver is a server that finds the answer, either from its own memory or by asking other DNS servers in a chain that ends with the server responsible for that domain.
The answer comes back as an IP address, and your browser then connects to that address. Traditional DNS uses port 53, a numbered channel that network software listens on. This entire exchange usually finishes before you notice, and the result is cached so repeat visits are quicker.
Caching means a stored copy of a recent answer. Your browser, your operating system and your router may all keep caches. Caches speed things up, but an outdated cached answer can occasionally send you to the wrong place, which is why clearing them is a common troubleshooting step.
Where DNS Settings Live: Router Versus Device
DNS can be configured in two main places in a home network, and understanding which one is in charge prevents a lot of confusion when you make changes.
DNS Settings on the Router
Your router typically receives DNS server addresses from your internet service provider when it connects. Through DHCP, the service that hands out local IP addresses, the router then passes DNS information to every device that joins your network, often listing itself as the DNS server and forwarding queries upstream.
Changing DNS on the router therefore affects every device that uses automatic settings, which makes it the simplest place for a household-wide change.
DNS Settings on Individual Devices
Computers, phones and game consoles can also have DNS servers entered manually in their network settings. A manual entry on a device overrides whatever the router provides for that device only.
This is useful for testing a resolver on one computer before changing the whole household, or for a device that needs different behavior.
Browsers and Apps With Their Own DNS
Some browsers and apps include their own encrypted DNS feature, which can bypass both the router and the operating system settings. If a change on the router does not seem to take effect in one browser, check that browser’s privacy or security settings for a secure DNS option.
The same applies to some streaming boxes and smart devices that are set to use a fixed resolver by their manufacturer. In those cases, the router setting simply does not reach them, and only the device or app settings can change the behavior.
What Your Internet Provider’s Resolver Does
By default, most homes use the resolver run by their internet service provider. It is assigned automatically, requires no setup and is generally located on the provider’s own network. For many households it works well, and there is no requirement to change it.
Some people still choose a different resolver. Reasons include wanting a resolver that supports encrypted DNS, one that offers optional filtering of known malicious or adult sites, or one that has proven more reliable for their connection. Public resolvers are services open to anyone, and many are free to use.
Every resolver can see the names your household looks up, because that is how it answers queries. Switching resolvers changes who receives that information rather than eliminating it. Read the privacy policy of any resolver you consider, and compare what it logs and how long it keeps those records.
Keep your expectations realistic about speed. A different resolver can make the first lookup of a site slightly faster or slower, but it does not change your internet plan’s bandwidth. Downloads and video quality depend on your connection, not on which resolver answers name lookups.
Changing the DNS Resolver on Your Router
Changing the resolver on the router applies the new setting to every device that receives its configuration automatically. Router menus differ by brand and firmware, so use the steps below as a general guide and check your router’s manual or app for the exact labels.
- Sign in to the router’s web interface or app using the administrator account, not the Wi-Fi password.
- Look for a section labeled Internet, WAN, DHCP Server or DNS, depending on the model.
- Switch from automatic DNS to manual, and enter the primary and secondary addresses published by the resolver you chose.
- Save the settings and restart the router if it asks you to.
- Reconnect a device or restart it so it picks up the new settings, then confirm websites load normally.
Always enter two resolver addresses when the router allows it. The secondary address acts as a backup if the primary one does not respond. Write down the original settings before you change them, so you can switch back quickly if anything behaves unexpectedly.
Some ISP gateways do not allow DNS changes. In that case, change DNS on individual devices instead, starting with the computers and phones your household uses most.
Encrypted DNS: DNS Over HTTPS and DNS Over TLS
Traditional DNS queries travel without encryption, so anyone positioned on the network path can see which names you look up and, in some cases, tamper with the answers. Encrypted DNS protects the query between your device and the resolver.
Two common methods exist. DNS over HTTPS, often shortened to DoH, sends queries inside the same kind of encrypted connection used by secure websites. DNS over TLS, or DoT, uses a dedicated encrypted channel for DNS traffic, normally on port 853. Both aim to keep lookups private and harder to alter in transit.
Support varies by equipment. Some routers offer encrypted DNS settings for the whole network, while many operating systems and browsers support it on the device itself. Look for options labeled private DNS, secure DNS or encrypted DNS, and select a resolver that supports the method you choose.
Encrypted DNS protects only the lookup. It does not fully hide your browsing from your internet provider and does not replace a VPN. It also may bypass DNS-based filtering set up on the router, which matters if your household relies on that filtering for younger users.
Common DNS Problems and Their Warning Signs
DNS problems often look like a broken internet connection, which makes them easy to misdiagnose. The difference is that the connection itself works, but names fail to turn into addresses. Recognizing the warning signs saves time.
- Browsers show messages such as server not found or DNS address could not be found while other apps still work.
- A website loads on mobile data but not on your home Wi-Fi.
- Pages take a long pause before loading, then display normally once they start.
- One device fails to resolve sites while others on the same network work fine.
- A site you visit often suddenly points to an unexpected page or certificate warning.
A certificate warning deserves extra caution. Do not click past it on banking, email or shopping sites. It can indicate an outdated cache, a misconfigured resolver or, more rarely, tampering, so investigate before entering any personal information.
If every device fails at once, start with the router. If only one device fails, start with that device. Narrowing the scope first tells you which settings to examine and which to leave alone.
Troubleshooting DNS Step by Step
Begin with the simplest fix: restart the device, then restart the router and modem if the problem affects several devices. Restarting clears temporary caches and forces devices to request fresh DNS settings through DHCP, which resolves many short-lived issues without further work.
Next, clear the operating system’s DNS cache. On Windows, open Command Prompt and run ipconfig /flushdns. On a Mac, the command differs by macOS version, so check Apple’s support documentation. Clearing the browser cache or restarting the browser helps when only one browser shows the problem.
Use the nslookup command, available on Windows, macOS and Linux, to test resolution directly. Typing nslookup followed by a website name shows which resolver answered and what address it returned. If it fails, try again specifying a different resolver to see whether the original resolver is at fault.
If manual DNS settings on a device are wrong or outdated, switch that device back to automatic. When problems continue across every device and every resolver, the issue may be the internet connection itself, so contact your ISP and mention the tests you have already run.
Keeping DNS Settings Reliable for Your Household
Once DNS is working well, a little upkeep keeps it that way. Record which resolver you use, where you configured it and whether encrypted DNS is turned on. Notes like these make future troubleshooting much faster, especially when someone else in the household needs to help.
Keep router firmware up to date, because updates often fix DNS-related bugs and security weaknesses. Change the default administrator password on the router as well. Malware that changes router DNS settings to point at a malicious resolver is a known threat, and a strong password makes that harder.
Check the DNS fields on the router occasionally. If you see addresses you did not enter and do not recognize, restore your chosen settings, change the administrator password and update the firmware. Consider a factory reset if the unknown settings return after you correct them.
As your network grows with more smart devices, guest users and home offices, revisit whether a single household-wide setting still fits. If the router allows separate DNS settings per network, some families keep a filtered resolver on one network and a standard one on another, so each group gets the behavior it needs.