https://github.com/chriscrowe/docker-pihole-unbound

Run Pi-Hole + Unbound on Docker
https://github.com/chriscrowe/docker-pihole-unbound

Last synced: about 2 months ago
JSON representation

Run Pi-Hole + Unbound on Docker

• Host: GitHub
• URL: https://github.com/chriscrowe/docker-pihole-unbound
• Owner: chriscrowe
• Created: 2019-02-03T00:25:51.000Z (over 5 years ago)
• Default Branch: main
• Last Pushed: 2024-04-29T02:25:07.000Z (5 months ago)
• Last Synced: 2024-04-29T03:32:13.109Z (5 months ago)
• Language: Shell
• Size: 61.5 KB
• Stars: 1,000
• Watchers: 38
• Forks: 264
• Open Issues: 58
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# 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.