simono41/docker-pihole-unbound
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
No description
34 commits 1 branch 30 tags 97 KiB
Shell 53.9%
Dockerfile 46.1%
Find a file
chronicblondiee e26a459bf3
remove uneeded 1.1.1.1 dns entry (#53) 
* remove uneeded 1.1.1.1 dns entry

I noticed that the 1.1.1.1 dns entry is set in the docker compose file but it is not used for pihole or unbound in any way so makes sense to remove the unneeded entry

* Update docker-compose.yaml

Removing `dns` directive from docker-compose

Co-authored-by: Chris Crowe <425808+chriscrowe@users.noreply.github.com>
2021-05-27 19:51:19 -07:00
one-container remove uneeded 1.1.1.1 dns entry (#53) 2021-05-27 19:51:19 -07:00
two-container Single container support (#11) 2020-12-31 12:23:33 -08:00
.gitignore Adding script for building and pushing new images 2020-12-31 12:39:33 -08:00
README.md Update README.md 2021-03-20 16:36:29 -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 simply our 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.