This project is designed to support a docker compose deployment of Adguard Home using Unbound DNS upstream with a persistent Redis cache for Unbound.
The default configuration is tuned for performance:
- Unbound is configured as a forwarder, see forward-records.conf
- Unbound is configured to serve expired, min ttl = 300/max ttl = 86400, and prefetch= on
To run, execute the following command from the project root directory:
docker compose -f "adguardhome-unbound-redis-compose.yml" up -d --build
Once running navigate to http:https://{$HOSTNAME}:3000 to intialize Adguard Home
These settings should be setup when you first get started so that Redis and Unbound behave as expected.
sudo sysctl vm.overcommit_memory=1
sudo sysctl -w net.core.wmem_max=8388608
sudo sysctl -w net.core.rmem_max=8388608
sudo nano /etc/sysctl.conf
vm.overcommit_memory=1
net.core.rmem_max=8388608
net.core.wmem_max=8388608
Custom Unbound configuration can be stored at /unbound-config/custom/*.conf
Examples can be found at unbound-config/examples and will override base configuration.
Run the following on the host machine within the project root directory:
sudo chown 1500:1500 unbound-keys
Run the following from attached shell on the unbound container:
unbound-control-setup -d /etc/unbound/keys
Create (or copy from examples directory) unbound-config/custom/remote-control.conf with the following:
remote-control:
control-enable: yes
server-key-file: "/etc/unbound/keys/unbound_server.key"
server-cert-file: "/etc/unbound/keys/unbound_server.pem"
control-key-file: "/etc/unbound/keys/unbound_control.key"
control-cert-file: "/etc/unbound/keys/unbound_control.pem"
Once added, restart the container for unbound for the changes to take effect.
Custom Redis configuration can be stored at /redis-config/custom/*.conf
Examples can be found at redis-config/examples and will override base configuration.
Redis and Unbound communicate via unix sockets to reduce overhead
In redis.conf, sockets are configured:
unixsocket /tmp/docker/redis.sock
unixsocketperm 777