Setup PiHole in a Synology NAS Docker (Whole Network DNS Filtering)

[@TechMeOut5]

*Are you using Pihole on your network? let us know in a comment*

[@alel1531]

It didn't work because the DNS SERVER service was installed. I uninstalled it and Pihole got off to a great start. I wanted to ask you: if wireguard is installed in server mode and all clients are connected to the network via the NAS, what should I do? Thank you.

[@1988dubeast]

This video was extremely well done. Very informative and easy to follow. I appreciate how thoughtful this video was, making installation and configuration a breeze.. Thank you very much.

[@TechMeOut5]

Thank you for watching!

[@savrip]

I've used this video twice. The old NAS was perfect the first time. The 2nd time around I totally missed the network option you showed. That's why I had to add 8888 to the firewall in order to get the page to load. Still nothing would work. Eventually I watched the video enough times I saw the correct network option! After fixing that I could remove the 8888 in the firewall rules and it ran as perfectly as last time. Thanks for the video.

[@darrell6179]

Thank you for showing in DSM 7. I'm a recent Docker user and until now I only found older videos for previous DSM version that I couldn't directly follow.

[@WunderTechTutorials]

Loved the video as always, Avi! Great job!

[@TechMeOut5]

Thanks for watching Frank!

[@alphanetworks7475]

Nice! the pihole will handle the dns filtering at the very "last stop"...nice idea!

[@fatannasty]

Great video! Thank you very much

[@JoshFisher567]

Best to set up unbound while you're at it that way you don't have to use any upstream DNS servers like Google or cloudflare. If it doesn't know the public IP it gets it directly from the source site. Only small downside is the first time you gonto a site it migjt take a second longer to load bit then it's vached so next time is super fast because whayever you jave both installed on jas it cached. Normally it goes out to Google or whoever for every query, or most Their is a container image for Synology with both combined into one.

[@QuikTechSolutions]

Excellent video Avi! Very well explained!

[@TechMeOut5]

Thanks tony. Thanks for watching

[@skyfall1975]

Great video and I managed direct. Good you did do DSM 7.

[@frenchysg8089]

I run one Pihole on my Synology, and one on the side as a backup. I use my getaway as the dns resolver, but added both pihole as DNS server for all VLANs on my UDMP. This way trafic is identified, and also all devices from my network are also using Pihole. I’ve also added a firewall rule to only allow specific dns resolver to hopefully block all hard coded dns request.

[@TechMeOut5]

Thanks for sharing!

[@JaimeVeredas]

I've already set up pi-hole in my raspberry pi but tryied do configure in my new Synology NAS 220+. But i'm unable to get pi-hole working. Firtsly i've tryed the instalation using my NAS IP and it worked but when I tryed to install using a macvlan can't manage to get it working. I've been wondering if it's because I created a bond with the 2 nics of my Synology. When I create the macvlan, instead of giving eth0, i gave bond0.

[@nickdegiorgio8819]

When adding the additional variables, I have one that is called "VIRTUAL_HOST" and the value is blank. It will not allow me to save the configuration with the value blank. Any suggestions? Could I just delete the VIRTUAL_HOST value?

[@brianhansen6906]

Same here. I also don’t have a server ip line to modify.

[@TechMeOut5]

In the virtual_host field, you simply type: pohole. Server ip is no longer needed

[@brianhansen6906]

Correction “pihole “ I did figure that out last night. Thankyou.

[@AissaouiAmor]

Great video, Trank you so much 👍

[@TechMeOut5]

Thank you! Cheers!

[@StaceySchroederCanada]

I just set up pihole in docker on my synology. I pointed my asus router to the ip on the nas but now my nas says it can't get an external ip ... pihole works and the nas works fine internally, just no ability to access the internet bring in new metadata etc. i don't have a firewall like you.

[@boban.stojanovski]

Thanks, nice tutorial

[@toukevable]

