AdGuardHome: Block Ads & Trackers Across Your Network

Learn how to quickly set up AdGuardHome to block ads and trackers network-wide—safer, faster browsing for every device on your network.

2026-03-30 GIGATAP Team #privacy
#privacy#adblock#adguard#dns#dns-over-https#dns-over-quic

AdGuard Home is useful when DNS filtering becomes a network-level privacy and safety control rather than a browser add-on. It can reduce ads, trackers, and known bad domains across devices, but it needs careful upstream DNS choices, allowlists, update discipline, and a fallback plan for broken services.

What is AdGuardHome#

AdGuardHome is a free, open-source DNS server that blocks ads and trackers across your entire home or office network. Unlike browser extensions or device-specific apps, AdGuardHome works at the network level—shielding every connected device, including smartphones, laptops, tablets, smart TVs, and IoT devices, from intrusive ads, malware, and tracking.

AdGuardHome is written in Go and is widely respected for its simplicity, strong privacy stance, no cloud dependence, and advanced DNS features (like DNS-over-HTTPS, DNS-over-TLS, DNSCrypt, and DNS-over-QUIC). It’s maintained by AdGuard, the same team behind the popular public AdGuard DNS service. AdGuardHome hands you full local control and customizability, making it a top choice for privacy enthusiasts.

Security Warning (March 2026):
A critical vulnerability was recently discovered that could let unauthorized users bypass authentication and gain full control. Update to version 0.107.73 or later immediately.

Installation#

AdGuardHome is cross-platform: installable on Linux, macOS, FreeBSD, OpenBSD, and Windows, as well as ARM-based single-board computers like Raspberry Pi. The quickest way to get started (Linux/Mac/BSD) is via their auto-install script.

1. Install via Shell Script (Linux/Mac/BSD)

Run:

curl -s -S -L https://static.adguard.com/adguardhome/release/AdGuardHome_linux_amd64.tar.gz | tar -xz
cd AdGuardHome
sudo ./AdGuardHome -s install

This downloads, extracts, and sets up AdGuardHome as a background service.

2. Windows Installation

Tip: If you’re running on a Raspberry Pi (ARM), download the ARM tarball before executing the install steps.

3. Docker (Optional)

For containerized deployments:

docker run --name adguardhome -v /opt/adguardhome/work:/opt/adguardhome/work -v /opt/adguardhome/conf:/opt/adguardhome/conf -p 192.168.1.10:53:53/tcp -p 192.168.1.10:53:53/udp -p 127.0.0.1:3000:3000/tcp -d adguard/adguardhome

The setup web interface will appear at http://localhost:3000 (or use SSH port forwarding). Bind ports only to trusted LAN/private interfaces and keep DNS/admin ports blocked from the public Internet.

Basic Configuration#

Once installed, open your browser to http://localhost:3000 (replace localhost with your server IP if remote). The initial wizard includes:

1. Admin Credentials#

Set a strong username and password—never skip this! Do not reuse simple credentials.

2. Network Interfaces#

Choose only trusted LAN/private interfaces. Do not select all interfaces on a public VPS/cloud host.

3. DNS Settings#

By default, AdGuardHome listens on port 53 (DNS). You can also enable encrypted DNS protocols (like DNS-over-HTTPS or DNS-over-TLS):

dns:
  bind_hosts:
    - 192.168.1.10
  port: 53
  protection_enabled: true
  upstream_dns:
    - "https://dns.cloudflare.com/dns-query"

Edit your DNS settings in AdGuardHome.yaml, or via the web dashboard later (Settings > DNS Settings > Upstream Servers).

4. Blocklists#

AdGuardHome comes with recommended blocklists, but you can add custom blocklists for additional ad, tracker, and malware domains.

Common Use Cases#

1. Whole-Network Ad & Tracker Blocking#

  • Configure your router’s DHCP server to hand out your AdGuardHome server’s IP as the primary DNS server.
  • Or, set individual devices’ DNS settings to your AdGuardHome IP.

Example router DNS config:

Primary DNS: 192.168.1.10   # (Your AdGuardHome server IP)
Secondary DNS: 1.1.1.1      # (Optional, as a fallback)

All traffic is now filtered through AdGuardHome!

2. Encrypted DNS For Privacy#

Enable DNS-over-HTTPS for outgoing queries (Settings > DNS settings > Upstream Servers):

https://dns.quad9.net/dns-query

This encrypts your DNS traffic so ISPs can’t view browsing requests.

3. Parental Filtering#

  • Add additional blocklists (e.g., for adult sites).
  • Enable SafeSearch enforcement under Settings > Parental control.

4. Detailed Stats & Query Logs#

AdGuardHome provides a dashboard with real-time stats:

  • Top-blocked domains
  • Per-device requests
  • Allowed, blocked, or filtered queries

Tips and Gotchas#

  • Update Immediately on Vulnerabilities
    Always upgrade promptly—security hotfixes may address critical risks. For this release, run:

    sudo ./AdGuardHome -s stop
sudo rm -rf /opt/AdGuardHome
# Repeat the install steps with the latest release

  • Don’t Use ‘Public’ DNS as Upstream for Privacy
    For true privacy, choose a trusted, no-logs DNS provider as your upstream (Quad9, Cloudflare, AdGuard DNS), ideally via DNS-over-HTTPS.

  • Network Loops
    Never set AdGuardHome to use itself as an upstream—this creates a DNS loop! Always use an external resolver.

  • Blocklist Quality
    Some blocklists may over-block or cause breakage (e.g., banking portals, login pages). If something breaks, temporarily disable blocklists or use whitelists.

  • Device Bypass
    Assign a different DNS (e.g., 8.8.8.8) on devices you want to bypass all filtering.

  • Multiple Networks
    If you have separate VLANs or guest Wi-Fi, ensure traffic can reach the AdGuardHome server, or run AdGuardHome in those network segments as needed.

Conclusion#

AdGuardHome brings simple, robust, and open-source ad/tracker blocking to your whole network. It’s ideal for privacy-conscious users, families, and small businesses who want consistent adblocking—from any device and without expensive hardware or cloud services.

Keep AdGuardHome updated (especially during security urgent releases), pick high-quality blocklists, and enjoy a faster, safer, and less annoying web for everyone behind your network!

For FAQs, troubleshooting, and advanced guides, see the official wiki. Happy browsing!

What should you decide before deploying AdGuard Home?#

Decide whether DNS filtering belongs on one device, a home network, or a small team network. That choice changes who owns breakage, how allowlists are maintained, and what fallback resolver is available when a legitimate service fails.

Definition#

  • DNS filtering - blocking or allowing domains at the resolver layer before apps and browsers connect to advertising, tracking, malware, or unwanted service endpoints.

Comparison#

Setup Use when Watch out for
Device-level DNS You only control one phone or laptop Other devices keep leaking or resolving normally
Network-level AdGuard Home You control the router or resolver path One bad list can break many users at once

FAQ#

Does AdGuard Home replace browser hardening?#

No. DNS filtering helps before connections happen, but browser storage, account identity, cookies, and fingerprints still need separate controls.

What should be monitored after deployment?#

Watch blocked-query spikes, broken login flows, allowlist changes, upstream resolver health, and whether devices are bypassing the configured resolver.