> ## Documentation Index
> Fetch the complete documentation index at: https://blog.onetsolutions.net/llms.txt
> Use this file to discover all available pages before exploring further.

# AdGuard Home: block ads and trackers everywhere on your VPS

> Run AdGuard Home on a VPS: an encrypted private DNS (DNS-over-TLS) that blocks ads and trackers on every device. Step-by-step Docker setup, OnetSolutions.

![AdGuard Home: the dashboard, showing DNS query counts, blocked domains and the most active clients](https://mintcdn.com/onetsolutions-blog/qDU15Upo4atDfpJO/images/2026/11/adguard-home.webp?fit=max\&auto=format\&n=qDU15Upo4atDfpJO\&q=85\&s=974e5a36e1100378b5facd2527a989cb)

*Published on November 22, 2026*

Your phone and laptop reach dozens of ad and tracking domains every day, at home and on the road: AdGuard Home, running on a VPS, filters those DNS queries for all your devices, wherever they are.

## What AdGuard Home does for you

* **Block** ads, trackers, phishing and malware domains at the DNS level, with no software to install on each device.
* **Encrypt** your DNS queries: AdGuard Home serves DNS-over-HTTPS, DNS-over-TLS and DNS-over-QUIC with no extra software.
* **Protect** devices that accept no blocker at all: smart TVs, speakers, IoT devices.
* **Tune** filtering per device, with your own lists and rules.
* **Watch** your network activity from the dashboard and the query log.

## At a glance

| | |
| - | - |
| License | GPL-3.0 |
| Language | Go (server), TypeScript (web interface) |
| Latest release | v1.0.0, released November 19, 2026 |
| GitHub stars | 38,730 as of November 22, 2026 |
| Minimum resources | Not specified in the official documentation |
| Repository | [github.com/AdguardTeam/AdGuardHome](https://github.com/AdguardTeam/AdGuardHome) |

## Install AdGuard Home on your VPS

Prerequisites: a Linux VPS with [Docker](https://help.onetsolutions.net/tutorials/how-to-install-docker) and its Compose plugin, and a domain name whose DNS zone you manage.

In your domain's zone, create two `A` records pointing to the VPS IP address: `dns.example.org` and `*.dns.example.org`. The second one serves the client identifiers (ClientIDs) described below.

Create the service directory. The `work` and `conf` subdirectories keep data and configuration across updates:

```bash theme={null}
# Service directory and persistent volumes
sudo mkdir -p /opt/adguardhome/work /opt/adguardhome/conf
cd /opt/adguardhome
```

The official documentation gives a `docker run` command. This `compose.yaml` file is a faithful transposition: same image, same volumes, same container ports. Only the useful ports are published, and plain DNS and the admin interface stay reachable from the VPS only:

```yaml theme={null}
# /opt/adguardhome/compose.yaml
services:
  adguardhome:
    image: adguard/adguardhome:v1.0.0
    container_name: adguardhome
    restart: unless-stopped
    volumes:
      - ./work:/opt/adguardhome/work
      - ./conf:/opt/adguardhome/conf
      # Let's Encrypt certificates, read-only
      - /etc/letsencrypt:/etc/letsencrypt:ro
    ports:
      # Plain DNS and setup wizard: VPS only
      - "127.0.0.1:53:53/tcp"
      - "127.0.0.1:53:53/udp"
      - "127.0.0.1:3000:3000/tcp"
      # DNS-over-TLS (TCP) and DNS-over-QUIC (UDP), open to the Internet
      - "853:853/tcp"
      - "853:853/udp"
```

Start the container:

```bash theme={null}
sudo docker compose up -d
```

> [!NOTE]
>
> On Ubuntu, `systemd-resolved` already holds port 53. The [AdGuard Home Docker documentation](https://adguard-dns.io/kb/adguard-home/docker/) explains how to disable its `DNSStubListener` if the container does not start.

## First steps

1. **Run the setup wizard.** From your workstation, open an SSH tunnel to the VPS, then browse to `http://127.0.0.1:3000`:

   ```bash theme={null}
   ssh -L 3000:127.0.0.1:3000 user@vps-ip
   ```

   The wizard asks for the listening interfaces and creates the admin account. Keep port `3000` for the web interface: it is the only one the tunnel reaches.

2. **Turn on encryption.** Get a Let's Encrypt certificate with [Certbot](https://certbot.eff.org) and the DNS challenge the documentation recommends. When Certbot asks for the names, enter `dns.example.org *.dns.example.org`:

   ```bash theme={null}
   sudo certbot certonly --manual --preferred-challenges=dns --preferred-chain="ISRG Root X1"
   ```

   In **Settings → Encryption settings**, set the server name to `dns.example.org`, then the paths `/etc/letsencrypt/live/dns.example.org/fullchain.pem` and `/etc/letsencrypt/live/dns.example.org/privkey.pem`. AdGuard Home reloads files given by path on its own when they change.

3. **Register your devices.** In **Settings → Client settings**, add one client per device with a ClientID, for example `phone`. The device then uses `tls://phone.dns.example.org` over DNS-over-TLS. On Android, enter `phone.dns.example.org` in the "Private DNS" field.

## Check that it works

From the VPS, query AdGuard Home for an ad domain. The `host` command comes with the `bind9-host` package:

```bash theme={null}
host doubleclick.net 127.0.0.1
```

The domain is blocked by the filter list enabled by default. With the default blocking mode, the answer is the null address:

```text theme={null}
doubleclick.net has address 0.0.0.0
doubleclick.net has IPv6 address ::
```

Browse for a few minutes on your phone. The queries should show up in the **Query Log**, attached to the `phone` client.

## Secure access

A DNS resolver open to the whole Internet becomes a relay for DDoS amplification attacks. That is why the `compose.yaml` above publishes port 53 on `127.0.0.1` only. Only the encrypted protocols, on port 853, are reachable from outside.

The admin interface is never exposed: it stays behind the SSH tunnel. The HTTPS port is not published either, because AdGuard Home serves the web interface and DNS-over-HTTPS on the same port.

Then restrict the service to your devices. In **Settings → DNS settings → Access settings**, list your ClientIDs under **Allowed clients**, as the documentation recommends for a public instance. Every other client is refused, including the `host` test run from the VPS.

Keep the per-client rate limit on: the documentation considers the default value sufficient in most cases.

> [!TIP]
>
> The [console firewall](https://help.onetsolutions.net/vps/firewall) adds a second barrier: allow inbound SSH and port 853 only, over TCP and UDP.

## Limits and alternatives

A DNS filter cannot block an ad served from the same domain as the content, such as YouTube ads or sponsored social media posts. Public DNS-over-HTTPS also needs a reverse proxy that forwards `/dns-query` only, with the `trusted_proxies` setting described in the encryption documentation.

| Alternative | Difference |
| - | - |
| [Pi-hole](https://pi-hole.net) | Same DNS filtering principle, but DNS-over-HTTPS and DNS-over-TLS need extra software. |
| [Blocky](https://github.com/0xERR0R/blocky) | Blocking DNS proxy configured through a YAML file, with no built-in admin interface. |
| [Technitium DNS Server](https://technitium.com/dns/) | Full DNS server that can also be authoritative for your zones, with list-based blocking. |

## Going further

* [AdGuard Home official documentation](https://adguard-dns.io/kb/adguard-home/getting-started/): installation, [Docker](https://adguard-dns.io/kb/adguard-home/docker/), [encryption](https://adguard-dns.io/kb/adguard-home/encryption/) and [running securely](https://adguard-dns.io/kb/adguard-home/running-securely/)
* [Install Docker](https://help.onetsolutions.net/tutorials/how-to-install-docker) on your VPS
* [Firewall rules](https://help.onetsolutions.net/vps/firewall): filter inbound traffic from the console
* [Hardening a Linux VPS](https://blog.onetsolutions.net/en/enhanced-vps-linux-security.md): the other settings to apply right after install

No VPS at OnetSolutions yet? [Pick yours](https://onetsolutions.net) and run AdGuard Home in a few minutes.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.