simono41/docker-pihole-unbound
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
No description
48 commits 1 branch 30 tags 97 KiB
Shell 53.9%
Dockerfile 46.1%
Find a file
Chris Crowe d7741de332
Changing to compose file version 3.0 
Should fix the issue seen here: https://github.com/chriscrowe/docker-pihole-unbound/issues/112
2022-03-13 20:43:56 -07:00
one-container Changing to compose file version 3.0 2022-03-13 20:43:56 -07:00
two-container fix: ServerIP env variable deprecated, and other docker-compose.yaml updates (#109) 2022-03-11 08:57:36 -08:00
.gitignore Adding script for building and pushing new images 2020-12-31 12:39:33 -08:00
README.md Update pihole base container to 2021.09 (#72) 2021-09-19 17:20:56 -07:00

README.md

Pi-Hole + Unbound on Docker

Use Docker to run Pi-Hole with an upstream Unbound 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 (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 to understand what this means.
    • With this approach, we can also simplify our Docker networking since macvlan is no longer necessary.
  • two-container (legacy) - Use separate containers for Pi-Hole and Unbound
    • This configuration uses MatthewVance's 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.