Sign inSign up

megavolts/adguard_unbound

By megavolts

•Updated 8 months ago

An alpine base Adguard Home bundled with Unbound DNS focus docker image focus on privacy

Image
0

7.2K

megavolts/adguard_unbound repository overview

⁠Adguard Home Bundled with Unbound DNS

An Alpine Linux Based network-wides ads & trackers blocking DNS serve (AdGuard Home), bundled with a DNSSEC Validating Recursive Resolver (Unbound DNS) docker image.

This image allow to use 127.0.0.1 as un upstream DNS server in Adguard Home configuration

AdguardHome Version

Unbound Version

OpenSSL Version

CD Build Docker Image

Build status

CD Unbound Release Check

CD Build Docker Image

CD Release Tag

⁠Changes

You can see the changes in the Releases⁠ section.

⁠Architecture

  • aarch64
  • amd64
  • armv7
  • armv6

⁠Available Docker Tags

Docker Size Docker Pulls

You can pull the most recent image from Docker Hub using it's latest tag or by using the corresponding image version number:

docker pull megavolts/adguard_unbound:latest or docker pull megavolts/adguard_unbound:0.107.67-0

We used a complemented dash for any revision, for example 0.107.67-1 to reflect any new relases of OpenSSL or Unbound.

⁠DNS over Quic

We are trying to implement DNS over Quic⁠, there will be a canary build for it.

docker pull megavolts/adguard_unbound:quic

⁠Configuration

By default, this image forwards queries Cloudflare DNS server over TLS. In other words, it does not act as a recursive server. The unbound.sh file⁠ provides the configuration unless it is overriden as described below.

This docker image use local root.hints and root.zone file, updated weekly wth a cron jo.b

The example cutsom_unbound.conf file is different from the one set by unbound.sh file. The example is provided to help you re-configure this as a recursive server. To use it, map '.../custom_unbound.sh' to ..:

⁠Docker Compose

A docker-compose.yml example file is provided.

Use the same volumemappings as the original AdGuardHome container. In fact, you can just swap in this image and everything still works. You only have to update your Upstream DNS server to 127.0.0.1:5053, which enables Unbound.

As with the original AdGuardHome image, this exposes the following: \

Volumes:
Docker configuration:

⁠Volumes

  • /opt/adguardhome/work : working direcotry for AdGuardHome
  • /opt/adguardhome/conf : configuration folder for AdGuardHome
  • /opt/unbound/conf: configuration folder for unbound with unbound.conf

⁠Ports

  • 53/tcp: Plain DNS over tcp
  • 53/udp: Plain DNS over ucp
  • 67/udp: DNS only DHCP service over udp
  • 68/tcp: DNS only DHCP service over tcp
  • 68/udp: DNS only DHCP service over udp
  • 80/tcp: Aguard Home admin panel over http
  • 443/tcp: Adguard Home admin panel over https and DNS-over-HTTPS over tcp
  • 443/udp: DNS-over-HTTPS over ucp
  • 784/udp: DNS-over-QUIC
  • 853/udp: DNS-over-TLS
  • 3000/tcp: Aguard Home initial configuration page over http
  • 5335/tcp: Unbound DNS connection over tcp
  • 5335/udp: Unbound DNS connection over ucp

⁠Acknowledgements

Thanks to the many Docker Images who got me inspired. This code was heavily influenced by Hat3ph⁠, MatthewVance⁠ and team MΛDИVTTΛH⁠.

⁠Credit:

⁠Licenses

⁠License

Unless otherwise specified, all code is released under the MIT License (MIT). See the repository's LICENSE file⁠ for details.

⁠Licenses for other components

Tag summary

Content type

Image

Digest

sha256:2b683dbc2…

Size

28.7 MB

Last updated

8 months ago

docker pull megavolts/adguard_unbound