docker-pihole-unbound/README.md

# Pi-Hole + Unbound on Docker

### Use Docker to run [Pi-Hole](https://pi-hole.net) with an upstream [Unbound](https://nlnetlabs.nl/projects/unbound/about/) resolver.

This repo has 2 different `docker-compose` configs-- choose your favorite. The `two-container` config may work better on Synology due to usage of `macvlan` networking which helps prevent port conflicts with the host.

- [`one-container`](one-container/) (new) - Install Unbound directly into the Pi-Hole container
  - This configuration contacts the DNS root servers directly, please read the Pi-Hole docs on [Pi-hole as All-Around DNS Solution](https://docs.pi-hole.net/guides/unbound/) to understand what this means.
  - With this approach, we can also simplify our Docker networking since `macvlan` is no longer necessary.
- [`two-container`](two-container/) (legacy) - Use separate containers for Pi-Hole and Unbound
  - This configuration uses MatthewVance's [unbound-docker](https://github.com/MatthewVance/unbound-docker) container to implement encrypted DNS to third party DNS resolvers (eg Cloudflare). This is arguably less privacy-friendly since you're handing your DNS queries to those 3rd party providers.
Updated README 2019-02-05 06:01:38 +01:00			`# Pi-Hole + Unbound on Docker`

Single container support (#11) Adding a 2nd docker-compose config for running both Pi-Hole and Unbound in the same container (following recommended steps in the Pi-Hole docs). Restructuring the project to maintain the old 2-container setup as well. 2020-12-31 21:23:33 +01:00			`### Use Docker to run [Pi-Hole](https://pi-hole.net) with an upstream [Unbound](https://nlnetlabs.nl/projects/unbound/about/) resolver.`
Updating README and cleaning up docker-compose 2019-02-03 01:53:58 +01:00
Update README.md 2021-03-21 00:36:29 +01:00			This repo has 2 different `docker-compose` configs-- choose your favorite. The `two-container` config may work better on Synology due to usage of `macvlan` networking which helps prevent port conflicts with the host.
Updating README and cleaning up docker-compose 2019-02-03 01:53:58 +01:00
Single container support (#11) Adding a 2nd docker-compose config for running both Pi-Hole and Unbound in the same container (following recommended steps in the Pi-Hole docs). Restructuring the project to maintain the old 2-container setup as well. 2020-12-31 21:23:33 +01:00			- [`one-container`](one-container/) (new) - Install Unbound directly into the Pi-Hole container
			`- This configuration contacts the DNS root servers directly, please read the Pi-Hole docs on [Pi-hole as All-Around DNS Solution](https://docs.pi-hole.net/guides/unbound/) to understand what this means.`
Update pihole base container to 2021.09 (#72) * Update pihole base container to 2021.09 * README typo fix 2021-09-20 02:20:56 +02:00			- With this approach, we can also simplify our Docker networking since `macvlan` is no longer necessary.
Single container support (#11) Adding a 2nd docker-compose config for running both Pi-Hole and Unbound in the same container (following recommended steps in the Pi-Hole docs). Restructuring the project to maintain the old 2-container setup as well. 2020-12-31 21:23:33 +01:00			- [`two-container`](two-container/) (legacy) - Use separate containers for Pi-Hole and Unbound
			`- This configuration uses MatthewVance's [unbound-docker](https://github.com/MatthewVance/unbound-docker) container to implement encrypted DNS to third party DNS resolvers (eg Cloudflare). This is arguably less privacy-friendly since you're handing your DNS queries to those 3rd party providers.`
Update pihole base container to 2021.09 (#72) * Update pihole base container to 2021.09 * README typo fix 2021-09-20 02:20:56 +02:00