2019-02-03 01:53:58 +01:00
# Pi-Hole + Unbound on Docker (works on Synology)
## Description
Running Pi-Hole in Docker can be challenging due to networking requirements by Pi-Hole, this is especially true when the ports that Pi-Hole uses are shared by the host it's running on (this is true for Synology in the default configuration).
This project uses a [`macvlan` Docker network ](https://docs.docker.com/network/macvlan/ ) to place your containers on your main network, with their own IP addresses and MAC addresses. Pi-Hole uses Unbound as it's resolver, and Unbound uses Cloudflare (1.1.1.1) upstream in order to support DNSSEC and DNS-over-TLS.
- Uses 2 Containers
- Pi-Hole ([pihole/pihole](https://hub.docker.com/r/pihole/pihole)) - Official from Pi-Hole
- Unbound ([mvance/unbound](https://hub.docker.com/r/mvance/unbound))
2019-02-03 02:04:08 +01:00
2019-02-03 01:53:58 +01:00
## Instructions
2019-02-03 02:04:08 +01:00
### Before running...
2019-02-03 01:53:58 +01:00
- Update some things in the docker compose, such as your IP addresses/subnets.
- Add a `.env` file next to the docker-compose.yaml so you can pass in the `${WEBPASSWORD}`
- Update the secondary/backup nameserver in the `resolv.conf` file
- Lastly you might want to provide some manual DNS entries in the `dnsmasq.conf` and/or `hosts` files
2019-02-03 02:04:08 +01:00
### Run it!
2019-02-03 01:53:58 +01:00
```bash
sudo docker-compose up -d
```
2019-02-03 02:04:08 +01:00
### Test it!
2019-02-03 01:53:58 +01:00
Test your configuration with dig:
```bash
2019-02-03 01:54:52 +01:00
dig google.com @192 .168.1.248
2019-02-03 01:53:58 +01:00
# Expecting "status: NOERROR"
```
You can also test for DNSSEC functionality:
```bash
2019-02-03 01:54:52 +01:00
dig sigfail.verteiltesysteme.net @192 .168.1.248
2019-02-03 01:53:58 +01:00
# Expecting "status: SERVFAIL"
2019-02-03 01:54:52 +01:00
dig sigok.verteiltesysteme.net @192 .168.1.248
2019-02-03 01:53:58 +01:00
# Expecting "status: NOERROR"
```
2019-02-03 02:04:08 +01:00
### Serve it!
2019-02-03 01:53:58 +01:00
If all looks good, configure your router/DHCP server to serve your new Pi-Hole IP address (`192.168.1.248`) to your clients.
2019-02-03 02:04:08 +01:00
## Acknowledgements
2019-02-03 01:36:02 +01:00
2019-02-03 02:06:50 +01:00
- [http://tonylawrence.com/posts/unix/synology/free-your-synology-ports/][synology-ports]
- [https://github.com/MatthewVance/unbound-docker][unbound-docker]
- [https://pi-hole.net][pihole]
- [https://nlnetlabs.nl/projects/unbound/about/][unbound]
[synology-ports]: http://tonylawrence.com/posts/unix/synology/free-your-synology-ports/
[unbound-docker]: https://github.com/MatthewVance/unbound-docker
[pihole]: https://pi-hole.net
[unbound]: https://nlnetlabs.nl/projects/unbound/about/
