Block Ads on your ENTIRE Network! Synology Pi-hole Setup Tutorial
Vložit
- čas přidán 3. 07. 2024
- Learn how to set up Pi-hole on a Synology NAS by walking through each step using Container Manager. Pi-hole is a network-wide DNS ad blocker which filters requests and automatically blocks ads. After configuring your router to use it as your DNS server, every device on your network will automatically use it!
✅ Written Instructions: www.wundertech.net/how-to-set...
🚀 Hire Me: www.wundertech.net/wundertech...
► Product Recommendations: link.wundertech.net/rmYt
🔔 Subscribe for more tech-related tutorials and overviews: link.wundertech.net/ssYt
❤️ Check out our website: www.wundertech.net
DISCLAIMER: The information in this video has been self-taught through years of technical tinkering. While we do our best to provide accurate, useful information, we make no guarantee that our viewers will achieve the same level of success. WunderTech does not assume liability nor responsibility to any person or entity with respect to damage caused directly or indirectly from its content or associated media. Use at your own risk.
WunderTech is a trade name of WunderTech, LLC.
0:00 What is Pi-hole?
0:41 Creating a Macvlan Network Interface
4:40 Creating Docker Folders
5:10 Configuring Pi-hole on Container Manager
7:03 Bridge Network Interface & Creating the Container
8:55 Accessing & Using Pi-hole
10:20 Modifying a Routers DNS Server
12:13 Final Thoughts - Věda a technologie
Just got this working here. I watched your YT video first, and then followed along on the website. Excellent instructions, and it was trivial to get working. Thank you!
Glad to hear that it helped!!
Great tutorial ! Just an FYI I had to use port 70 for tcp as 80 was occupied.
Great video Frank. Very easy to follow along and everything is explained super clearly. Excellent!
Thanks, Avi! Appreciate you watching!
The only dude on CZcams that has super clear instructions to get this running. My only issue now is running other things in the container manager aka docker. Nothing else seems to want to run after I installed pihole. And I only use a couple devices to go through pihole and not have it set for the entire network. Eventually I'll figure out why nothing else works but at least pihole does!
Thank you! When you say nothing else works, do you get any specific errors? Anything out of the ordinary?
Just got this working on my DS423+ and DS720+ thanks for the excellent tutorial.
I'd tried using other tutorials and couldn't get pihole to work, so I'm well chuffed I got it up and running with no issues on this try.
Glad to hear that it helped!
Another great one Frank!
Thanks, Tony!
Amazing Video. The best channel on CZcams.
Thank you!
Thanks!
Thank you so much!!
Wow. Firstly thank you. I know this was for me. ... Second it's 100% working now. Third..... There's a site for viewers to get their timezones to enter but I'm not at my Mac atm to add it.. and lastly.. would it be a good suggestion for you to explain what vlans are and how they work? ... Would be a great video as I'm learning about them and why they're the only way to really get going with docker.
Thanks! The macvlan interface we are using is really just a sub-interface to our main interface. Traditionally, VLANs are configured on a routing device (router or layer 3 Switch) and a macvlan network interface isn't really the same. We're just breaking down our ethernet interface and using a sub-interface (macvlan) off the parent interface (eth0 for example).
@WunderTechTutorials thank you for this updated video, my previous pihole setup from your Docker video from a few years ago broke once I moved to Container Manager. You were very kind in helping diagnose an error I kept getting inside pihole. Looks like the issue is back with this configuration again "DNSMASQ_CONFIG FTL failed to start due to failed to create listening socket for port 53: Permission denied". I will read thru the comments of the old video to get the answer you gave me a year ago. Thank you again for making an updated video, I've been searching youtube but no one had a fresh video using Container Manager.
I'd use my synology for pihole but it's a no go with out unbound...
Thanks! Do you still have that second Pi-hole container running or did you stop it? I
@@WunderTechTutorials I only have the one from this video running. I did try an imagine update to get the latest version of pihole installed but i still have the port 53 error inside pihole. the solution last year was to install an older version of pihole and the port 53 error went away. I don't how to install and older version of pihole using this new method.
@@DelacruzDigital Hmm, definitely weird. I kind of remember that now that you say it, but I still don't know why an older version would fix it. I'd try and confirm port 53 isn't being used by anything else (maybe Synology's DNS server is installed, etc).
@@WunderTechTutorials I was thinking about that because i had this problem in the past and the reason was that I had a Synology DNS server installed. The first step should be to use a tool to see which ports on the Synology are in use.
Awesome video, keep going!
Thanks
Thank you so much!!
Great walk through. One issue I ran into was the mixed use of double and single quotes in the compose.yaml file. Docker build refused to run, but once I switches to all single quotes in the compose.yaml file it ran fine!
Did you consider as well to show how to create a recursive DNS of out Pihole using unbound? I think ppl might be interested. Overall very nice and detailed video!
Yeah, I am going to look into it. I've set it up on a Raspberry Pi but not a Synology. Maybe a future video!
Done in 12 min :) gr8 video... Just a question
how to add Unbound? without interfering with pi-holes IP?
I've used Unbound + Pi-hole on a Raspberry Pi but not a Synology. I'll look into it!
Great Tutorial and Walkthrough, got it working from you're video and written instructions. Would we able to also make this dns excess-able outside of our local address and what would be the security implications if we were to do so?
You can - the best way is to most likely use a VPN but then you'll be routing all traffic through it. I wouldn't personally use port forwarding.
Hello frank great and easy video I have a question I like to setup unbound with this can you tell us how to do this ?
Thanks! Yes that's come up a few times. Hope to create a future tutorial on it!
HI. First of all, thank you. I have learned a lot over the years also thanks to your tutorials. One thing doesn't add up to me when you access the pihole gui, why is there -2 under adlist domains instead of 183,000 or something else? last night, after giving up since it didn't resolve any names, I put pihole on the host and that number actually showed 156,246. However, there was no way to make him solve anything! What am I missing? Where am I wrong? Thanks again.
Thank you for the video. I have AT&T fiber and DNS is locked. I can't change it. Does it mean I need to run my own DNS server? Another question, how does Pihole influence on internet speed?
You can set them on each client if you'd like, but it's going to be a lot more tedious and difficult to maintain. Shouldn't have an impact on speed but selecting certain upstream DNS providers might be better from a performance perspective than others.
Worked great, thank you Frank! BUT, I cannot get teleporter to work (trying to import the whitelists that I have on my primary Rasp Pi pihole). Any ideas?
Thanks! Was the Pi-hole instance directly on Raspberry Pi OS or Docker? I am thinking that might be part of the issue if it's Raspberry Pi OS, though not positive.
@@WunderTechTutorials My primary instance is running directly on Pi OS... I thought that could be causing the problem, but then I got it to work. The issue was my impatience 😆 I thought it was hung up, but I just needed to let it cook for a while. Lots of little writes to spinning disks took longer than I was expecting! Thanks for following up, and thanks again for all your great content.
hi frank, i did everthing in the video. but my pihole container has a warning status and its in a (pihole ftl no process found) loop
So as me. Changing the "DNSMASQ_USER" from "pihole" to "root" does the trick for my. But I do not know if this is a safe or good option. Maybe Frank can mention something to this? Oh and also check you Ports. I had to change Port 80 and 67 too.
I haven't experienced that, but here is a thread with a few suggestions: www.reddit.com/r/pihole/comments/ttqwsb/docker_piholeftl_no_process_found/?rdt=63952
Hey Frank, brand new subsciber here ( from Australia), just found your channel tonight, slowly working my way through you channel, does this work with QNAP NAS or only with Synology??, I have PiHole on Rasberry Pi, I wouldn't mind trying this on QNAP though. TY
Thanks! If you can use Docker Compose, it should, but you'll have to modify it for the mount paths, etc.
What rule should you set if you have multiple vlans and ur using Unifi?
It depends. Not sure I can really give guidance on it unfortunately. Ultimately, all VLANs have to be able to access the macvlan network interface IP to use it as a DNS server.
I presently have pihole running in Docker on my NAS, but not with a macvlan. Works great, but in pihole I never see which individual client is actually making the requests. They're all lumped together into a single client IP. Would this setup with a macvlan address that and allow better client resolution in pihole? Thanks for the video.
This won't fix that scenario unfortunately. You'd need each client using DNS pointed straight to the Pi-hole IP so the requests are coming from each client as opposed to the router.
@@WunderTechTutorials Thanks. I was hoping there might be some way for my Unifi Dream Machine router to pass the clients through to pihole, but I guess this won't help in that case.
You might be able to with the UDM - If you modify the DHCP settings (Networks > Select the Name > Edit the DNS server), that might push the DNS IP to the clients. If it does, it'll accomplish what you're looking for.
Can you make tutorial if someone wants to use vmm instead of docker?
Is there a specific reason you want to do it that way? It's going to be much more resource-intensive and Docker is generally easier overall.
I messed up the subnetting on the first go around and now I am getting this error: Pool overlaps with another one on this space. Any idea where I need to go to clear it so I can try to set up the new one?
If it's the macvlan, you can delete it from the Network section of container manager.
Hmmm… I tried to, and I actually have even reinstalled container manager itself and it just isn’t wanting to cooperate… I am sure there is something I am missing but it keeps giving me that error message…. It is a good learning experience though, I am new to this stuff 😂
Very nice video, thanks. My setup is a little more complex cuz of VLANS. I have Pihole installed on synology, which is in my main LAN, but the users use different VLAN, so i have to create a firewall rule on my Ubiquiti, but i don't understand it enough to make the rule. I can make a rule to access all other VLANS to main VLAN, but then the purpose of the VLAN is gone i think, anyone who can help me out?
You'd have to allow port 53 traffic (DNS) from the VLANs to the Pi-hole server.
How much would doing this impact network performance? You're basically routing all network traffic through the NAS, yes?
You're not routing the actual traffic through the NAS - only the DNS queries. I wouldn't worry about it impacting performance unless you were using Unbound for DNS queries initially because Unbound will basically always operate faster than pushing all traffic to an upstream DNS provider. If you weren't, I don't think it'll be a huge difference. Either way, you can try it out and switch it back if you really want to see!
It was working for me but then I installed "Virtual Machine Manager" and now I cannot run pihole. I can re-install pihole using the script provided in the link below this video but then I can't run it. I get this "Container API has failed". I know it has to do with the network because I can install jellyfin and run it but I can't access it either. If you have any advise that might help me, I would greatly appreciate it. Thanks
Did you try deleting and recreating the macvlan network interface? I suspect that the interface name changed and that's why it's not working.
@@WunderTechTutorials Thank you for responding. Yes I tried it before and after removing virtual machine manager and it did not work. So searched online to figure out what changes when virtual machine is added and it turns out; when creating the macvlan you have to refer to the eth0 as ovs_eth0. I changed this in the script and ran it again to create the macvlan and now jellyfin and pihole both work again.
Thank you, it works perfect!
I’m trying to extend this setup by integrating Tailscale, aiming for a seamless experience across devices, especially when off my local network. Despite following your guide closely and trying out other tutorials that attempt to merge Tailscale with Synology and PiHole, I’m hitting a roadblock, likely due to the specific PiHole configuration we followed in this tutorial. I believe it is due to the network configuration, IP addresses and the way the NAS and Pihole are interacting under MacVLAN with their own IP addresses. I don’t know how to deal with that.
Would you consider creating a tutorial that specifically addresses integrating Tailscale with the Synology PiHole setup you’ve shown? My goal is straightforward: to use PiHole with my phone (or any Tailscale-connected device) regardless of my network location.
Thanks! Have you tried using the bridge network IP as the DNS server? Tailscale + Pi-hole might be a little tough, but if it's going to work, it's going to work with the bridge IP.
Hey! Thank you for the response. I ended up setting up OpenVPN successfully with your video about it, great video! I revisited the video to understand better which DNS settings to use and to grasp the overall configuration.
Currently, my router is configured to utilize the Pi-Hole as its DNS server. For OpenVPN, I've established port forwarding to the NAS's static IP, which I assigned through the router. Additionally, I've enabled port forwarding specifically for OpenVPN. Is this the appropriate setup? Or should I have configured the port forwarding to direct towards the Pi-Hole's static IP instead?
Also, I'm curious about when to use the bridge network IP for Pi-Hole, or is it done differently with OpenVPN?. Could you shed some light on that?@@WunderTechTutorials
Thank you!
@@av1155G Thanks! Sounds like you did everything right and no, definitely no port forwarding to Pi-hole. The bridge IP is only used for NAS to Container communication. I have an example of it in the video that goes over when to use it, though if you want Pi-hole when you're using OpenVPN, you'll use it in the OpenVPN config file as well. That is gone over in the written instructions.
@@WunderTechTutorials Thank you for the response. I’ve reviewed the guide, and it all makes sense. However, I’m encountering an issue with accessing my ‘name.synology.me’ remote domains when I’m on the same local network. These domains work fine when I’m connected to a different network, like a hotspot, but they don’t load on the local network. Interestingly, when connected to the hotspot, I can access Synology via the local IP address using OpenVPN, and everything works as expected. What could be causing the remote domain to not load only when I’m on the local network?
Could it be PiHole? The VPN? Would you know a fix for this by any chance? Thank you!
Hey! I successfully set up OpenVPN and everything works, but when I go ahead to set Pi-hole as my DNS server nothing happens.
Pi-hole’s IP address (running with its own IP on the NAS as a docker container via a MacVLAN interface) is my router’s custom DNS. Pi-hole works well with any device connected to the local network.
When I set “dhcp-option DNS pi.holes.ip.address” ad-blocking does not work for the device using the VPN outside the local network, and on the admin portal in Pihole no queries show up from the device on the VPN outside the local network. I have also tried with “Permit all origins” in PIhole’s DNS settings, and nothing. I also opened port 80 and port 53 on the firewall.
I have tried so many things and cannot get it to work, would you have any idea what might be going on?
Whenever I make these kinds of changes, I'm always afraid that it is going to be horribly difficult if not impossible to undo. Also, what are the potential side effects ? Is there an easy way to reverse this ?
All you'd have to do is delete the docker container and change your dns servers back to whatever it was before...that's the benefit of using docker.
@@jasonheminger4844 Thank you. Maybe I'll dip my toe in the water then.
Like the other comment said, as long as you change the DNS server back to the default, the risk is relatively small. Keep in mind you can use a single device as well just to test it (by setting that one device to use Pi-hole as its DNS server).
Don’t forget if you WANTED to, you could also delete the MacVLAN network you made too but that part would be optional…
@@DavidM2002I'm learning too. Ya it's tough these guys know more than God but try it and hopefully you have made backups of your server. ... I have three Synology Nas units so I can play.... It's easy to reset your Nas so play a little. This is New stuff bc of docker but it's our future.
@wundertechtutorials Thanks for all your tutorials; they have been a wealth of information for a novice like myself. On this and another video previously posted, I cannot locate an available IP address to assign the Pi-hole Macvlan. I receive the following error when I execute the docker-compose script:
Error response from daemon: failed to create the macvlan port: device or resource busy
The creation of the mcvlan completed without incident so I assume there is a conflict. How do I identify an available IP address or make changes so one is available? Like I said, I am a novice :-( Thank you.
Thanks! By any chance, did you create a macvlan network interface already? If you open Container Manager and select Network, do you see any there?
@@WunderTechTutorials Yes, the macvlan interface was successfully created via ssh. I also see the bridge created via the docker-compose script before it failed with the error "device or resource busy." Can pi-hole use any of the IP addresses in the 192.168.1.x / 24 namespace that is not in use? Apologies for my ignorance.
@@derekbailey4394 Are you sure it's related to that as the problem? Are you using the 192.168.1 subnet? Is the network interface assigned to any other docker containers?
Can I also setup a VPN for my entire network in my Synology NAS?
Yes! czcams.com/video/2gkbwxm72lE/video.html
I'm not sure why but I can't get the bridge network part to work. Everything else work as expected. Please help ?
What isn't working? The NAS to Pi-hole communication?
@@WunderTechTutorials Yes the NAS to Pi-hole communication. My NAS is on 192.168.5.x vlan, not default one. I found out that only if I change "DNS/Interface settings" from "Response only on interface eth0" to "Permit all origins" then I can use the bridge network ip of 192.168.x.2 as preferred DNS server in NAS settings. Btw, I want to say thank you for taking your time and effort to share with us your knowledge. I've learned a lot from your videos from zero experience about Synology until now and I'm still learning. Cheers !!!
Is there a way to run both PiHole and AdGuard together (mainly for YT Ad Blocking)? I tried creating a macvlan network for AdGuard, but it's currently being used for PiHole. How can I set both up using eth0 IP Address. eth0 is currently being used by PiHole, eth1 is available, but I'm assuming that's the second LAN port of my synology NAS which is currently not in use.
Yeah, I think the easiest way would be to use the ETH1 port if you're already using ETH0.
@@WunderTechTutorials I really appreciate the reply, thanks! Since I’ll be using ETH1, will I need to plug an Ethernet cable from the second LAN of my Synology NAS to my router to have an assigned IP Address?
@@__AT__0Yes, that is correct!
@@__AT__0 your problem is like to me now, eth0 is used for docker adguard and I want to install pi hole too but when I created macvlan again there are warning on my ssh nas "this ip is currently used for other bla...bla...". I need to plug other lan cable from nas to my mikrotik router I think
I see you also have that "only 3 clients" bug on your pihole even though the whole network is using pihole.
i'm not being able to enter my password on windows terminal......... i have a complex password with special characters.
any help with that cause when i type it normally it always comes back as denied.
thanks in advance!
Off the top of my head, the only thing I can think of is copy/paste. Hopefully that lets it go through!
I had the same issue on a Mac. After research found out that you simply type in the PW for your NAS however none of the characters will appear. It looks as if you're doing nothing but if you type in your password correctly it will work. Took me about 5 attempts before I figured it out
I get this error in pihole. There was a problem applying your settings.
Debugging information: PHP error (2): parse_ini_file(/etc/pihole/setupVars.conf): failed to open stream: No such file or directory in /var/www/html/admin/settings.php:17
Where exactly is that error? In Docker or Pi-hole?
@@WunderTechTutorials Got it working . Using Pihole with this method can it be access by cloudflare . Can't access it by cloudflare with a public hostname.
@@Francisco-ke4lx With Cloudflare in what regard? Port forwarding?
@@WunderTechTutorials Yes
@@Francisco-ke4lx Personally, I would try and do it through a VPN rather than port forwarding. It's up to you, but port forwarding the DNS port will basically make it a public DNS server. I'm not sure why it wouldn't work through Cloudflare but I would personally do it differently.