Setup Pi-hole With Unbound On Your Synology NAS Using Docker-Compose And Git

This video goes over setting up Pi-hole and Unbound on your Synology NAS using docker-compose and git along with the synology-docker-pihole-unbound GitHub repository.

The video topics include:
• An overview of how Pi-hole and Unbound will be setup using the synology-docker-pihole-unbound GitHub repository.
• Walking through the setup steps using SSH and Git.
• Confirm and test that the Pi-hole and Unbound containers work properly using the Pi-hole web interface, dig and nslookup.

===
SUPPORT THIS CHANNEL

Synology NAS Models I use and recommend (Amazon Affiliate Links)
===

In the video I mentioned or referenced the following link:

Timecodes
0:00 | Introduction
0:20 | Setup Overview
1:36 | Prerequisites – Git Server, Docker And SSH
2:07 | Walkthrough Setup Steps Using GitHub Repository Instructions
4:21 | Confirm Pi-hole And Unbound Are Working Properly
5:44 | Closing

#synology #docker-compose #pihole #unbound #git #github

[digital_aloha]

Added TIMEZONE to .env file, edited the docker-compose.yaml file appropriately and updated the README.md file.

I realized when I was finalizing the video that I didn't add TIMEZONE as an environmental variable so I made the above updates. Now you only need to edit the .env file if you would like to adjust your TIMEZONE rather then having to edit the docker-compose.yaml file directly.

[RahulJadhavVijay]

Saved so much time using your yaml file. Thanks a lot. Please keep the videos coming. I recently bought a NAS and your videos are a great help configuring it up.

[Gill_Bates]

Thanks for a great tutorial, worked pretty much first time for me using DSM 7.2 and as a Project in Container Manager.

[LucasJanin]

Thanks a lot for this fantastic tutorial and GitHub repository! It works great, very easy to understand.
One small issue, all my other docker containers still don't see the Pi-Hole (ping not answering when I'm using the PIHOLE_BRIDGE_IP, 192.168.72.2 in your example).
Did I miss anything? Thanks

[afreisi]

Nice !, but what is the need to use an IP bridge?

[jdpdata]

Fantastic! Been waiting for this. Thanks I'll try setting up on my DS918+ tomorrow.

[daaaMook]

Thanks for this guide!

To update pihole/unbound from this setup, here are the instructions:

ssh <admin account>@<IP address of Synology NAS>

cd /volume1/docker

cd

sudo docker pull pihole/pihole
sudo docker pull mvance/unbound

sudo docker-compose down

sudo docker-compose up -d

[frankieje]

@digital_aloha Hi there, I successfully implemented this setup the other day, only to realize that unbound is not contacting root servers directly, but cloudflare. Do you know of a way to change the config so that unbound points at root dns servers? I thought that was the point of unbound in addition to Pi-Hole. Thanks for pulling all of this together.

[ozricus]

Thanks for the video! If my LAN is using 192.168.1.x with one portion set aside for DHCP and the other for static assignments, do I still use the 2 different ranges in your video? 192.168.81.x and 192.168.72.x ?

[donald]

does unbound need updated every now and then? I followed this guide but if unbound has a list of ip addresses for every website out there, doesn't it need updated? thanks for the vid

[BrenWaves-bz]

Great vid! So far so good on the setup steps, until I noticed the unbound stopped, started, stopped, etc (off / on every minute or so). in the unbound container log, I receive warnings and a "fatal glibc error cannot get entropy for arc4random". What do I do now? Thanks in advance.

[-pappy-]

very nice guide. well explained and presented perfectly. worked like a charm. you have my sub 👍

[Mido-qrbw]

I'm having trouble with the bridge network, everything else work as expected except the bridge. nslookup from NAS does not return anything (connection timed out...). Please help ?

[jaydee_]

Thanx again for this video. Great stuff! I followed all your steps and Pi hole is working as expected, but there seems to be one (small) caveat, at least in my installation. Although I see tons of entries in the Query Log from different clients, I can't see one single client in the Tools -> network -> network overview. The overview simply stays empty, regardless of what I'm trying and regardless of some configuration changes I've made (i've changed the interface settings to "permit all origins" and expanded the CIDR-Range of my local network for the conditional forwarding). So I would like to know if you do also have this issue or ran into it in the past?

[mitchellcoote]

Thanks for the video, how would you go about adding wg-easy to this setup?

[bncorbet]

You guide was awesome and I can get the containers running and login to pihole. All seems to be working, but after 30 seconds the pihole web interface stops responding. Any ideas?

[chunky_luva]

I deviated from the guide slightly. Ended up not being able to do the dig or nslookup tests at the end of the video. The dig commands not working makes sense but the nslookup failing suggests I did something wrong. However things seem to be working well as best as I can tell. Is there anything to configure for Unbound or any gui interface I can use with it? Otherwise if my pihole web admin is showing the Upstream DNS Server as the unbound ip address and everything is working as far as blocking and whitelisting then I am good right?

[jaydee_]

Thanks again for this great tutorial. You do mention that this approach fixes the issue of an IP address switch when the unbound container comes up first. Can you please briefly explain how you do prevent this with your setup? I followed your tutorial and in my installation unbound still picks up the "pihole IP" from time to time. It doesn't seem to be reproducible for me, it's pretty weird... My yaml file do have "ipv4_address: for each container, just like yours. But I don't know if that is all to prevent the occasional switch. The only thing I've done different is, that I created the macvlan network manually and not through the yaml file. Any ideas?

[ictstelucjam]

Hi, Thanks for this great expolanation. I was sooo struggling with the compose file on my OdroidM1, that now I testet it with your compose on my Syno NAS. But I am really new in the MACVLAN, I have set it up like you eplained it, and read a lot about the theme MACVLAN. But one thing isnt clear to me. I am using this and its working but, I have a second IPadress extra on my router, . So the MACVLAN has the real LAN enbdet on 115, but it took two adresses, that is, the 115, wich is correct but also a 116 at the end. In pihole the 116 is configured as the upstream DNS, So that must be the Unbound container. But I thought that the hole concept of using the MACVLAN is that is only using one IP adres, and in my case the 115. So? What am I doing wrong here? Can you please explain a little whats going wrong? Or is it normal behavior?

[xrayos]

thank you very much for this guide. worked great first time. how would you set this up to not require a password from your yaml file? I deleted the line for the password variables, but it still assigned a random password