Great video, straight to the point. :) Hint for my future self: for IPv6 add the environment variable "ServerIPv6" and as value the IPv6 of the Synology or Macvlan. In the router configure the DNS for both IPv4 and IPv6.
If only I could like a video more than once... I already own a raspberry pi that I was using exclusively as a pihole, but the idea of consolidating into an already existing piece of hardware on my network seems so much more efficient. ☑ My OCD thanks you sire!
The /32 subnet mask is used for an individual IP address. So basically, we are reserving that one IP address so that it doesn't change. Let me know if you have any other questions or need clarification!
First off. Great video. I was excited to try and install this and give it a shot. EDIT: I found the problem. It was how I pointed my win 10 to the Pihole. I'm not sure WHY the different method worked but if I follow the instructions of the website it didn't work BUT I saw another youtube video that showed a separate method of adding a DNS and that one worked no problem. Pihole is up and running and I can connect to everything with no problem. Ah well. Thank you for the great videos. I look forward to getting an actual raspberry pi to run my second pihole on.
@@WunderTechTutorials I figured out why it didn't work when I first changed my DNS. I was watching your pi hole tutorial using the Rasp Pi and in that tutorial, you showed how to flush and register your DNS on Win 10. I never knew that was a thing. Maybe add that to all the written instructions? Anytime I switch my DNS now I have no problems and don't have to restart my comp over and over to get it to work. LoL. I really do love what you do. Thank you for taking the time in making these. Its been fun,
@@kaput808 Hahaha sorry for not mentioning that earlier! Yes, that's a very important part, but only if you're changing the DNS on the local machine. If you're doing it on the router, it's not necessary. Either way, glad you got it to work and thanks so much for watching!
Thank you! You can, but just keep in mind that if any DNS requests hit that DNS server, you will not have ad-blocking. If you're okay with that, then this is a great option!
To avoid HA issues, wouldn't it be better to config for instance 8.8.8.8 as a secondary DNS server in the manual / DHCP setup? So when the NAS is down for whatever reason,. you're still be able to perform lookups?
You can, but you will then lose ad-blocking/local DNS resolution. If neither of those are important to you, using 8.8.8.8 as a secondary DNS server is great!
Thanks, I kinda got mine working. I can only access it directly on my nas, not the ip I set with the 2nd pihole container. I am using the current latest images though.. I'll check it again at some point, but how would you add unbound to this? I've got unbound setup on a VM with AdGuard, but I want to compare pihole to Adgaurd, with both running unbound, and keep the environment I prefer.
I haven't set up Unbound on a Synology NAS yet (hopefully have a video coming soon). I believe that it will work the same as other tutorials, but you'll have to connect to the NAS using the bridge network (just an assumption for now). Hopefully, I'll have a video soon!
Hi, thanks a lot for the tutorial. I have one question. I did everything except the bridge. I don't get what you need it for. If I ping my dns ip from the nas (ssh) I get a response. What is the bridge for? Again thanks !
The bridge is only needed for NAS to container communication. Meaning if you're going directly from the NAS to the container, you would use the bridge IP. If you're setting your router with the container as the DNS server, the NAS will go through the router so you won't need the bridge!
Great video good job! the problem i got with docker its that I never get the download to start :/ I can download/upload to/from my NAS but when I use Docker... nothing start then I got like an timeout error. Maybe its authorisations but I can't find any.
Hmm, that's weird. Do you know if DNS resolution is working properly (meaning did you change the DNS server on your NAS)? Also, are you using the default "docker hub" section or are you using something else?
Yes, but you wouldn't get the blocking capabilities of Pi-Hole unless you have a redundant Pi-Hole DNS server. You also run the risk of having certain queries run through the non-Pi-Hole DNS server due to the Pi-Hole server being overloaded. Overall, you are correct, and if having ads blocked 100% of the time is not necessary, then you're good in using a backup DNS server like Google. However, if you want DNS blocking always or are using Pi-Hole as a local DNS server, you probably want to spring for a Raspberry Pi or run a secondary instance on a different server as well.
Thanks for the tutorial, any info on how to add unbound to the pi-hole docker container? I already have pi-hole running on a raspbery pi with unbound but wanted to add a second pi-hole instance with unbound using my synology DSM6. so I can have redundancy incase 1 goes down I have the other. Any info would be awesome.
What do you mean that every environment is empty? When you configured the image, there should have been a bunch of pre-filled entries? Hopefully these written instructions will help: www.wundertech.net/how-to-setup-pi-hole-on-a-synology-nas-two-methods/
@@dkone78 This is old and I apologize - I wasn't notified that you commented back. If the environment section is totally blank, I would delete the image and re-download it. Hopefully, that will fix it!
Thanks for this video. How do I change the default webpassword shown @ 3:22 ? Isn't 8.8.8.8 Google's own default DNS server? Shouldn't something else be chosen, or it just doesn't matter? Has the "bug" been fixed since 5.1 was released? A newer version?... or is it still an issue? On a side note, this may be the first video I've ever had to actually slow down to 0.75 instead of speed up to 1.25....LOL
Thanks for watching! The value that you put in that field (where I have password) is what will be the password. WEBPASSWORD needs to stay but "password" can be changed to whatever you'd like to use. The way that Pi-Hole works is it filters the traffic and blocks the web request if required, and if not, forwards it to an upstream DNS provider. In my case, I'm using Google (8.8.8.8), but you can use whatever you'd like here! I need to test the new version of Pi-Hole and will get back to you. It didn't work the last time I tried but I'm sure a new version has been released. Yes, I do tend to go fast :-) My feelings are that long, drawn out videos are a hindrance to users and it's better to get the information out as briefly as I can. That's why I include written instructions in the description of every video. Thank you for watching and if you need anything else, please let me know!
Can you do a video about combining the macvlan method with a keepalived container? That way you can have redundant dns while keeping most of the logs on a single pihole instance. I can't really find any information on how to set it up, is it even possible?
Do you mean have redundant DNS servers on the same NAS? Unfortunately, you will need to use two different devices for redundancy purposes, but I will add this to my list and do a little more research on seeing if it's possible. Thank you for watching!
@@WunderTechTutorials no, one physical raspi with keepalived and one pihole docker install on a synology with keepalived as well (there is a docker for keepalived as well but I don't know if what I want is possible) Thanks for looking into this!
Great Video! Thank you for this :) .... just a question, I have 2 different ISP connected to my DS920+, I've already setup the Pi-hole for the ISP connected in LAN1 same goes with the ISP connected in LAN2, for the LAN1 everything is working as expected but unfortunately for the LAN2 I'm getting an error in Pi-Hole diagnosis tab "DNSMASQ_CONFIG.......FTL failed to start due to failed to create listening socket for port 53: Address already in use" I believed it is because I'm already running my Pi-Hole in LAN1 and the port 53 is already in used and by the time I setup the Pi-hole in LAN2 it gives me that error. What is the best way to fix this? TIA
Unfortunately, you won't be able to set up two different instances on your NAS. You technically can, but then you'll have to use a different DNS port (as your NAS only has one port 53). The other option is to set up two separate macvlan networks and do it that way, but truthfully, I'd really recommend buying a cheap Raspberry Pi and hosting the second instance on there. It's cheap (you can buy a Pi Zero), easy to set up, and will provide redundancy in case your NAS shuts down.
@@WunderTechTutorials yeah you're right that's what I thought. I think I'll go on your recommendation buying Pi Zero instead. Thanks a lot.... really appreciate it :)
Followed the initial portion of this guide and configured my router to look at my Synology IP address for DNS and everything freaks out. Couldn't connect to my router, synology or the pihole webport to sort it out. Eventually figured out my router changed it's IP address in order to prevent a conflict. Spent 2 hours trying to get a grip on what went wrong. Then tried again with the same results. Will be looking at other guides that explain more in detail what is happening when I set things up.
Did you change the DNS server on your router? DNS is for domain name lookups, meaning that it will not impact IP addresses. So if you have a local device on your network that's IP address 192.168.1.10, changing the DNS IP address on your router will not impact that. It could stop domain name resolution (if the router can't access the NAS, for example), but that would impact external network traffic. The only way that you can run into IP address issues (that I can think of) is if you changed Pi-hole to be your DHCP server, or accidently changed the IP address of your router. Either way, I'm sorry to hear you're running into issues. If there's anything I can answer to help, just let me know.
Generally, the easiest way that I find to do it is to download the latest Pi-Hole image, stop the Pi-Hole container and then right-click it and duplicate settings. It will then create a new container with the same settings (and new image) where you can start it up and test to make sure everything is still working as expected. If it is, feel free to delete the old container. People have suggested that you can do it by "clearing" the existing container, but that does NOT work for me. I lose all my settings that way. Hopefully this helps!
I followed you steps exactly, DSM7, there is something hanging it up because of "Port Settins" in the "Advanced Settings" configuration. Any suggestions?
@@boca812 Did you have this working on DSM 6 OK or is it since upgrading to DSM 7. Fingers crossed you sort it out but delaying my update to 7 in case I have issues.
@@dan4493 I never had 6, only 7. I did get it going. I uninstalled and deleted everything, even the file folders. When I started over I didn't have the port problems like I had previously while doing the exact same thing. Thanks for your help. I'm now trying to get Alexa to work with Audio Station, using Snologys instructions. But that's not working.
When I used the non macvlan option, and went to change the dns settings on my router it said there was a conflict on the ip subnet, which I'm guessing is because my synology has a reserved ip which the pihole is using as well? What do I need to do?
fixed it with the option 1 approach (non macvlan). Windows was using the original DNS. Open command prompt in windows 10, type ipconfig /all. See what DNS it is using. If its not your pihole address then type ipconfig /flushdns. run ipconfig again. You should now see the new dns. Happy days...
@@phillipmarszal8475 The tutorial is still relevant, but there have been a few issues with the recent Pi-hole images. Not that this is ideal, but can you try and download an older version to see if it works properly?
It works perfectly, but do you know how to add another subnet? Upstream router eth1: 192.168.1.0/24 eth2: 192.168.2.0/24 Synology: 192.168.1.4 Pihole: ph_network: (subnet: 192.168.1.0/24, ip range: 192.168.1.254/32, gw: 192.168.1.1), ph_bridge: (subnet: 192.168.22.0/24, ip range: 192.168.22.2/32, gw: 192.168.22.1) Now, IP within 192.168.1.x is able to resolve domain via Pihole but not 192.168.2.0/24
If you're trying to add a different subnet, you're going to have to add a static route. This is done on the router and informs the subnet what gateway to go through to find the devices on the other subnet. There is a section on this page titled "VERY IMPORTANT INFORMATION". This shows how you can create a static route, but you will have to substitute your router's information! www.wundertech.net/backup-your-synology-nas-using-hyper-backup-to-a-raspberry-pi-on-site-or-off-site/
Thanks for the video it was really helpful seems to be all working fine however next step is to configure my router for all clients to this server. Just have one client manually using this server to test it out first. I have used version 5.1 as in your video as I was not sure if the 'newest version' on the drop down list works ok? Also when you update the version of the image do you have to change all your settings again?
The new version should be working properly now, but 5.1 is fine as well. As long as you properly mapped the volumes (this is where all your personal settings are stored), everything should be good.
@@WunderTechTutorials Thanks for the info will give it a go but doubt there is much of a change from this version. Also when you created the conf file with name server does that mean that whatever is in that file is the DNS server that will be used irrespective of what DNS service you tick on the actual pi-hole DNS settings page? I am not sure if the conf file will always be used as the DNS server irrespective of the pi-hole settings?
@@dan4493 No, that is just a file that needs to be created to get the container to run (unfortunately). People run into tons of issues without that, but whatever exists in Pi-hole should be respected.
@@WunderTechTutorials Ah ok thanks for confirming this. Do you know if there are any issues with running this with DSM 7 - not upgrading just in case at the moment
Maybe you have the synology dns server running at same time with Pi-hole. If this is your case, you have to stop running synology dns server, and it should work fine.
The password isnt working for me. I added a new environment variable called WEBPASSWORD but when I enter the password in the webinterface it tells me that I entered a false password
Did you enter that environment variable BEFORE The container was created? If not, you will have to recreate the container with that variable. There are other ways of doing it, but truthfully, they're all more time consuming than just recreating the container.
@@flayandpray4333 Hmm that's strange. Have you tried recreating the container to see if it works? Basically, if the environment variable isn't properly configured, it will generate a random password (which can be found through the terminal, but it will be a bit of a pain).
@@WunderTechTutorials Yes I already tried that one. I even used ssh to connect to my nas to use the random generated password but with this method i ve got the problem that the webinterface doesnt accept it aswell
@@flayandpray4333 Do you know what version of Pi-hole you're running? Is it specifically stating that the password is wrong? I've had issues logging in in the past, but it was related to the version of Pi-hole I was running.
Maybe you have the synology dns server running at same time with Pi-hole. If this is your case, you have to stop running synology dns server, and it should work fine.
The videos are in addition to the written instructions (which is why it's fast). If you're interested in viewing those, here they are: www.wundertech.net/how-to-setup-pi-hole-on-a-synology-nas-two-methods/
Awesome tutorial. Once I dig up my old raspberry pi, I'm going to set both up for the dual method. Thanks a ton sir.
Your tutorial helped a lot! Thank you
I was so lost, thank you for explaining all of this
Glad that it helped, thanks for watching!
Great video, straight to the point. :) Hint for my future self: for IPv6 add the environment variable "ServerIPv6" and as value the IPv6 of the Synology or Macvlan. In the router configure the DNS for both IPv4 and IPv6.
Thank you. Great video, great notes!
I'm glad it helped, thank you for watching!
Great video! it worked flawlessly.
Glad to hear it helped, thanks for watching!
great tutorial, thanks!
If only I could like a video more than once...
I already own a raspberry pi that I was using exclusively as a pihole, but the idea of consolidating into an already existing piece of hardware on my network seems so much more efficient. ☑
My OCD thanks you sire!
Thanks so much! I appreciate the kind words!
Thanks so much indeed - really great guide. Subbing now.
Thanks a lot! I appreciate the support.
very helpfull, thanks man :)
Really needed for this video, cause of Synology strange docker app! Thanks!
I can't understand only 1 thing, why do you use /32 mask and why its working with /24 subnet?
The /32 subnet mask is used for an individual IP address. So basically, we are reserving that one IP address so that it doesn't change.
Let me know if you have any other questions or need clarification!
I asked you to look into a way to donate months ago, and I totally missed the Thanks button. So, here goes: Thanks!
Thank you so much for your generous donation!
Merci beaucoup pour cette excellente vidéo
Thank you for watching!
Thank you
Great vid
Thank you so much. That helped figure out why it diden't work befour.
I'm glad to hear it helped, thanks for watching!
Thanks a lot, my first time trying pihole, now time to try it and see if I keep it or remove it
Thank you for watching! Glad it helped!
Hello @WunderTech, Could you please do an updated version for the DSM 7.1? Thank you so much
First off. Great video. I was excited to try and install this and give it a shot.
EDIT: I found the problem. It was how I pointed my win 10 to the Pihole. I'm not sure WHY the different method worked but if I follow the instructions of the website it didn't work BUT I saw another youtube video that showed a separate method of adding a DNS and that one worked no problem. Pihole is up and running and I can connect to everything with no problem. Ah well. Thank you for the great videos. I look forward to getting an actual raspberry pi to run my second pihole on.
I'm glad to hear that you were able to get it working! Thanks a lot for watching!
@@WunderTechTutorials I figured out why it didn't work when I first changed my DNS. I was watching your pi hole tutorial using the Rasp Pi and in that tutorial, you showed how to flush and register your DNS on Win 10. I never knew that was a thing. Maybe add that to all the written instructions? Anytime I switch my DNS now I have no problems and don't have to restart my comp over and over to get it to work. LoL. I really do love what you do. Thank you for taking the time in making these. Its been fun,
@@kaput808 Hahaha sorry for not mentioning that earlier! Yes, that's a very important part, but only if you're changing the DNS on the local machine. If you're doing it on the router, it's not necessary. Either way, glad you got it to work and thanks so much for watching!
IMO the easiest and best videomanual for doing this. Is there a way of updating pihole in an easy way?
Thanks for watching! Yes, this video should help! th-cam.com/video/E0Q4xVn0gRc/w-d-xo.html&ab_channel=WunderTech
Awesome vid!
If I do need to reboot my Synology, could I configure a backup DNS (say Google or Cloudflare) as a failover/redundancy?
Thanks again!
Thank you! You can, but just keep in mind that if any DNS requests hit that DNS server, you will not have ad-blocking. If you're okay with that, then this is a great option!
To avoid HA issues, wouldn't it be better to config for instance 8.8.8.8 as a secondary DNS server in the manual / DHCP setup? So when the NAS is down for whatever reason,. you're still be able to perform lookups?
You can, but you will then lose ad-blocking/local DNS resolution. If neither of those are important to you, using 8.8.8.8 as a secondary DNS server is great!
Thanks, I kinda got mine working. I can only access it directly on my nas, not the ip I set with the 2nd pihole container. I am using the current latest images though.. I'll check it again at some point, but how would you add unbound to this?
I've got unbound setup on a VM with AdGuard, but I want to compare pihole to Adgaurd, with both running unbound, and keep the environment I prefer.
I haven't set up Unbound on a Synology NAS yet (hopefully have a video coming soon). I believe that it will work the same as other tutorials, but you'll have to connect to the NAS using the bridge network (just an assumption for now). Hopefully, I'll have a video soon!
great video. Any chance of one that shows how tp update pihole to a new version. I hate having to start from scratch every time. Thank you!
Thanks! This is how I normally update: th-cam.com/video/bTb7889qNxQ/w-d-xo.html
@@WunderTechTutorials will give it a try next time there's an update.
For me it didn't work, when I enter the docker console it says lighttpd stopped and falls into a loop. Maybe some idea what I am doing wrong?
Hi, thanks a lot for the tutorial. I have one question. I did everything except the bridge. I don't get what you need it for. If I ping my dns ip from the nas (ssh) I get a response. What is the bridge for? Again thanks !
The bridge is only needed for NAS to container communication. Meaning if you're going directly from the NAS to the container, you would use the bridge IP. If you're setting your router with the container as the DNS server, the NAS will go through the router so you won't need the bridge!
Can anyone explain how to make sure I substitute the correct subnet/mask when setting up with the bridge (option 2)?
What is the IP address of your router? That will determine which you should use.
Would doing the method #1 installation cause any issues if you are also using your Synology NAS to host a website? Thank you for your time.
No, port 443 isn't used which is used for HTTPS so you should be good!
Great video good job! the problem i got with docker its that I never get the download to start :/ I can download/upload to/from my NAS but when I use Docker... nothing start then I got like an timeout error. Maybe its authorisations but I can't find any.
Hmm, that's weird. Do you know if DNS resolution is working properly (meaning did you change the DNS server on your NAS)? Also, are you using the default "docker hub" section or are you using something else?
Wouldn’t you still be able to resolve DNS if your synology is down by using a secondary dns?
Yes, but you wouldn't get the blocking capabilities of Pi-Hole unless you have a redundant Pi-Hole DNS server. You also run the risk of having certain queries run through the non-Pi-Hole DNS server due to the Pi-Hole server being overloaded.
Overall, you are correct, and if having ads blocked 100% of the time is not necessary, then you're good in using a backup DNS server like Google. However, if you want DNS blocking always or are using Pi-Hole as a local DNS server, you probably want to spring for a Raspberry Pi or run a secondary instance on a different server as well.
Thanks for the tutorial, any info on how to add unbound to the pi-hole docker container? I already have pi-hole running on a raspbery pi with unbound but wanted to add a second pi-hole instance with unbound using my synology DSM6. so I can have redundancy incase 1 goes down I have the other. Any info would be awesome.
I've been meaning to set up Unbound in a container but haven't had a chance. Hopefully soon!
@@WunderTechTutorials that would be awesome. I look forward to it. Thanks for your reply. You have a great channel.
Thanks for great tutorial but I don't understund why on the my pihole image task environment is empy?Any idea?
What do you mean that every environment is empty? When you configured the image, there should have been a bunch of pre-filled entries?
Hopefully these written instructions will help: www.wundertech.net/how-to-setup-pi-hole-on-a-synology-nas-two-methods/
my Environment section is empty and I don't understand the reason, zero pre-filled entries, I have try to reinstall pihole imaze but has change.
@@dkone78 This is old and I apologize - I wasn't notified that you commented back.
If the environment section is totally blank, I would delete the image and re-download it. Hopefully, that will fix it!
Do you need both Pi Hole Docker containers running ? or can you just run the one and delete the first once the MacVlan is created
Those are just two different options, you only need to install one of them. Either will work, so use whichever one you think is best!
Thanks for this video. How do I change the default webpassword shown @ 3:22 ?
Isn't 8.8.8.8 Google's own default DNS server? Shouldn't something else be chosen, or it just doesn't matter?
Has the "bug" been fixed since 5.1 was released? A newer version?... or is it still an issue?
On a side note, this may be the first video I've ever had to actually slow down to 0.75 instead of speed up to 1.25....LOL
Thanks for watching!
The value that you put in that field (where I have password) is what will be the password. WEBPASSWORD needs to stay but "password" can be changed to whatever you'd like to use.
The way that Pi-Hole works is it filters the traffic and blocks the web request if required, and if not, forwards it to an upstream DNS provider. In my case, I'm using Google (8.8.8.8), but you can use whatever you'd like here!
I need to test the new version of Pi-Hole and will get back to you. It didn't work the last time I tried but I'm sure a new version has been released.
Yes, I do tend to go fast :-) My feelings are that long, drawn out videos are a hindrance to users and it's better to get the information out as briefly as I can. That's why I include written instructions in the description of every video.
Thank you for watching and if you need anything else, please let me know!
Can you do a video about combining the macvlan method with a keepalived container? That way you can have redundant dns while keeping most of the logs on a single pihole instance. I can't really find any information on how to set it up, is it even possible?
Do you mean have redundant DNS servers on the same NAS? Unfortunately, you will need to use two different devices for redundancy purposes, but I will add this to my list and do a little more research on seeing if it's possible. Thank you for watching!
@@WunderTechTutorials no, one physical raspi with keepalived and one pihole docker install on a synology with keepalived as well (there is a docker for keepalived as well but I don't know if what I want is possible)
Thanks for looking into this!
@@sitte24 I got it - let me see if I can come up with anything!
Great Video! Thank you for this :) .... just a question, I have 2 different ISP connected to my DS920+, I've already setup the Pi-hole for the ISP connected in LAN1 same goes with the ISP connected in LAN2, for the LAN1 everything is working as expected but unfortunately for the LAN2 I'm getting an error in Pi-Hole diagnosis tab "DNSMASQ_CONFIG.......FTL failed to start due to failed to create listening socket for port 53: Address already in use" I believed it is because I'm already running my Pi-Hole in LAN1 and the port 53 is already in used and by the time I setup the Pi-hole in LAN2 it gives me that error. What is the best way to fix this? TIA
Unfortunately, you won't be able to set up two different instances on your NAS. You technically can, but then you'll have to use a different DNS port (as your NAS only has one port 53). The other option is to set up two separate macvlan networks and do it that way, but truthfully, I'd really recommend buying a cheap Raspberry Pi and hosting the second instance on there. It's cheap (you can buy a Pi Zero), easy to set up, and will provide redundancy in case your NAS shuts down.
@@WunderTechTutorials yeah you're right that's what I thought. I think I'll go on your recommendation buying Pi Zero instead. Thanks a lot.... really appreciate it :)
I'm a bit confused, when confiuring the DNS settings on the router do i give it my Synology IP address for a primary DNS IP?
It depends on the option you used. If you used the macvlan setup, it'll be that IP address. If you used the host, it's the Synology NAS.
Followed the initial portion of this guide and configured my router to look at my Synology IP address for DNS and everything freaks out. Couldn't connect to my router, synology or the pihole webport to sort it out. Eventually figured out my router changed it's IP address in order to prevent a conflict. Spent 2 hours trying to get a grip on what went wrong. Then tried again with the same results. Will be looking at other guides that explain more in detail what is happening when I set things up.
Did you change the DNS server on your router? DNS is for domain name lookups, meaning that it will not impact IP addresses. So if you have a local device on your network that's IP address 192.168.1.10, changing the DNS IP address on your router will not impact that. It could stop domain name resolution (if the router can't access the NAS, for example), but that would impact external network traffic. The only way that you can run into IP address issues (that I can think of) is if you changed Pi-hole to be your DHCP server, or accidently changed the IP address of your router.
Either way, I'm sorry to hear you're running into issues. If there's anything I can answer to help, just let me know.
How do you update pi hole running on docker in Synology?
Generally, the easiest way that I find to do it is to download the latest Pi-Hole image, stop the Pi-Hole container and then right-click it and duplicate settings. It will then create a new container with the same settings (and new image) where you can start it up and test to make sure everything is still working as expected. If it is, feel free to delete the old container.
People have suggested that you can do it by "clearing" the existing container, but that does NOT work for me. I lose all my settings that way.
Hopefully this helps!
@@WunderTechTutorials Works well! Thanks!
@@MickH7400 Awesome! Thanks for watching!
Can anyone confirm if this now works with the newest version? I don’t see any mention in the written instructions…
When you say "works with the newest version", what exactly do you mean? DSM 7?
I have synology NAS 220j and it's not compatible with docker. Is there any workaround for that?
I unfortunately don't think there is at this point :(
I followed you steps exactly, DSM7, there is something hanging it up because of "Port Settins" in the "Advanced Settings" configuration. Any suggestions?
When are you getting that error message?
@@WunderTechTutorials When you go through to do the intial set up. It won't let me APPLY the final set up
@@boca812 Did you have this working on DSM 6 OK or is it since upgrading to DSM 7. Fingers crossed you sort it out but delaying my update to 7 in case I have issues.
@@dan4493 I never had 6, only 7. I did get it going. I uninstalled and deleted everything, even the file folders. When I started over I didn't have the port problems like I had previously while doing the exact same thing. Thanks for your help. I'm now trying to get Alexa to work with Audio Station, using Snologys instructions. But that's not working.
@@boca812 ah ok no worries. I’ll bear your method in mind if I have issues when upgrading to DSM however I haven’t had any port problems so far.
When I used the non macvlan option, and went to change the dns settings on my router it said there was a conflict on the ip subnet, which I'm guessing is because my synology has a reserved ip which the pihole is using as well? What do I need to do?
It shouldn't have any conflicts. When you say that the error is pointing to a subnet issue, is your NAS/router on the same subnet?
fixed it with the option 1 approach (non macvlan). Windows was using the original DNS. Open command prompt in windows 10, type ipconfig /all. See what DNS it is using. If its not your pihole address then type ipconfig /flushdns. run ipconfig again. You should now see the new dns. Happy days...
Can you run this pihole on the latest version yet? or still 5.1v?
Yes! The v5.1 issue was resolved in a later version.
is there an alternative to docker, my synology nas is not suitable for docker.
Unfortunately, not that I know of. I have always used Docker to get Pi-hole working on my NAS.
Followed your tutorial to a T and cannot access the pihole UI, not sure why? Is tutorial still current?
My network scan sees pihole assigned ip, however, scan say no open ports.
Pinging also doesn’t return anything (probably cause port issue but don’t know enough about networking)
@@phillipmarszal8475 The tutorial is still relevant, but there have been a few issues with the recent Pi-hole images. Not that this is ideal, but can you try and download an older version to see if it works properly?
not sure if this vid gonna get a response, but i got to the terminal console.... now im lost. how you get to that?
When you say you got to the terminal, do you mean that you were able to SSH into your NAS?
It works perfectly, but do you know how to add another subnet?
Upstream router
eth1: 192.168.1.0/24
eth2: 192.168.2.0/24
Synology: 192.168.1.4
Pihole: ph_network: (subnet: 192.168.1.0/24, ip range: 192.168.1.254/32, gw: 192.168.1.1), ph_bridge: (subnet: 192.168.22.0/24, ip range: 192.168.22.2/32, gw: 192.168.22.1)
Now, IP within 192.168.1.x is able to resolve domain via Pihole but not 192.168.2.0/24
If you're trying to add a different subnet, you're going to have to add a static route. This is done on the router and informs the subnet what gateway to go through to find the devices on the other subnet.
There is a section on this page titled "VERY IMPORTANT INFORMATION". This shows how you can create a static route, but you will have to substitute your router's information!
www.wundertech.net/backup-your-synology-nas-using-hyper-backup-to-a-raspberry-pi-on-site-or-off-site/
Thanks for the video it was really helpful seems to be all working fine however next step is to configure my router for all clients to this server. Just have one client manually using this server to test it out first. I have used version 5.1 as in your video as I was not sure if the 'newest version' on the drop down list works ok? Also when you update the version of the image do you have to change all your settings again?
The new version should be working properly now, but 5.1 is fine as well. As long as you properly mapped the volumes (this is where all your personal settings are stored), everything should be good.
@@WunderTechTutorials Thanks for the info will give it a go but doubt there is much of a change from this version.
Also when you created the conf file with name server does that mean that whatever is in that file is the DNS server that will be used irrespective of what DNS service you tick on the actual pi-hole DNS settings page? I am not sure if the conf file will always be used as the DNS server irrespective of the pi-hole settings?
@@dan4493 No, that is just a file that needs to be created to get the container to run (unfortunately). People run into tons of issues without that, but whatever exists in Pi-hole should be respected.
@@WunderTechTutorials Ah ok thanks for confirming this. Do you know if there are any issues with running this with DSM 7 - not upgrading just in case at the moment
@@dan4493 No issues as far as I know!
how do i update?
Here you go! www.wundertech.net/how-to-update-docker-containers-on-a-synology-nas
It doesnt work for me I've tried multiple times doing exactly what you do and pihole keeps crashing and having to restart itself over and over
Are there any error messages in the log?
@@WunderTechTutorials no errors but I gave up and just spun up a vm and installed pi-hole on it instead. Thank you for replying and helping people.
Maybe you have the synology dns server running at same time with Pi-hole. If this is your case, you have to stop running synology dns server, and it should work fine.
The password isnt working for me. I added a new environment variable called WEBPASSWORD but when I enter the password in the webinterface it tells me that I entered a false password
Did you enter that environment variable BEFORE The container was created? If not, you will have to recreate the container with that variable. There are other ways of doing it, but truthfully, they're all more time consuming than just recreating the container.
@@WunderTechTutorials Yes I entered the variable before the container was created
@@flayandpray4333 Hmm that's strange. Have you tried recreating the container to see if it works? Basically, if the environment variable isn't properly configured, it will generate a random password (which can be found through the terminal, but it will be a bit of a pain).
@@WunderTechTutorials Yes I already tried that one.
I even used ssh to connect to my nas to use the random generated password but with this method i ve got the problem that the webinterface doesnt accept it aswell
@@flayandpray4333 Do you know what version of Pi-hole you're running? Is it specifically stating that the password is wrong? I've had issues logging in in the past, but it was related to the version of Pi-hole I was running.
The username has to be root in newer versions.
Why did u delete my comment?
I didn't delete any comments. If you added a URL or command of some sort, TH-cam automatically removes it.
Pihole keeps crashing, same results from every tutorial
Are you getting any errors in the Docker logs?
Maybe you have the synology dns server running at same time with Pi-hole. If this is your case, you have to stop running synology dns server, and it should work fine.
Damn it’s so ducking complicated.
all goes toooo fast
The videos are in addition to the written instructions (which is why it's fast). If you're interested in viewing those, here they are: www.wundertech.net/how-to-setup-pi-hole-on-a-synology-nas-two-methods/