selfhost.directory

The index of self-hostable projects — ranked, categorized and served with live updates.
Own your data and stop giving it to big tech.

GitHub
pihole-v6-unbound logo

Self-host pihole-v6-unbound

2026.10.1-unbound1.25.2-r2

Pi-hole plus Unbound DNS resolver in one Docker container

ReleaseOpen Source
Updatedlast week
LanguageShell
Setup difficultyEasy
Stars
1 334
Ports
53, 443, 80 (Pi-hole web interface)
Docker
mpgirro/pihole-unbound

What is pihole-v6-unbound?

A single container image from this repository bundles Pi-hole together with the Unbound recursive DNS resolver: the build starts from the upstream Pi-hole container and adds a step that installs and configures Unbound inside it, following the guidance the Pi-hole project publishes for that setup. It suits anyone who wants a local resolving DNS service without chaining two containers, since the bundled resolver is reachable at 127.0.0.1#5335 out of the box. Rebuilds happen automatically through GitHub Actions with Renovate keeping things fresh, and a weekly job refreshes the Unbound package so security updates do not wait on Pi-hole releases. Tags mirror upstream Pi-hole versions, and every build additionally gets an immutable, more explicit tag. Images land on both Docker Hub and GitHub's own registry. Tuning happens through the same environment variables the upstream Pi-hole container accepts, with a sample compose.yaml plus a .env file in the repo. The older chriscrowe image this project succeeded has been deprecated, so migrations must change the image name. There is no project homepage and no licence statement in the sources; bugs in Pi-hole or in Unbound itself belong upstream, and this tracker is only for image-publishing problems.

pihole-v6-unbound alternatives

Should you self-host pihole-v6-unbound?

pihole-v6-unbound scores 51/100 on selfhost.directory (how scoring works) and ranks #24 of 41 in DNS. It has 1 334 GitHub stars, -5 in the last 30 days.

It shipped 12 stable releases in the past year. The latest, 2026.10.1-unbound1.25.2-r2, came out on 31 October 2026. New versions land roughly every 3 weeks.

Setup is easy: most people get it running in one sitting. An official Docker image is available. It is written mostly in Shell.

Its closest alternative on selfhost.directory is Pi-hole (87/100, 61 709 stars). It scores higher overall, so compare the two before you pick. See pihole-v6-unbound vs Pi-hole side by side.

Features

  • Automated image builds
  • Environment Variable Configuration
  • Example Docker Compose deployment
  • Integrated Unbound recursive resolver
  • Publishing to Docker Hub and GHCR
  • Upstream-aligned version tagging
  • Weekly security rebuilds

pihole-v6-unbound README

Pi-hole + Unbound on Docker

A Docker image for running Pi-hole with integrated Unbound DNS resolver in a single container.

This is the official and maintained successor repository of the original cbcrowe/pihole-unbound image by @chriscrowe

BREAKING CHANGE!

TL;DR: The image changed. chriscrowe/pihole-unbound is deprecated and no longer receives updates. Change your setup to use the new image mpgirro/pihole-unbound.

How to configure pihole-v6-unbound

  • TZUTCTimezone, so logs rotate at local midnight instead of UTC midnight.

    values: <Timezone>

  • FTLCONF_webserver_api_passwordrandomPassword for the Pi-hole admin page; run docker logs pihole | grep random to find the generated one.

    values: <Admin password>

  • FTLCONF_dns_upstreams127.0.0.1#5335Upstream DNS server(s) Pi-hole forwards queries to, separated by semicolons; supports #[port] and Docker service names.

    values: IPs delimited by ;

  • FTLCONF_dns_dnssecEnables DNSSEC in pihole.toml.

    values: true | false

  • FTLCONF_dns_listeningModePi-hole FTL listening mode.

    values: single

pihole-v6-unbound releases & version history

@ Every self-hosted release, weekly

One Monday email with the week's stable releases across the directory.

More in DNS

Rate this project

Click to rate — no account needed.

0 comments

Posting as guest
Loading comments…