AdGuard Home review — DNS ad blocker for your entire network
AdGuard Home is a self-hosted DNS server that blocks ads, trackers and malware domains before they reach your devices. One installation covers everything on your network that uses it for DNS — smart TVs, gaming consoles, phones, laptops — without configuration per device.

AdGuard Home review
AdGuard Home is a self-hosted DNS server that blocks ads, trackers and malware domains before they reach your devices. One installation covers everything on your network that uses it for DNS — smart TVs, gaming consoles, phones, laptops — without configuration per device.
Who is this for? Anyone with a home server, NAS or Raspberry Pi who wants to block ads and trackers for the entire network. It also comes with the firmware of GL.iNet routers — see the GL.iNet setup guide. Pi-hole is the main alternative.
How DNS blocking works
When your browser wants to load ads.google.com, it first asks the DNS server: “What is the IP address of ads.google.com?” With AdGuard Home, your devices send that question to AdGuard Home. If the domain is on a blocklist, AdGuard Home answers with the address 0.0.0.0 (or :: for IPv6), its default blocking response: an address that leads nowhere. The browser doesn’t load the ad — no connection was ever made.
This works for every device using your AdGuard Home as a DNS server. No browser extension needed, no per-app configuration.
Specifications
| Property | Value |
|---|---|
| Type | Self-hosted DNS sinkhole |
| Blocklists | AdGuard DNS filter on by default; built-in catalogue with OISD, HaGeZi, Steven Black and others |
| Upstream DNS | Any DNS provider; default is Quad9 via DNS-over-HTTPS (on GL.iNet routers: 8.8.8.8 and 9.9.9.9, unencrypted) |
| Encrypted DNS | DNS-over-HTTPS, DNS-over-TLS, DNS-over-QUIC and DNSCrypt as upstream; can also serve DoH/DoT/DoQ itself |
| Per-client rules | Yes — different rules per device |
| Statistics | Yes — built-in dashboard and query log |
| Interface languages | Many, including Dutch (follows your browser language) |
| Platforms | Linux, macOS, Windows, FreeBSD, OpenBSD (x86, ARM incl. Raspberry Pi, MIPS and more); Docker, Snap; built into GL.iNet firmware |
| Open-source | Yes (GPLv3) |
| Price | Free |
GL.iNet integration — built-in
GL.iNet routers (Flint 2, Beryl AX, Slate AX) have AdGuard Home built into the firmware. Nothing to install separately — switch it on in the GL.iNet web interface.
Once it is on, devices that use the router for DNS go through AdGuard Home. A device set to its own DNS server skips it, unless you switch on Override DNS Settings of All Clients in the router’s DNS settings (off by default), and that only catches unencrypted DNS. Two defaults differ from a standalone install: the upstream servers are 8.8.8.8 and 9.9.9.9, unencrypted, and AdGuard Home has no password of its own. GL.iNet starts it in a mode where only a browser that is logged in to the router gets in (our reading of firmware 4.7.4 and 4.11 and AdGuard Home’s source, not tested on a device). See the GL.iNet setup guide for the steps.
Self-hosting — Raspberry Pi, home server or VPS
On other hardware, install AdGuard Home with the official install script (see adguard.com/adguard-home, or the source on GitHub). It also exists as a Docker image; the privacy DNS guide has a Docker command. The steps are under Getting started below.
Keep it on your home network. If you run it on a VPS, don’t leave plain DNS open to the whole internet: AdGuard warns that this exposes the server to DDoS attacks. AdGuard’s own security notes say a public instance needs access settings (allowed clients) and rate limiting, and to switch off plain DNS from outside if all your devices can use encrypted DNS.
Dashboard and statistics
AdGuard Home has a built-in web interface showing:
- How many requests have been blocked
- Which domains are queried and blocked most often
- Top clients: how many requests each device sends
- Query log: every DNS request, per device, in real time
This also makes visible which devices are unexpectedly sending traffic — a smart TV trying to contact tracker servers shows up right away.
By default the query log keeps 90 days of requests and the statistics 24 hours, on the device itself. You can shorten that under Settings → General settings.
Upstream DNS configuration
AdGuard Home forwards requests for non-blocked domains to an upstream DNS provider. Out of the box that is Quad9 over DNS-over-HTTPS (https://dns10.quad9.net/dns-query), the Quad9 address without malware blocking. In France, Quad9 stops serving users on 24 November 2026 (see the privacy DNS guide). You can pick another:
| Provider | DoT/DoH | Privacy | Malware blocking |
|---|---|---|---|
| Quad9 (9.9.9.9) | Yes | Good | Yes (dns.quad9.net) |
| Cloudflare (1.1.1.1) | Yes | Fair | Via 1.1.1.2 |
| Google (8.8.8.8) | Yes | Poor | No |
The ratings follow our privacy DNS guide. For privacy-sensitive use, an independent privacy-friendly resolver is usually a better default than your ISP’s DNS.
AdGuard Home vs Pi-hole
| AdGuard Home | Pi-hole | |
|---|---|---|
| Installation | Script / Docker / Snap / binary | Script / Docker |
| Built-in DoH/DoT | Yes | Needs extra software (e.g. dnscrypt-proxy) |
| Interface | Modern, many languages incl. Dutch | Functional, English only |
| Blocklists | Built-in catalogue (Choose from the list) or your own URL | Paste list addresses (Lists) |
| Reverse DNS | Yes | Yes |
| Community (GitHub stars, 7 Nov 2026) | ~38,200 (since 2016) | ~61,700 (since 2014) |
| Open-source | GPLv3 | EUPL |
For new installations we recommend AdGuard Home: encrypted upstream DNS and a Dutch interface without extra software.
Privacy: what AdGuard Home sends out
AdGuard (the company, Adguard Software Ltd) says in its AdGuard Home privacy notice that AdGuard Home “does not send anything to us”: your logs stay on your own device. It does connect out for its job: your DNS queries go to the upstream (Quad9 by default; 8.8.8.8 and 9.9.9.9 on GL.iNet), it downloads filter lists from their hosts, and it checks for updates by downloading a version file from AdGuard’s server (static.adtidy.org). Browsing security and parental control, both off by default, send a 4-character hash prefix of each domain to AdGuard.
Caveats
DNS blocking is not watertight: ads served from the same domain as the content (AdGuard’s own examples: YouTube and Twitch ads, sponsored posts on Facebook and Instagram) cannot be blocked by DNS without breaking the service itself. Combine with a browser extension like uBlock Origin for better coverage.
No HTTPS inspection: AdGuard Home only sees DNS requests, not the contents of HTTPS connections. That is also good — it would undermine encryption.
Availability during outage: If AdGuard Home goes offline, DNS stops working for clients that depend entirely on it. Think through your fallback or recovery plan in advance.
Pros and cons
Pros
- Blocks ads, trackers and malware domains for every device that uses it for DNS, without per-device configuration
- Encrypted upstream (DoH/DoT/DoQ/DNSCrypt) built in; on a standalone install the default upstream is already Quad9 over DoH
- Natively integrated into GL.iNet routers (Flint 2, Beryl AX) — switch it on in the router panel
- Per-client rules let you apply different blocking policies per device
- Real-time query log shows exactly which devices are contacting which domains
Cons
- Cannot block ads on the same domain as the content (e.g. YouTube) — use uBlock Origin alongside it
- If AdGuard Home goes offline, DNS may stop working for clients that fully depend on it
- Sees all DNS queries from all devices — adds a local single point of trust (query log kept 90 days by default)
Conclusion
AdGuard Home is an effective free privacy measure at network level. One installation on your router or Raspberry Pi covers every device that uses it for DNS, without configuration per device. Combined with a privacy-friendly upstream DNS provider (such as Quad9), it blocks a big share of ads and trackers, in AdGuard’s own words, though not all: see the caveats above.
Getting started
These steps match AdGuard Home v0.107.80 (stable, November 2026) and GL.iNet firmware 4.11. A v1.0 with a new interface is in beta; menu names may change there. The interface follows your browser language, so in a Dutch browser you’ll see Dutch labels.
On a GL.iNet router (simplest)
Open the GL.iNet web interface at 192.168.8.1. Go to Applications → AdGuard Home and switch AdGuard Home on. AdGuard Home then filters the DNS requests of devices that use the router for DNS. For upstream DNS and blocklists, open AdGuard Home’s own interface via the Settings Page link (port 3000) and continue with steps 5 and 6 below. On GL.iNet the upstream there is 8.8.8.8 and 9.9.9.9 (unencrypted), not Quad9: replace them as in step 5; the GL.iNet setup guide has the router-specific details.
On Raspberry Pi or other Linux host
-
Give the device a fixed IP address, e.g. a DHCP reservation in your router. The wizard warns about this too: AdGuard Home is a server, and if the router hands it a different address later, your network loses DNS.
-
Run the install script (from AdGuard’s README; it installs to
/opt/AdGuardHome, registers a service and starts it):curl -s -S -L https://raw.githubusercontent.com/AdguardTeam/AdGuardHome/master/scripts/install.sh | sh -s -- -vPrefer to read it first? Download
install.shfrom the same address, read it, then runsh install.sh -v. A firewall on the host (firewalld on Fedora, for example) must let through 3000/TCP for the setup, 80/TCP for the web interface and 53/UDP for DNS. On Fedora, AdGuard’s FAQ also recommends installing into/usr/local/bin(-o /usr/local/bin) because of SELinux. -
Run the setup wizard right away. Open
http://<IP of the device>:3000and click Get Started. Until you finish the wizard, anyone on your network who opens that address could set it up.
Under Admin Web Interface you choose the listen interface and the port (default All interfaces, port 80); under DNS server the same for DNS (port 53). If port 53 is already taken by
systemd-resolved(Ubuntu, for example), the wizard shows a Fix button that switches off its DNSStubListener; on Docker or Snap you do that yourself (AdGuard FAQ). The screen also shows the Static IP Address check.Limit the web interface to your home network. At Listen interface under Admin Web Interface, pick the device’s own network connection instead of All interfaces (the list shows name and address, e.g.
eth0 - 192.168.1.10). The web interface is then not reachable via the device’s other connections, such as a VPN or the public address of a VPS. To change it later:address:underhttp:inAdGuardHome.yaml, then restart AdGuard Home. On a VPS, never leave the web interface open to the internet.
Next, under Authentication, you create a username and password (8 to 72 characters) — required, even if AdGuard Home is only reachable on your local network. There is no default login. The wizard then shows the addresses your devices should use (Configure your devices); click Open Dashboard.
-
Point your router’s DNS at AdGuard Home. Write down the router’s current DNS setting first, so you can switch back if the device is ever down. In the router’s LAN/DHCP settings, enter the AdGuard Home device’s IP as the DNS server. Leave no public DNS server next to it: devices may use that one and skip the filter. Devices pick up the change when they renew their DHCP lease (reconnect Wi-Fi to speed it up).
-
Check or change the upstream. In the web interface (from now on at
http://<IP>— the port you chose in the wizard, 80 by default; 3000 is only for the first setup), go to Settings → DNS settings → Upstream DNS servers. The default is Quad9 without malware blocking. For Quad9 with malware blocking, replace it withtls://dns.quad9.net(orhttps://dns.quad9.net/dns-query), click Test upstreams, then Apply. Used Mullvad DNS here? Mullvad set 2 November 2026 as the end date of its public DNS service; switch that upstream to Quad9. -
Add blocklists (optional). The AdGuard DNS filter is on from the start. More lists: Filters → DNS blocklists → Add blocklist → Choose from the list (e.g. OISD Blocklist Small or HaGeZi’s Normal Blocklist), then Save.
-
Check it works: Query Log should show requests from your devices, each with its own address.
HTTPS for the web interface. Without HTTPS, your login and password cross the network unencrypted. Under Settings → Encryption settings, switch on Enable Encryption (HTTPS, DNS-over-HTTPS, and DNS-over-TLS), fill in a Server name, the certificate (Certificates) and the Private key, then Save configuration. Open the https:// address first and check that it works; only then tick Redirect to HTTPS automatically, otherwise a certificate problem locks you out of the web interface. Locked out anyway? Set enabled: false (or force_https: false) under tls: in AdGuardHome.yaml and restart AdGuard Home. You need a certificate for a domain name you control; on a home network that is extra work, so at the very least limit the web interface to your home network as in step 3.
Forgot the password? There is no reset command. AdGuard Home stores the password as a bcrypt hash in AdGuardHome.yaml (in /opt/AdGuardHome with the install script). AdGuard’s reset instructions: make a new hash with htpasswd -B -C 10 -n -b <USERNAME> <PASSWORD>, paste it as password: under users: in that file, and restart AdGuard Home. After 5 wrong logins AdGuard Home blocks further attempts for 15 minutes (defaults).
Already have a setup?
- Moving from Pi-hole: AdGuard Home can’t import Pi-hole’s settings. Add your list URLs again under DNS blocklists (AdGuard Home reads hosts-file and domain-only lists). Both need port 53, so install AdGuard Home on another device or stop Pi-hole first, and change the router only once AdGuard Home answers.
- Updating an existing AdGuard Home: use Update now in the web interface, or
./AdGuardHome --update. Don’t run the install script with-rfor an update: it removes the AdGuard Home folder, including your settings, before installing again. Docker and Snap installs don’t update themselves; update the image or package.
Next step
Chosen AdGuard Home?
- Setting up a GL.iNet travel router — activating AdGuard Home on GL.iNet Flint 2, Beryl AX or Slate 7
Similar options
- Pi-hole review — the older project (on GitHub since 2014, AdGuard Home since 2016), with more GitHub stars
Want to go further?
- Which network setup fits your profile? — DNS blocking as part of your overall network security
- Raspberry Pi as a home privacy box — DNS filtering and safe remote access on one small home server