AdGuard Home (DNS/Adblock)
AdGuard Home provides network-wide advertisement blocking and internal DNS resolution.
ID: 105
IP Address: <ADGUARD_IP>
Version: Latest Stable
1. Infrastructure Requirements
LXC Container specification for standard deployment:
| Component | Specification | Description |
|---|---|---|
| Core | Debian 12 | Standard LXC Template |
| CPU | 1 Core | Minimal processing requirements |
| RAM | 512 MB | Static allocation |
| Storage | 8 GB | local-lvm |
| Network | Static IPv4 | CIDR: <ADGUARD_IP>/24 |
| Gateway | <GATEWAY_IP> |
Secondary Router |
2. Deployment Procedure
A. LXC Creation
- Access the Proxmox Web GUI.
- Select Create CT (Container).
- Assign ID (
105) and Hostname (adguard). - Select Debian 12 template.
- Configure storage and network as specified in Section 1.
B. Installation
Connect via SSH or Proxmox Console and execute:
# Update repositories
apt update && apt upgrade -y
# Download and install AdGuard Home
curl -s -S -L https://raw.githubusercontent.com/AdguardTeam/AdGuardHome/master/scripts/install.sh | sh
C. Initial Configuration (http://<ADGUARD_IP>:3000)
Access the web wizard and configure the following:
- Listening Interface: All Interfaces.
- Admin Port:
3000. - DNS Port:
53.
3. Post-Setup Configuration
Internal DNS Rewrites
Navigate to Filters > DNS Rewrites to map internal services:
| Domain | Target IP | Reason |
|---|---|---|
pve.home |
<PROXMOX_IP> |
Host Access |
*.home |
<NPM_IP> |
Reverse Proxy Entry |
Router Integration
Set the AdGuard IP as the Primary DNS on the network router:
| Setting | Value | Description |
|---|---|---|
| Primary DNS | <ADGUARD_IP> |
AdGuard LXC Address |
| Secondary DNS | [EMPTY] | Prevents DNS bypass |
4. Verification
Execute nslookup google.com from a client device:
- Expected Server:
<ADGUARD_IP>. - Success Indicator: The AdGuard "Query Log" increments.