What DNS-level ad blocking actually is
Before an app or browser connects anywhere, it asks a DNS resolver to turn a domain name (such as ads.example.com) into an IP address. A filtering resolver keeps a list of known ad and tracker domains. When your Mac asks for one of those, it gets back no usable address (often 0.0.0.0 or "does not exist"). The connection never happens, so the ad or tracker cannot load.
This works at the domain level, before any connection is made. The resolver does not read page content or inject anything into your browser. That is why one DNS setting covers Safari, Chrome, Firefox, Mail and most other apps at once, with no extension. The trade-off is that it can only block or allow a whole domain, with no knowledge of what is on it.
Pros and cons vs. extensions and proxies
Where DNS blocking wins:
- Broad coverage. One change covers every browser and app that uses the system's DNS, including apps with no ad blocking of their own.
- Nothing to install. Public resolvers need only a settings change. No system extension, no proxy.
- Low overhead. It only answers DNS queries; it does not sit in your traffic path decrypting anything.
Where it falls short:
- First-party ads survive. YouTube pre-rolls come from the same domains as the videos, so a DNS blocker cannot drop them without breaking the site. Extensions that filter the page can.
- All or nothing per domain. If one domain serves both a tracker and something you need, you cannot split it.
- Some traffic bypasses it. Browsers with their own encrypted DNS (Brave uses it by default, Chrome and Firefox can be set to it), iCloud Private Relay in Safari and most VPNs send lookups elsewhere, so your resolver never sees them.
- Maintenance. Trackers rotate domains, so the lists have to be kept fresh. Public resolvers do that for you; self-hosted ones need updates.
- It cannot tell apps apart. DNS sees the domain but not which app asked. You cannot tell whether a tracker request came from a game, a menu bar utility or your browser.
The best ad-blocking DNS options in 2026
These are public filtering resolvers you point your Mac at. They are free to start with and most need no account.
- NextDNS (free tier, paid plans). The most customisable: you pick blocklists, allow or deny domains and see logs. The free plan covers 300,000 queries a month; after that NextDNS keeps answering queries but stops filtering until the next month. Paid plans lift the limit. Your addresses are personal to your configuration, so set it up with NextDNS's app or configuration profile, or link your IP address in its dashboard.
- AdGuard DNS (free public servers, paid plans). The default servers 94.140.14.14 and 94.140.15.15 block ads and trackers out of the box. A family variant (94.140.14.15 / 94.140.15.16) also filters adult content.
- Cloudflare 1.1.1.1 for Families (free). Use 1.1.1.2 and 1.0.0.2 to block malware, or 1.1.1.3 and 1.0.0.3 for malware plus adult content. It targets security, not ads.
- Quad9 (free). 9.9.9.9, run by a Swiss non-profit foundation. It blocks malware, phishing and botnet domains rather than ads, and states that it does not log your IP address.
For ad and tracker blocking, start with AdGuard DNS (simplest) or NextDNS (most control).
How to set custom DNS on macOS (plus self-hosted and app-level)
Change your DNS in System Settings (about a minute):
- Open System Settings > Network.
- Pick your active connection (Wi-Fi or Ethernet), then click Details....
- Go to the DNS tab.
- Under DNS Servers, click + and add the addresses you chose, for example 94.140.14.14 and 94.140.15.15 for AdGuard DNS.
- Remove old entries you no longer want and click OK. Reconnect to the network if the change does not take effect.
The setting belongs to that connection, so repeat it for other networks you use. On hotel or airport Wi-Fi with a login page, switch DNS back to automatic until you are signed in, or the login page may not appear.
Self-hosted (whole network):
- Pi-hole and AdGuard Home are free and filter every device on your network, smart TVs included. Both run on a Raspberry Pi or any always-on computer, and setup takes an evening rather than a minute. The catch is the hardware and the upkeep.
App-level on the Mac:
- AdGuard for Mac is a paid app that filters traffic through a local proxy, so it can also remove elements inside pages, not only whole domains.
- NetMute (this site's app) takes the per-app angle. It shows which domains each app on your Mac contacts, and its Tracker Shield blocks known tracker domains in your apps. That covers DNS's blind spot: you see which app asked, not only which domain. Free to download, with Pro as a one-time purchase. It works next to a DNS resolver or on its own.
The bottom line
For broad coverage with almost no effort, point your Mac's DNS at a filtering resolver. AdGuard DNS (94.140.14.14 / 94.140.15.15) is the simplest ad blocker, NextDNS the pick if you want control and logs. Cloudflare for Families and Quad9 are security layers rather than ad blockers. For every device in the house, self-host Pi-hole or AdGuard Home.
Keep the limits in mind: DNS blocking works per domain, does not know which app made a request, misses browsers with their own encrypted DNS and cannot remove first-party ads. If you want to see which app is phoning home and stop its trackers, NetMute fits next to any DNS setup. Many people run both: a filtering resolver for the network, NetMute for what each app on the Mac does.