How to Block Ads and Trackers Using Simple Router Settings in 2026
.webp "Simple Router Settings to Block Trackers and Targeted Ads"){kind=tracking}
Simple Router Settings to Block Trackers and Targeted Ads
Take control of your home network with DNS filtering, smarter privacy settings and practical security checks — without replacing your router or paying for an expensive subscription.
Reading time: Approximately 10–12 minutes
Have you ever searched for a pair of trainers, a new phone or a holiday, only to find advertisements for the same thing following you around the internet? It can feel as though your devices are sharing more information than you intended.
Some of that behaviour comes from advertising networks, embedded trackers, cookies and other forms of data collection. Your internet connection also relies on Domain Name System (DNS) lookups to find the servers behind websites and online services.
Here is the useful part: by changing a few network settings, you can block requests to many known advertising and tracking domains for devices connected to your home Wi-Fi.
You do not necessarily need a new router, a complicated firewall or advanced networking skills. However, it is important to understand what DNS filtering can and cannot do before changing anything.
Open your router's administration page, find its Internet, WAN or DHCP/DNS settings, and configure a reputable ad-blocking DNS service if your router supports custom DNS. Alternatively, use a dedicated network-wide DNS filter such as AdGuard Home or Pi-hole.
Save the settings, reconnect your devices and test the results. DNS filtering can block many known advertising and tracking domains, but it cannot guarantee an ad-free internet or prevent every form of tracking.
Highlights: What You Need to Know
- Router-level DNS filtering can protect multiple devices without installing an ad-blocking app on each one.
- Ad-blocking DNS services work by refusing or redirecting lookups for domains on their filtering lists.
- Changing DNS settings does not automatically encrypt all your internet traffic.
- Apps using their own encrypted DNS, VPNs or mobile data may bypass your router's filtering.
- Some adverts are delivered from the same domains as legitimate content and cannot reliably be blocked through DNS alone.
- Custom DNS settings are different from your Wi-Fi password, router firewall and browser privacy controls.
- Always keep a record of your original DNS settings so you can restore them if something stops working.
1. Why Are Targeted Ads Following You?
Online advertising is not necessarily based on a single tracking technology. Advertisers and advertising platforms can use several signals to decide which adverts to show, measure whether someone clicked an advert, or estimate which products may interest a visitor.
Common tracking methods
- Third-party cookies: Small pieces of browser data that can support cross-site advertising and measurement, subject to browser restrictions and privacy settings.
- Tracking pixels and scripts: Embedded resources that can report page visits, campaign activity or other events.
- Advertising SDKs: Software libraries incorporated into mobile apps that can support advertising, analytics and measurement.
- IP addresses: Network addresses that may provide approximate location information or help services associate activity with a connection.
- Device and browser fingerprinting: Techniques that combine characteristics of a device or browser to help distinguish it from others.
- First-party data: Information a service collects directly through your account, searches, purchases, preferences or interactions.
These methods are not interchangeable. Blocking a tracking domain can prevent certain network requests, but it does not erase information already held by a company or stop a service from using data you deliberately provide while logged in.
If you search for a product on a shopping website and later see an advert for it, the explanation may involve your account activity, browser identifiers, an advertising network or a combination of signals. A router cannot reliably identify every reason that advert appeared.
2. How Router-Level DNS Ad Blocking Works
DNS stands for Domain Name System. It translates human-readable domain names, such as example.com, into the network addresses needed to reach internet services.
When a device requests a domain, a DNS resolver looks up the answer. An ad-blocking DNS service compares the request with its filtering rules. If the requested domain matches a blocked entry, the service may return a blocked response rather than the usual address.
A simplified example
Without DNS filtering
Your phone → DNS resolver → Advertising domain resolves → The device can attempt to load the advert or tracker.
With DNS filtering
Your phone → Filtering DNS resolver → Domain matches a block rule → The request is blocked or receives a filtered response.
The filtering decision occurs at the domain-lookup level. The filter generally does not inspect the complete contents of encrypted HTTPS web pages.
Why configure DNS on the router?
When the router distributes your chosen DNS resolver through DHCP, compatible devices can use that resolver automatically. This can make the setup useful for phones, laptops, tablets, smart TVs and other home devices.
There is an important qualification: router manufacturers handle DNS settings differently. Some let you configure the DNS servers advertised to devices, some expose separate WAN and LAN settings, and others restrict custom DNS entirely.
AdGuard Home's official setup documentation describes router-based configuration and notes that some routers do not allow a custom DNS server. See the AdGuard Home getting-started guide.
How DNS Filtering Works
A simplified view of how a filtering DNS service handles domain requests on your network.
The DNS lookup proceeds normally.
The resolver prevents normal resolution according to its filtering rules.
Important: This is a simplified illustration. DNS filtering blocks matching domains, not every advert or tracking method. Encrypted DNS settings, VPNs and app-specific network behaviour may bypass router-level filtering.
3. Choose the Right Blocking Method
| Method | Difficulty | Best for | Main limitation |
|---|---|---|---|
| Public filtering DNS | Easy | Beginners who want a quick setup | Limited control over filtering rules |
| Router custom DNS | Easy to moderate | Protecting compatible home devices | Depends on router support and device behaviour |
| AdGuard Home | Moderate | Custom blocklists, query logs and device-level rules | Requires a device or server to stay available |
| Pi-hole | Moderate | DIY network-wide DNS filtering | Needs maintenance and correct DNS configuration |
| Browser content blocker | Easy | Fine-grained webpage ad and cosmetic filtering | Usually needs separate configuration on each browser |
Our recommendation: Start with a reputable public filtering DNS service if your router supports it. Move to AdGuard Home or Pi-hole if you need custom lists, device-specific rules, detailed logs or more control.
4. Step-by-Step: Configure Your Router to Block Trackers
The exact menu names vary by manufacturer, model and firmware version. These instructions describe the general process rather than promising that every router will display identical options.
Set Up Router DNS Filtering in 5 Steps
The exact menu names vary by router brand, model and firmware.
Open Router Admin
Connect to your home network and open the router's official local administration page or app.
Find DNS Settings
Look under Internet, WAN, LAN or DHCP settings. The correct location depends on your router.
Choose a Filtering DNS
Use a reputable provider's current setup instructions. Check whether its service supports ad and tracker filtering.
Save and Reconnect
Save the changes, reconnect devices if necessary and renew their network settings when required.
Test Your Setup
Check the provider's diagnostics and test several websites and apps. Confirm that DNS filtering is actually active.
Step 1: Connect to your home Wi-Fi
Connect a phone or computer to the router you want to configure. For the initial setup, avoid making changes while connected to an unfamiliar public network.
Step 2: Open the router administration page
Open a browser and enter the router's gateway address. Common examples include:
192.168.0.1192.168.1.1192.168.1.254
These are examples, not universal addresses. If none works, check the gateway address in your device's network details or consult the router's label or manual.
Sign in using your router administrator credentials. Do not share these credentials with anyone.
Step 3: Back up your existing settings
Before changing anything, take screenshots of the current DNS configuration or export a router configuration backup if the manufacturer provides that option.
Step 4: Find the correct DNS menu
Look for a menu labelled one of the following:
- Internet or WAN settings
- LAN settings
- DHCP server
- DNS configuration
- Network settings
- Advanced settings
Read the labels carefully. The DNS resolver used by the router itself may be configured separately from the DNS addresses handed out to your devices.
Step 5: Choose a filtering DNS service
Select a reputable DNS service that explicitly offers advertising and tracker filtering. Use the provider's official setup instructions to obtain the correct IPv4 addresses, IPv6 addresses or encrypted DNS hostname for your chosen product.
For a beginner-friendly starting point, you can review AdGuard DNS and its filtering options.
Do not copy an address from an unverified forum post. DNS providers may offer different endpoints for standard DNS, malware protection, family filtering and other features.
Step 6: Enter the DNS settings
If your router provides primary and secondary DNS fields, enter the addresses specified by your chosen provider.
Use the provider's documented configuration for both fields. Do not assume that a second DNS address from a different provider will preserve your filtering policy.
Step 7: Save and reconnect
Save the changes and wait for the router to apply them. If necessary, reconnect your devices to Wi-Fi or renew their network leases.
Some routers restart automatically; others apply DNS changes without rebooting. Follow the instructions shown by your router rather than repeatedly switching it off and on.
Step 8: Verify that your devices are using the intended resolver
Check the DNS settings on a connected device. If you have configured DNS through DHCP, confirm that the device receives the expected resolver address.
Then test a few websites and apps you use regularly. If you use a DNS provider's diagnostic page, make sure it corresponds to the specific service you configured.
5. Which DNS Settings Should You Use?
There is no single DNS address that is best for every household. The right choice depends on the filtering features you need, the provider's privacy policy, availability, speed and your router's compatibility.
Option A: AdGuard DNS
AdGuard DNS offers filtering options intended to block advertising, trackers and, depending on the selected configuration, other unwanted domains. Choose an endpoint from its official documentation that matches your requirements.
Read the official AdGuard DNS documentation.
Option B: AdGuard Home
AdGuard Home is a self-hosted network-wide DNS filtering solution. It can provide blocklists, query statistics, client-specific configuration and support for encrypted DNS connections.
It is particularly useful when you want to control which devices use which rules. However, you must install it correctly and keep the host device available.
Option C: Pi-hole
Pi-hole is another popular self-hosted DNS filtering project. It can block many advertising and tracking domains for devices configured to use it.
It requires a suitable host, configuration and occasional maintenance. Depending on your router, you may need to advertise the Pi-hole address through DHCP or configure DNS forwarding.
Explore the official Pi-hole documentation.
Compare the practical trade-offs
| Consideration | Public filtering DNS | Self-hosted DNS filter |
|---|---|---|
| Initial setup | Usually simpler | Requires installation and configuration |
| Custom blocklists | Depends on provider and plan | Generally more flexible |
| Per-device policies | Depends on service features | Often available |
| Local query visibility | Depends on provider's dashboard | Can provide local logs and statistics |
| Maintenance | Mostly managed by provider | You maintain the host and software |
| Single point of failure | Provider availability matters | Your local server must remain available |
Privacy tip: A filtering DNS service is not automatically a no-logging service. Read its privacy policy, understand what query information it retains, and check whether its encrypted DNS endpoint is supported by your device or router.
6. Advanced Option: Pi-hole or AdGuard Home
If your router does not offer useful DNS controls, a dedicated DNS filtering server may be a better solution.
You can run suitable software on a compatible low-power computer, single-board computer or supported home server. The device acts as the DNS resolver for your household.
How the network is arranged
Device → Home router → Local DNS filter → Upstream DNS provider
Your devices send DNS requests to the local filtering server. The server checks its rules and forwards permitted lookups to its configured upstream resolver.
Basic deployment plan
- Choose a supported device and install the software using its official documentation.
- Assign the DNS server a stable local IP address, preferably through a DHCP reservation.
- Configure an upstream DNS resolver and select appropriate blocklists.
- Set the router's DHCP configuration to advertise the filtering server to compatible clients.
- Test several devices and confirm that DNS queries appear in the server's logs.
- Keep the software updated and secure its administration interface.
Do not expose a DNS server's administration panel or an unrestricted DNS service directly to the public internet. An improperly configured resolver can create security, privacy and abuse risks.
For encrypted connections between clients and a filtering resolver, see the AdGuard Home encryption documentation.
7. What About Android Phones?
Android offers another option called Private DNS. On supported Android versions, this normally configures DNS-over-TLS using a provider's hostname.
Depending on the device and Android version, the menu is usually found under a path similar to:
Settings → Network & Internet or Connections → Private DNS
Choose the option to specify a Private DNS provider hostname and enter the exact hostname supplied by your chosen provider. The wording and menu location may differ between Android manufacturers.
Private DNS on your phone is not the same as configuring DNS on your router. A phone configured to use its own Private DNS provider may use that service instead of the resolver distributed by the router.
Also remember that Android's Private DNS setting is not a full VPN. It protects DNS traffic to the configured resolver but does not, by itself, encrypt every connection or conceal your public IP address from websites.
8. How to Test Whether DNS Blocking Works
Changing a setting is not proof that the intended protection is active. A short verification process helps identify configuration mistakes.
Use this checklist
- Confirm that your router has saved the new DNS configuration.
- Check whether your device is using the intended resolver.
- Review the filtering provider's diagnostic tools or local query logs.
- Test a known blocked domain using the provider's recommended test method.
- Open everyday websites and apps to check for broken features.
- Repeat the test on a second device, such as a tablet or laptop.
- Test separately on mobile data to understand which protections depend on your home network.
Some blocklists update frequently, and DNS caches can temporarily preserve previous results. Restarting an app, reconnecting to Wi-Fi or clearing a relevant DNS cache may help during testing.
Do not rely solely on whether an advert appears on one webpage. Advert delivery can vary by page, location, account, browser and advertising system.
More Privacy
Reduce DNS requests to domains on your filtering lists.
Fewer Ad Requests
Block some ad-serving domains before their content loads.
Less Network Clutter
Some pages may make fewer requests and load more efficiently.
Added Protection
Suitable blocklists may block known malicious domains too.
9. What Router DNS Filtering Cannot Block
DNS filtering is useful, but it has important technical limits. Understanding them prevents false confidence.
1. Adverts served from the same domain as content
Some platforms deliver adverts and ordinary content through the same domains or infrastructure. Blocking the entire domain could break the service, so a DNS filter may not be able to remove the advert without also affecting legitimate content.
2. First-party tracking
A website may collect analytics or behavioural information through its own domain. DNS filtering cannot reliably distinguish every tracking request from the legitimate functions hosted on that domain.
3. Browser fingerprinting
Fingerprinting can use browser and device characteristics. It does not always require a separate tracking domain that a DNS blocklist can identify.
4. Apps with their own DNS or VPN configuration
Some applications use encrypted DNS, a VPN or another network path that bypasses the DNS resolver configured on the router. The extent of bypass depends on the device, application and network configuration.
5. Mobile data and other Wi-Fi networks
Your home router's DNS settings do not automatically protect your device when it switches to mobile data or joins a different network. Device-level configuration can help provide more consistent protection.
6. Existing data and personalised recommendations
Blocking a tracker today does not delete your existing account history, advertising profile or previously collected information. Services may continue to personalise adverts using data they already have or information you provide directly.
For additional browser-level protections, review the current privacy controls in your browser. Google's documentation explains technologies such as storage partitioning that can reduce certain forms of cross-site tracking, although the protection available depends on the browser and its implementation.
Read about Chrome storage partitioning.
DNS Filtering: What to Expect
Router-level DNS filtering is useful, but it is not a complete replacement for browser protection or privacy-conscious app settings.
✓ What It Can Do
- Block requests to listed advertising domains.
- Reduce connections to known tracking domains.
- Apply network-level rules to compatible devices.
- Filter certain known malicious domains when supported by the chosen lists.
! What It Cannot Guarantee
- Blocking every advert embedded in a website or app.
- Stopping first-party tracking or all fingerprinting.
- Filtering traffic that bypasses your configured DNS resolver.
- Replacing HTTPS, software updates or browser security controls.
Best approach: Combine a reputable filtering DNS service with browser tracking protection, updated devices, secure Wi-Fi settings and sensible app permissions.
10. Troubleshooting Common Problems
Problem: Websites stop loading
Likely cause: The DNS service is unavailable, an address was entered incorrectly, or a necessary domain has been blocked.
Fix: Check the DNS addresses and provider status. If necessary, temporarily restore the original DNS configuration to confirm whether the new filter is responsible.
Problem: Some adverts still appear
Likely cause: The advert is delivered from a domain that is not blocked, uses a shared content domain or is loaded through a path that bypasses your filter.
Fix: Check the DNS logs, update your blocklists where appropriate and consider a browser content blocker for compatible browsers.
Problem: One phone ignores the router settings
Likely cause: The phone uses manually configured DNS, Android Private DNS, a VPN or another encrypted DNS feature.
Fix: Review the phone's DNS and VPN settings and decide whether you want it to use the central network filter or a separate filtering service.
Problem: The filtering server stops working
Likely cause: The host has powered off, lost its network connection or stopped running the DNS service.
Fix: Restore power and connectivity, inspect the DNS service and check the server's logs. Plan a recovery option before making a local DNS filter the only resolver for your household.
Problem: A streaming service or app breaks
Likely cause: A required domain has been included in a blocklist.
Fix: Identify the blocked domain through the filtering logs and use the service's documented allowlisting controls where appropriate. Avoid disabling all filtering as the first response.
11. Build a Stronger Privacy Setup
Router DNS filtering works best as one part of a broader privacy strategy. Combine it with sensible browser settings, secure networking and careful account management.
Recommended privacy checklist
- Enable DNS filtering: Block known advertising, tracking and malicious domains through a reputable service.
- Update router firmware: Install official security updates when available.
- Change default administrator credentials: Use a unique, strong password for router management.
- Secure Wi-Fi: Use WPA2-AES or WPA3 where supported and choose a strong Wi-Fi password.
- Review browser privacy controls: Restrict unwanted third-party cookies and consider a reputable content blocker.
- Limit app permissions: Review access to location, contacts, microphone and other sensitive features.
- Use HTTPS: Prefer secure website connections and pay attention to browser security warnings.
- Review account settings: Check advertising personalisation and activity controls for the services you use.
- Separate smart devices: If your router supports a guest network or IoT network, consider isolating devices that do not need access to your main devices.
- Audit DNS regularly: Review blocklists and logs, and remove rules that cause unnecessary breakage.
DNS encryption deserves special attention. Traditional DNS requests may be visible to parts of the network path. DNS-over-HTTPS (DoH) and DNS-over-TLS (DoT) can encrypt the connection between a client and a compatible resolver, but they do not hide all browsing activity from every party.
For example, DNS encryption does not automatically hide the IP address you connect to, stop cookies, prevent all browser fingerprinting or make a website unable to identify you through an account you sign into.
12. Expert Analysis: Which Approach Makes the Most Sense?
The best configuration depends on your technical confidence and how much control you want.
For beginners
Start with a reputable public DNS filtering service and configure it through your router if supported. This offers a relatively simple way to reduce requests to known advertising and tracking domains without maintaining another device.
For privacy-conscious households
Consider AdGuard Home or Pi-hole if you want local logs, custom blocklists, per-device rules and more visibility into DNS activity. Account for installation, updates and the need to keep the resolver available.
For people who want cleaner webpages
Combine network-level DNS filtering with a reputable browser content blocker. Browser filtering can apply rules to webpage elements and requests that DNS filtering cannot distinguish reliably.
For stronger privacy
Combine DNS filtering with browser privacy settings, secure Wi-Fi, software updates and careful account controls. A VPN may be useful for specific network privacy needs, but it is not a universal tracker blocker and changes which provider handles your traffic.
The privacy trade-off many guides overlook
When you switch DNS providers, you change who receives your DNS queries. Those queries can reveal information about the domains your devices look up, even though they do not necessarily reveal every page or action you perform on a website.
Therefore, choosing an ad-blocking resolver is not just a technical decision. It is also a decision about which organisation you trust to process your DNS traffic. Review its privacy policy, logging practices, security model and reliability.
Similarly, a locally hosted DNS filter gives you more control, but it does not eliminate trust decisions. Your upstream resolver still receives queries that your local filter forwards, and the server itself needs to be secured.
Our verdict: For most households, router-level filtering DNS is a sensible first step because it is simple and can cover several devices. For greater control, a self-hosted filter is worth considering. For the strongest practical result, combine network filtering with browser-level protection and realistic expectations about what each layer can achieve.
13. Final Thought: Take Control of Your Home Network
You do not have to accept every advert and tracking request as an unavoidable part of being online. A carefully configured router and a trustworthy DNS filtering service can reduce exposure to many known advertising, tracking and malicious domains across compatible devices.
The process can be straightforward: back up your settings, select a suitable filtering resolver, configure your router, reconnect your devices and test the result. If you need more control, consider a dedicated DNS filter such as Pi-hole or AdGuard Home.
Just remember that no single DNS setting can guarantee complete anonymity or eliminate every targeted advert. Combine network-level filtering with browser protections, secure devices and thoughtful privacy choices.
That is the real goal: not a magical one-click privacy fix, but a home network that gives you more control over what your devices contact and which services you trust.
14. Frequently Asked Questions (FAQs)
1. Can I block targeted ads by changing my router settings?
Yes, to a degree. Configuring your router to use a DNS service with advertising and tracker filtering can block requests to many known advertising domains. It cannot block every advert or prevent all forms of personalisation and tracking.
2. What is the easiest way to block ads across my home Wi-Fi?
The easiest approach is usually to configure a reputable ad-blocking DNS service through your router, provided it supports custom DNS settings. Devices that use the configured resolver can then benefit without individual app installation.
3. Do I need to buy a new router for DNS ad blocking?
Not necessarily. Many routers support custom DNS settings. If yours does not, you may be able to use a compatible local DNS filtering server or configure filtering separately on supported devices.
4. Is DNS ad blocking completely free?
Some public filtering DNS services offer free options. Self-hosted software such as Pi-hole can also be used without a paid software subscription, although the hardware, electricity and maintenance may have costs. Check each provider's current terms.
5. Does DNS ad blocking make my internet faster?
It can reduce unnecessary requests and sometimes improve perceived loading performance. However, the result depends on the website, resolver response time, caching and the content being loaded. It does not guarantee faster internet speeds.
6. Can DNS filtering block YouTube adverts?
Not reliably. Some advertising is delivered through the same domains or infrastructure used for legitimate video content. DNS filtering alone generally cannot distinguish every advert from the video stream.
7. Does router-level DNS blocking protect every device?
It can protect compatible devices that use the router's filtering resolver. Devices using mobile data, a VPN, manually configured DNS or their own encrypted DNS may bypass that resolver.
8. Is AdGuard DNS better than Pi-hole?
Neither is universally better. AdGuard DNS is convenient if you want a managed service, while Pi-hole offers local control and custom filtering. Your choice depends on maintenance preferences, desired features and privacy requirements.
9. Can my internet service provider see my browsing activity after I enable encrypted DNS?
Encrypted DNS can prevent your ISP from reading the DNS queries carried within that encrypted connection. It does not automatically conceal every destination IP address or all other network metadata, and the resolver you choose can still process your DNS queries.
10. Will DNS ad blocking stop websites from tracking me completely?
No. It can block many known tracking domains, but it cannot reliably prevent first-party tracking, all cookies, fingerprinting, account-based personalisation or information already collected by websites and apps.
11. Is it safe to change my router DNS settings?
It is generally manageable if you use a reputable provider and follow your router's instructions. Record the original settings first, enter the correct addresses and restore the previous configuration if internet access or essential services stop working.
12. Should I use a VPN as well as DNS filtering?
That depends on your privacy goals. A VPN can change the network path and protect traffic between your device and the VPN endpoint, depending on its configuration. It does not automatically block all trackers or replace browser-level privacy controls.
Editorial Note: Results may vary depending on your router and DNS settings. These methods can reduce ads and trackers but may not block all of them. Always verify settings and keep your router firmware updated.
