AdGuard Home as container (LXC) in Proxmox VE

After some practical daily challenges, I have decided to give a try to AdGuard Home as local DNS resolver.

One of the big differences is ability to resolve external DNS servers using DNS-over-HTTPS, DNS-over-QUIC, DNSCrypt.

ref

https://github.com/AdguardTeam/AdGuardHome

Login into Proxmox

?? Download Debian distro template for containers. For some reason it might be cancelled or disrupted. As we now, which one template is expecting to find, let's download that manually. Navigate to containers' templates storage, find suitable and hit [Download] button

Download task itself

??

Template downloaded

Script location:

https://community-scripts.org/scripts/adguard

Open node shell

Download the script:

export dir="/root/delme/"
mkdir -p ${dir}
cd ${dir}

curl -O https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/adguard.sh
ls -latr

Let's see what is inside of this script

and invoke it's from the shell, when confident:

chmod +x adguard.sh
./adguard.sh

Installation questions

Telemetry and diagnostics

Use [Down], [Space], [Enter

Kind of installation

Choose "Default Install"

Installations

Script will search for template, and if it is not found, begin download

Installation successful

Applicatin configuration

Check in the browser the URL, which is indicated by installer (HTTPS will not work at this point)

http://10.77.77.184:3000

Do not change anything, proceed with defaults

Create admin user (and note pass to password manager)

Take instructions for other devices. Usually just skip it.

Finalize application initial configuration

Login with user created.

Dashboard

The only change we want to perform is to change IP address. Locate container, open it's network configuration, change from DHCP to STATIC and define desired IP address (remember do define CIDR mask). Remember default gateway!

Open container's shell , take a note of network address and perform restart. Verify address (there are still old and new):

ip -br -a

Restart container

shutdown -r now

After reboot, Verify again

ip -br -a

ip -br a
shutdown -r now

Last thing, before go: verify that container has "Start on boot" tick box enabled. Thus, we shall be sure that DNS server will be started with hypervisor. That applies to all machines, which need to be started (such as main router :)

Add public public name servers

Navigate to DNS settings (upstream servers)

List available here

https://dox.installanduse.com/books/domain-name-system-dns/page/public-nss-doh-dot-doq

Check for "Fastest IP address"

Leave some public NSs to resolve list

Save settings

Next morning, after the first day of DNS traffic

(img)

With no filtering lists loads, DNS server serverd 54% of cached traffic to local clients. That is very good, which means, that local clients received DNS response earlier, rather then for original query.

(img)