Hi, thank you but I get that error message once pihole is open. DNSMASQ_CONFIG FTL failed to start due to failed to create listening socket for port 53: Address already in use I'm not using the firewall of the nas so I did not create the rule asked this time. But I tried with the firewall and that rule too and I got the same error. What should I do ? No point to go further in the video because I dont get any infos from pihole because of that error.

[@toukevable]

I saw under an answer to that question but for me I don't know what is running on that 53 port already.

[@toukevable]

I have cloudflare connector running on docker , I tried to stop it and restart pihole but same error

[@ariyako]

Thank you so much!

[@okanerdem]

I did same steps but when i login to the pihole i saw " DNS Service not running" what can be issue ?

[@crudge]

Moved from using a Raspberry Pi to my NAS

[@Crazy--Clown]

Does Pihole filter out YT ads using their app

[@IlanEliyahu]

Shalom Avi, I followed your instructions to install Pihole on my Synology NAS but when I login to the Pihole admin webpage, the DNS service is not running, and in the Pi-hole diagnosis page I'm getting an error message "DNSMASQ_CONFIG - FTL failed to start due to failed to create listening socket for port 53: Address already in use" I'm using my Synology as an AD and a DNS server. Is it possible to have the Pihole on the same Synology as my AD and DNS server?

[@TechMeOut5]

Hi. Your question is excellent. Actually when you run your Synology as an ad and dns server, the dns listening port (53) is already "taken". This is why when you install pihole, it cannot use this listening port and spits out an error. What you will need to do at the end of the day is to seperate. On your synology run either ad and dns or pihole. Not both. Since pihole can be easily installed on a raspberry pi...i would assume this will be the economical way to go

[@crudge]

Great - thank you

[@IIWII9]

Thanks for this excellent tutorial. I've been running Pihole now for about 1 week without issues. Do you have any guidance on running unbound with this Pihole setup?

[@marcus_cole_2]

skip how too setup vm for noobs... so we have to just to more videos ...THANK YOU

[@BrunoVoeten]

I use the concept my router is pointing for the DNS to the NAS IP (pihole), what IP address should be in de DNS field of the NAS Network Interface when using a fixed IP?

[@TechMeOut5]

If you are using this concept than all devices on your network including your nas should use the routers ip address as dns server

[@alel1531]

First of all Thanks, great tutorial. Unfortunately this happens to me after I have started the service: Starting pihole-FTL (no-daemon) as pihole Stopping pihole-FTL pihole-FTL: no process found Starting pihole-FTL (no-daemon) as pihole Stopping pihole-FTL pihole-FTL: no process found Starting pihole-FTL (no-daemon) as pihole Stopping pihole-FTL pihole-FTL: no process found That's what I read in the log and I'm not getting through it. I went through the procedure twice and there are no errors. Is there something I'm missing? Thanks again.

[@steaders82]

Change DNSMASQ_USER to root

[@thijmen38]

When i try to change the DNS server on my Deco routers it gives me the message that the IP is conflicting with the subnet. Anybody knows how i could fix this?

[@ravipersonal90]

NO not working for me it dose not show the Pi-hole page

[@dakshadhikari4817]

Does this set up the pihole as a recursive dns server?

[@TechMeOut5]

Yes and no. Yes, pihole can a be a recursive dns server but no, setting it up this way will not fullfil this. The pihole will reach out to public dns servers for domains it doesnt know about

[@dakshadhikari4817]

@@TechMeOut5 Thank you for the reply. After setting it up as you described, can I switch it to a recursive DNS server?

[@CodySmiley]

Overcomplicated. In a month or three something breaks when installing something else etc and you have a problem because of the custom configuration.

[@TechMeOut5]

Its been running this way for over a year with zero issues, the configuration isn't all that "custom"

[@skyfall1975]

You can save the docker json file after creating everything. And you can still point individual devices to the pinhole instead off the router directly.