AdGuard Home

Home Networking & Privacy

A DNS service on your own device that filters queried domains for devices using it.

Use with conditions

Official website Repository

Last updatedRelease 2026-08-18

Open source licenseGPL-3.0

PlatformsWindows · macOS · Linux · FreeBSD · OpenBSD (architecture combinations follow the official table)

DeploymentSelf-hosted service

About this project

AdGuard Home is a DNS filtering service run on a device controlled by its administrator. When clients use it for DNS, their domain requests are processed according to its configuration, filtering advertising and tracking sources at that layer. Operating a local instance and using the public AdGuard DNS service are distinct ways of obtaining DNS filtering.

The management interface supports blocklists, custom rules, activity monitoring and settings for individual clients. The project also lists encrypted upstream DNS protocols, optional DHCP and a REST API. Domain rules, client configuration and upstream resolution together determine how requests are handled, while the interface and API provide different routes for managing the running service.

Filtering at the domain level does not modify individual elements inside a webpage. The project explicitly documents a limitation when advertising and normal content share the same domain: DNS cannot readily separate them. Examples include some video platform advertising and sponsored social content. Understanding that domain structure is therefore part of interpreting what this filtering method can and cannot block.

AdGuard Home: Overview AdGuard Home official repository README

Decision guide

Why it is worth a look

Rule-based filtering of advertising and tracking domains
Web configuration, client rules and query monitoring

Before you use it

DNS filtering cannot block every advertisement that shares a domain with content; the official documentation explicitly lists limitations such as YouTube
The first-run setup listens on port 3000; restrict local or LAN interfaces and permissions for the intended use
Judgment: Changing router DNS affects covered devices; outages or incorrect rules can prevent access to apps or websites
Record original DNS/DHCP settings, test on one device and verify recovery before expanding the scope

Manual setupHigh

With an AI agentHigh

DeploymentSelf-hosted service

Additional requirements3 confirmed

An always-on supported device and administrator permissions; Available DNS port 53 and initial setup port 3000; Listen only on appropriate local or LAN interfaces; A local administrator account; this does not require registration with a cloud service; Record original DNS/DHCP settings and prepare recovery beforehand; Confirmed requirements: Command line, An always-on device or service, Account

What it can do

Rule-based filtering of advertising and tracking domains
Web configuration, client rules and query monitoring
Optional encrypted upstream DNS and DHCP

Who it fits

Good for

Home network users willing to maintain an always-on host and understand DNS configuration

Not a fit

Judgment: Users requiring guaranteed removal of all video advertising or unwilling to maintain a network service

Getting started

Match the system and architecture on the official stable release page, then download and extract the precompiled package
Read deployment security documentation and check permissions, port 53 and administration interface access
Install the system service with user authorization, create a local administrator and configure upstream DNS
Change DNS on one test device only; verify app access and recovery before deciding whether to change router DNS

Alternatives to consider

What it takes

Getting startedHigh

Ongoing maintenanceHigh

Failure impactHigh

Knowledge neededHigh

Not selected for comparison.

Get help from an AI agent

DeploymentSelf-hosted service

Additional requirements3 confirmed

With an AI agentHigh

{
  "project": "AdGuard Home",
  "decision": "Use with conditions",
  "purpose": "A DNS service on your own device that filters queried domains for devices using it.",
  "repository": "https://github.com/AdguardTeam/AdGuardHome",
  "official_site": "https://adguard.com/en/adguard-home/overview.html",
  "deploy_shape": "Self-hosted service",
  "additional_dependencies": "An always-on supported device and administrator permissions; Available DNS port 53 and initial setup port 3000; Listen only on appropriate local or LAN interfaces; A local administrator account; this does not require registration with a cloud service; Record original DNS/DHCP settings and prepare recovery beforehand; Confirmed requirements: Command line, An always-on device or service, Account",
  "direct_setup": "High: precompiled packages still require system services, permissions and DNS configuration",
  "ai_assisted_setup": "Moderate to High: AI can explain ports, logs and configuration; it cannot replace network access and recovery verification",
  "operational_burden": "High: an always-on host, updates, filtering rules, query logs and configuration backups",
  "operational_risk": "High: affects domain resolution for dependent devices; public exposure adds abuse and attack risks",
  "knowledge_requirement": "High: DNS, system services, permissions, network interfaces and router settings",
  "license": "GPL-3.0",
  "install_steps": [
    "Match the system and architecture on the official stable release page, then download and extract the precompiled package",
    "Read deployment security documentation and check permissions, port 53 and administration interface access",
    "Install the system service with user authorization, create a local administrator and configure upstream DNS",
    "Change DNS on one test device only; verify app access and recovery before deciding whether to change router DNS"
  ],
  "good_for": "Home network users willing to maintain an always-on host and understand DNS configuration",
  "avoid_if": "Judgment: Users requiring guaranteed removal of all video advertising or unwilling to maintain a network service"
}