No description
d60ebfcd7d
* Disable so-rcvbuf custom value Using the default value is most of the time enough for a normal operation. This removes an Unbound warning that complains about not having the requested 1m or more for kernel buffering. * Corrected indentation * Include additional information Explained how to correctly enable so-rcvbuf. Co-authored-by: burnbabyburn <xyz258@abwesend.de> Co-authored-by: burnbabyburn <xyz258@abwesend.de> |
||
---|---|---|
one-container | ||
two-container | ||
.gitignore | ||
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.