Skip to main content
AdGuard Home: the dashboard, showing DNS query counts, blocked domains and the most active clients 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

Install AdGuard Home on your VPS

Prerequisites: a Linux VPS with 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:
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:
Start the container:
On Ubuntu, systemd-resolved already holds port 53. The AdGuard Home Docker documentation 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:
    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 and the DNS challenge the documentation recommends. When Certbot asks for the names, enter dns.example.org *.dns.example.org:
    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:
The domain is blocked by the filter list enabled by default. With the default blocking mode, the answer is the null 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.
The console 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.

Going further

No VPS at OnetSolutions yet? Pick yours and run AdGuard Home in a few minutes.