FYI ALL : as of June 2022 the Docker interface has changed slightly. Instead of all the settings being under advanced settings, they now are in separate windows, prompted by the next button. Its all still there, just in a different setup. Since I am new to all this, when I went to reinstall pihole, I found it confusing as it did not follow the video exactly. Since I don't really understand what is happening I follow the video by rote and it threw me off.
Hi J P, Thanks for your comment on the changes to the Docker interface. I've pinned it to the top of the comments section so hopefully it gets others attention as well. I'll also look at possibly creating a new video tutorial with the new Docker interface being highlighted. Thanks again!!
@@digital_aloha thanks again. Again this video is super helpful. I think I had to set my router DNS to the pihole IP to get it to work as well. Prob obvious to experienced users.
@@Jp421JP, You're welcome. I'm happy to hear that you've been referring back to this video to get your pihole set up and glad you got everything working if your network.
@@digital_aloha This threw me off a little too. It might help if you included a summary of the Docker container configuration in the description of the video.
I know this video is 3 years old and the interface/software has a changed a bit but this is the only video/article I found that actually got Pi-hole working for me. Thank you for the detailed video and a to the point video! Cheers!
Aloha from North Shore and mahalo for the tutorial. Been wanting to try this out on my DS1817+ for a while but wasn't sure if it'd break anything. Also, nice to see a fellow Islander on YT with tech content. Subbed and looking forward to more.
Aloha jamauai (from rainy Hilo) and mahalo for subscribing. Hope the video gets you going with Pi-hole on your DS1817+. More videos coming and nice to connect with another UA-camr in the state!!
I already had a Pihole running on a PI4b along with my PVR, that sends its queries via a stubby instance so DOT, however, occasionally as with all things it fails. Replacing my dying 416j with a ds920+ gave me the opportunity to have a second instance running for redundancy so thanks for the tutorial. I did find the NAS would not 'see' the Pihole address behind the macvlan, in the end I've put in a static route so it goes via the router otherwise it is working albeit only a fraction of the traffic is going through it 3k Vs 500K I suspect the bare metal one responds faster so is preferred, I'll wait until it is just me in the house and disable that one to make 100% sure I have really redundancy. EDIT - of course the address I need for the NAS is the bridge address not the actual pihole address as seen by the rest of the lan.
Hi IMBlakeley, You've been busy going through many of my videos. Thanks for leaving feedback and happy to hear you you've got your Pihole redundancy setup. I should try that out in my network. 🤔
After setting up Pi-hole per your instructions all worked well except that Adlists could not be updated. I kept getting " [✗] List download failed: no cached list available" in the Pihole container log files. In the Pihole GUI, the error message was "connection refused". The problem turned out to be that the Synology firewall was not allowing the pihole-bridge through. In your example, 192.168.82.2 must be allowed through the Synology firewall. Now all works great. Thanks for the excellent tutorial.
can you please specify again, which ip adress is to set in the correct spot? i'm using 192.168.155.1 as for my fritz!box and set up the macvlan 192.168.154.1 ... now i'm using 192.168.155.76 for the pihole and 192.168.155.77 for the unbound-pihole within the fritz!box ... as for the dns server adresses: which ones do i have to put in my NAS and my fritz!box to tunnel everything of the getgo? other than that thanks a lot for your videos, great help!!
I have to thank you for this wonderful tutorial. I have a question regarding the dnsmasq.d. I setup dnsmasq in my edgeRouter and I am wondering if it will have conflict when running another on the Docker Pi Hole that I setup in the Synology? If there will be a conflict, can I setup Pi Hole without the dnsmasq? Thanks.
Hi Peter, You're welcome and thanks for your feedback. Regarding your dnsmasq.d question actually Pi-hole will run dnsmasq because it is what Pi-hole uses for it's DNS/DHCP server. In the video the /etc/dnsmasq.d mount point is actually a physical location where you could add in custom configurations if needed, but even if it weren't created Pi-hole will run dnsmasq. There shouldn't be any conflicts with dnsmasq running on your edgeRouter and you just need to point your client to your Pi-hole to make use of it. Good luck with your setup!!
@oppailover3087 I actually cover setting up unbound with pi-hole in a couple of my videos, but I think this one would be the best to follow -> ua-cam.com/video/nOlx10aRZjk/v-deo.html. Hope this helps? Best of luck in your setup!!
I have successfuly used Pi hole as per your video. However, since the NAS controls the DNS, if it is down, like loss of power or recently Synology had an update that basically broke everything until you updated all the aps, its is frustrating. Is there a way to have it use an alternate DNS, if the NAS is off? It happens enough so that it is a problem.
@Jp421JP What I do in my setup is add Pi-hole as the first DNS server, then add a secondary DNS server to the DHCP configuration as well. In my case I actually run a BIND server on my network, but you should be able to add Google's (8.8.8.8) or Cloudflare's (1.1.1.1) public DNS server. That setup should get you through the downtime of your Synology NAS and Pi-hole. Hope that helps?
With the recent change from Docker to Container manger, Pihole does not seem to be blocking as much as much it used to. It used to block everything well, now ads are getting through and it blocks only a small percent. I saw somewhere that with the change it affects the Bridge network somehow?
Hi thanx for the tutorial, it was clear. FYI i had an issue, PiHole container was in a infinite reboot loop Logs says that i had to change DNSMASQ_USER to root After that, it works fine.
I am stranding with the part phihole-bridge (in your video at 6:00). I get a warning during the setup that the gateway is used for another Docker network. I removed docker completely to start over again but I get the same warning. Any idea what's causing this issue?
Hi Cees, Not exactly sure the cause but what happens if you try another subnet? Maybe you are using a network that is already in use. Alternatively you could SSH into your Synology NAS and try to figure out what Docker networks are already created. The commands that I'd try are "sudo docker network ls" to list the existing Docker networks and "sudo docker network inspect " to display the network's information which should show its Subnet and Gateway. Hope this helps and good luck in trying to resolve the problem.
i already have my pihole with raspi and want to make another for pihole backup in case my raspi goes down. i already followed this guide and successfully deployed my pihole with macvlan and bridge network. but my pihole on synology cannot query anything if i try nslookup with its own bridge ip as a server? kindly help on this?
Great video! Can you also explain, how to get the setup running with IPv6, since I set my Piholes IP on the local DNS of my Fritz!Box for the whole network traffic?
Hi Eddy, Thanks for the compliment on the video!! I'll definitely look into setting up Pi-hole using IPv6 and will create a video when I do (can't promise you a quick turn around though). Good luck in trying to figure things out in the meantime!!
@@eddymouser4575 Great!! Glad you got things going. Did you setup IPv6 when setting up the Pi-hole container or after the container was created using the Web GUI? Just curious :)
Hii There! Great tutorial, very easy to follow and well explained :) unfortunately i cannot figure out why my pihole is not working. i made it to the part at 9:50 where you nslookup this does not work for me unfortunately and i followed your instructions 1:1 accept for that i had to use the local ip of (192.168.1.8 for my macvlan and 192.168.2.8 for my bridge network). am i missing something here? my router (that handles my dhcp) has the local ip of 192.168.1.1 and my subnet mask is 255.255.255.0. Thank you for any suggestions. would love to get this running finnaly :)
Hi _UNWIRE, Thanks for the compliment on the video. Much appreciated!! Regarding your setup, it sounds like you did everything properly!! One thing I can't tell is if you have the firewall enabled on your Synology NAS. If you do see if things work after disabling it. Also, just confirming that you did the nslookup command from a terminal NOT ssh'd into your Synology NAS. This should be done from a local terminal from your computer. Hope this helps a little. Best of luck in figuring out your setup.
@@digital_aloha Thank you so much! I've been trying to figure this out and I was finally able to make it work with your guide! It was the firewall of my nas that was causing it to not work... what do i have to allow in my firewall rules for it to still work without having to disable the firewall completely like i am doing currently? Thank you and have a delightful day :)
@@aintnoair Glad the info that was provided helped you out! Regarding the firewall I think you need to enable access to the custom bridge network and possibly the MacVLAN network as well. I have a video that covers setting up the Synology NAS firewall as it relates to Docker which I think will help you. Here is a link to the specific time within the video that I think is relevant in your setup -> ua-cam.com/video/-my0ilNnxR4/v-deo.html. Hope this helps and good luck in getting your firewall configured properly!!
Excellent video and thanks for your detailed explanation of each part of the setup. Thanks, The bridge network part solved my VPN issues in Synology. One minor question is that only one client (gateway IP of the bridge network) is displayed on the PipHole Admin page even though there are many devices that are using its service through VPN connection. Could it be possible to get a real device id and added to the client list of the Piphole?
Hi Hello World 9527, You're welcome and I'm happy that you got things working once the bridge network was configured. As for your question regarding only the gateway IP of the bridge network being displayed in the Pi-hole admin page, that is how the bridge network works. It won't pass individual client IP addresses directly to Pi-hole. On your LAN though your devices should show up individually because of the MacVLAN network that was setup. Hope this helps?
@anthonycoppet8788 You're welcome!! This is a limitation of MacVLAN networks and the reason why you'd need to setup a bridge network. The NAS would need to use the bridge network to access Pi-hole.
Is there any technical reason to define a custom bridge (in your example you used 192.168.82.0/24 subnet) vs the default bridge of 172.17.0.0/16? Isnt that what the docker0 interface is for to allow host to container connectivity? Or is the custom bridge subnet a preference?
Hi ArmBradPitt 😊, Great question... Other then isolating the Pi-hole container from the rest of the containers running on the default bridge network and making it simple to figure out the IP address assigned to the container (being that it is on a /32 subnet) there isn't a technical reason not to use the default bridge network.
I have not been able to find a tutorial like this for a container that has both pihole and unbound using docker on synology NAS. I've been searching for a week and can't seem to get em running individually (one container with pihole and another with unbound cause I can seem to get the networks to both for both containers), or one container with both pihole and unbound. Any suggestions?
Hi Vic, I was hoping this video would stand out in detailing the setup of running Pi-hole through Docker on a Synology NAS and thanks for the confirmation (although not specifically in what you are looking for with both Pi-hole and Unbound). I'll look to put together a video on using Unbound and Pi-hole on a Synology NAS some time in the future. Regarding your specific question, what I would suggest is using a MacVLAN network setup but instead of using a /32 network like in the video use a /30 network which would provide you 2 assignable IP addresses that you can assign to the Pi-hole and Unbound containers respectively. For example if I used 192.168.81.8/30 I'd be able to assign the Pi-hole container 192.168.81.9 and the Unbound container 192.168.81.10. At this point you should be able to point Pi-hole to Unbound as your upstream DNS provider. Hopefully that does the trick and let me know if this helps? I could use your feedback as I put together the Unbound video.
Hi Vic, You're welcome! And I did release a video on setting up Unbound with Pi-hole running on a Synology NAS. Check it out if you haven't already -> ua-cam.com/video/-546g1w_L3w/v-deo.html and good luck with the setup if you are still trying to get it going.
@mohamedfarhanal-subaey1670 Good question!! Technically you don't and you could just use the default bridge network to provide your Synology NAS access to Pi-hole. What I like about creating the pihole-bridge is that you specify the IP address that will be used so you don't have to inspect the Pi-hole Docker container to figure out what default bridge network IP address was assigned to it. I hope that makes sense?
@@digital_aloha thank you for your reply and I would like to ask you if you have time to make tutorial in detail in how to install pihole with unbound because I try to flow all your video regarding synology , pihole and unbound but I'm really confused. my device synology DS220+ DSM 7.1.1 Ram 6GB 16TB HDD it will be a grate helpful. best regards
@@mohamedfarhanal-subaey1670 Actually I did create a video that sets up both Pi-hole and Unbound using Git and docker-compose. See if that one works well for you. Here is the link -> ua-cam.com/video/nOlx10aRZjk/v-deo.html. Let me know how it goes!!
Hi Michel, I actually just ran through the setup of pi-hole on a new Synology NAS I've been working with and the local DNS seems to be working fine for me. I logged into the pi-hole web interface, went to Local DNS and added a DNS entry. I then changed my Macbook to use pi-hole for it's DNS server and the local DNS entry I added into pi-hole worked fine. In your situation are you able to resolve external hosts using pi-hole? Just curious if pi-hole is working properly to start off with. In any case good luck with your setup!!
@@digital_aloha Hey Aloha, thanks for the quick reply. Yeah, thats what I did but I didn't change the DNS server on my device/s. I changed in on the level of my router (Fritzbox). The queries are properly blocked by pi-hole on any device. However, any IP I try to entry in the pihole DNS records is later on not reachable / cannot be found with a DNS_PROBE_POSSIBLE error (including the one from pihole itself).
@@michelwork I did a little bit of research and others that have the same DNS_PROBE_POSSIBLE error seem to have some issue with the router they are using. I found this post on reddit from a person that uses a Fritzbox as well -> www.reddit.com/r/pihole/comments/n1wrdq/local_dns_not_working_after_domain_change/. Hopefully this helps you out? Good luck in trying to solve the issue.
Thanks for the great video, I have all macs on my network, and I use Unifi for DHCP. In your example, what IP address would I give my DHCP server on my Unifi to use the PIHole server
Hi Jack, You're welcome and I'm happy the video was helpful. Regarding your question the IP address you should assign your DHCP server is the MacVLAN IP address that you assigned to Pi-hole. Hope this helps and good luck in your setup!
As someone new to networking, this was well explained and detailed. Thank you. Could you explain why this installation is better than simply running pihole normally? With the macvlan and bridge? Perhaps you did, but I did not understand it.
Hi J P, You're welcome and thank you for your comment as well. I'm going to link to a UA-cam video (ua-cam.com/video/jaYlhE_EEyA/v-deo.html) and Pihole Discourse post (discourse.pi-hole.net/t/setup-on-synology-docker/18067) that really dive into why you should use a macvlan and bridge network when setting up Pihole on a Synology NAS if you want to deep dive into the topic. My short summary on why you should set things up this way, regarding the macvlan network, is it provides the Pihole docker container it's own separate IP address, removing the restrictions you would have if it were set up in the default bridge network that you get with Docker. This removes any chance of port conflicts (for example Pihole runs on port 53, but if you had port 53 used on your Synology NAS you'd have to map Pihole to a non-standard port number like 5353 for example). Regarding the bridge network this is required because your Synology NAS can't access the macvlan IP address directly so the bridge network gives the Synology NAS access to the Pihole container. Hopefully this makes sense and doesn't confuse things further?
@@digital_aloha Thanks, that was helpful. It did not cover the bridge network, as I saw. Why does synology need access to the pihole container via the bridge? While it runs on the synology, the NAS would seem to be "out of the loop" so to speak.
@@Jp421JP You're welcome!! The bridge network is needed because of the limitations of the MacVLAN network. The MacVLAN network within Docker is explicitly setup with isolation in mind (even from the host) and the work around is adding in the bridge between Docker and the Synology NAS itself. I think there are workarounds to get things working, but the bridge was the simplest option to use in my opinion.
@@digital_aloha Thanks for the explanation. This makes me think that I don't actually need the bridge configuration since I just point my router to the Pi-hole's MacVLAN IP address, while my Synology NAS already refers to my router to resolve domain names. Is that correct, or am I missing something here?
@@carlocabrera489 Hi Carlo, I believe that should work! If your Synology NAS doesn't need to refer to your Pi-hole directly then it should be fine and you won't need a bridge network setup. If you tried this let us know how it went!!
Great tutorial. The Bridge step was really hard to follow though because the print is too small to read and the video can't be zoomed because the res is too low. Hopefully I'll figure it out somehow. Update: It wasn't clear that it was "/24" for the subnet and "/32" for the range. Also, same problem with folder names. Way too small to get the spelling right.
Hi Michael, Thanks for the feedback on the video. I'll keep in mind that the text was pretty small and adjust accordingly in future videos. Unfortunately my equipment doesn't allow for higher resolution. Hopefully you got your Pi-hole setup configured and and working properly!!
Thank you very much for your great tutorials. Unfortunately in this one, when I try to create pihole-bridge network I receive an error saying that the Docker uses the same address for a gateway or the subnet overlaps with the existing Docker network in the address space. QUICK update - I have just realised that I created "homebridge container" that uses host mode. That's why I cannot create pihole-bridge network. I will try to find the solution.
Hi Marcin, You're welcome!! I'm happy to hear that my tutorials have been helpful to you. Hopefully you find (or have found) a solution to your issue where you couldn't create the pihole-bridge network!!??
Everything worked great except I can't get the blacklist to block anything? I have my test computer pointed to the pihole and netflix is blocked but still comes up. even says it blocked in pihole. Any help?
Hi Donnie, Sorry for the slow response. Hopefully you resolved the issue already but, if not, the problem is likely due to the blacklist rule for netflix not being assigned to a client group. To check on this, from the Pi-hole UI, go to Group Management -> Domains. Here you should see your netflix rule and what you want to do is look for the Group assignment column and assign the rule to a group, which should be the Default group if you haven't created other groups. Hope this helps and good luck to you in your setup.
Actually that is the web interface for my router. You'll want to log on to your router or DHCP server to get the details of what IP addresses are available. Hope that helps? Good luck to you in your set up!!
Great video. However, I'm running into an issue in where the FTL is failing to start. When I open the admin panel, the pi-hole diagnosis screens shows this error - "FTL failed to start due to failed to create listening socket for port 53: Permission denied". When I go to the docker logs themselves, I see three repeating lines. First line is "Starting pihole-FTL (no daemon) as pihole". 2nd line is "Stopping pihole-FTL". 3rd line is pihole-FTL: no process found. I do have a docker with pihole working using the same bridge as my Synology but I have that turned off. Thoughts?
I know this question is months old but I was just looking through the comments to help solve this as I just experienced the same issue. After several hours of troubleshooting I was able to figure out what caused this problem for me. It occurred after I restarted the NAS. It turns out that Unbound and pihole swapped IP addresses. Originally in my setup, Unbound's IP was 192.168.1.9 and Pihole's was 192.168.1.8. Subsequently Unbound was 192.168.1.8 and pihole was 192.168.1.9. This likely occurred because their IP addresses are not static, so whichever container started first got first dibs on IP address. As I am not sure how to make the addresses static, I kept the current settings and accordingly changed the IP settings on my router and other devices. Certainly making the addressed static would be ideal because this problem is likely to return the next time I restart the NAS.
Hello. Thanks for you tutorial. followed it, made a macvlan x.x10.25/32 made a bridge x.x11.25/32, set the server to the macvlan adress and started the container. could log in the pihole at x.x.10.25 but afaik pi hole would not filter anything. nslookup with x.x.11.25 would work fine but macvlan x.x.10.25 would not respond to the nslookup. if I point dns of my pc or router to x.x.11.25 nothing would happen. what would be dns server for the other clients? how to resolve macvlan nslookup not working? ping from my pc to macvlan x.x.10.25 would work fine.
Hi Neinhalt004, You're welcome and it looks like you are pretty close in your setup!! I think the issue is the IP address you are using and from what terminal you are running the nslookup command from. The macvlan x.x.10.25 IP address should be used by external clients and your router. The bridge x.x.11.25 IP address should only be used by your Synology NAS and services running on the NAS. Regarding your specific questions your PC, router and other clients should use the macvlan x.x.10.25 IP address (this should be the address that you would use the majority of the time). The bridge x.x.11.25 IP address should be set on your Synology NAS so it makes use of the pi-hole install and if you run services like a VPN server on your Synology NAS you'd use the bridge IP address there as well. Hope this helps? And good luck in getting everything working!!
@@digital_aloha thank you again for you kind answer. so external clients (or better yet vlan dns in router) receive the dns with the ip of the host (nas in my case), the host receives the internal container ip. is there a strategy in assinging the container ip's in the bridge? I have just setup a the bridge with whatever unused subnet (by other containers). I think the pi-hole would have worked with the setting sugested but I can't wrap my mind why would the nslookup would not work, when in your video it clearly did. did you made a route from host to container outside of this tutorial?
Hmm... Actually the external clients should use the macvlan IP address assigned to the pi-hole container. As for a strategy for assigning bridge IPs I'd just use an unused subnet or at least one that is different from the subnet that your NAS is on. Regarding any additional routes I actually didn't do anything more then what you saw in the video. Hope this helps?
@@digital_aloha It helped. I realise that the first setup was ok and the pihole was installed correctly. I did not pay attention when you tested nslookup outside of the nas host and that led me to the wrong conclusions. remade the container and put the macvlan in the primary dns of the vlan router settings. it all seems to work ok. thank you again for this great tutorial, you have a new suscriber.
> Finding a free address that can be used for a macvlan network I'm not sure how to do this; could you recommend any resources that go into more detail about this step?
Hi Dru, Hard to say what resource to provide you because it will be different for each situation. You should watch the "Setup The Docker MacVLAN Network" section of the video for hopefully some help. Essentially what you'll need to do is look at the configuration of your DHCP server and find an IP address that isn't used by any other system on your network. Then you'll use that IP address when creating your MacVLAN network. Hopefully that helps a little? Good luck to you!!
When I am trying to add "pihole-bridge" in docker network - I cannot add gateway "IPv4 gateway 192.168.1.254 is already in use by other Docker network." pihole-macvlan Gateway is also same
Hi Getur, The pihole-bridge network can't be the same as the pihole-macvlan network. That is probably why you are getting the error message. Also make sure the pihole-macvlan subnet that you set up is on the same network as your Synology NAS. Hope that makes sense? Good luck!!
Hi Connor, I like that idea!! I'll look into creating a video on updating Pi-hole (or maybe in general Docker containers) running on a Synology NAS. Thank you for the suggestion!!
@@digital_aloha Cool, thanks! I’ve had Pi-hole running on my NAS in a docker container for a while, I just can’t figure out the right way to update it… so I haven’t. And there’s tons of initial set up videos, just not for how to do updates. I think a video like that would help a lot of people out.
@@connor-betts I responded to another viewer regarding upgrading Pi-hole (and Unbound for that specific viewer) and I'm basically cutting and pasting my response here. Hopefully this helps... Still planning a video on upgrading Docker containers running on a Synology NAS though. 😀 1. Go to Docker within DSM and bring up Registry. 2. Search for Pihole and click Download to download the latest image. This will replace the image that you currently have downloaded. 3. Go to Container and stop the Pihole container. 4. After the container is stopped click on Action and Reset. This will give you a warning that all data will be lost on reset, but that is fine because of the volumes you setup earlier. Click Yes. 5. After the reset is completed click Action and Start which should bring up the container using the updated image. Good luck!!
Hi tomski182, I've been trying to figure out why you would need to run the Pi-hole container as a privileged container, but I can't find anything. All of my Pi-hole installs don't require a privileged container and I've done a bunch of installs. Maybe you did some tweak to your Docker installation at some point? Sorry I can't be of much help on this. Good luck in finding a solution!!
I don't have a video that automates setting up just Pi-hole, but if you want to include Unbound in your setup you could try the setup from this video -> ua-cam.com/video/nOlx10aRZjk/v-deo.html.
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.
I have a problem.when I key nslookup,server is 9:05 DNS ip.then,youtube.com .The reason is I used virtual machine?IF only macvlan one IP ,just don't create macvlan bridge and change DNS, it has internet.Then,I want macvlan two IP~
I would double check what IP address was assigned to the Pi-hole container on the MacVLAN network. To do this SSH into your Synology NAS and run `sudo docker container inspect pihole` (or the name you gave your Pi-hole container) and confirm the IP Address. Then try the nslookup command using that IP address. Hope this helps? Good luck to you!!
FYI ALL : as of June 2022 the Docker interface has changed slightly. Instead of all the settings being under advanced settings, they now are in separate windows, prompted by the next button. Its all still there, just in a different setup. Since I am new to all this, when I went to reinstall pihole, I found it confusing as it did not follow the video exactly. Since I don't really understand what is happening I follow the video by rote and it threw me off.
Hi J P, Thanks for your comment on the changes to the Docker interface. I've pinned it to the top of the comments section so hopefully it gets others attention as well. I'll also look at possibly creating a new video tutorial with the new Docker interface being highlighted. Thanks again!!
@@digital_aloha thanks again. Again this video is super helpful. I think I had to set my router DNS to the pihole IP to get it to work as well. Prob obvious to experienced users.
@@Jp421JP, You're welcome. I'm happy to hear that you've been referring back to this video to get your pihole set up and glad you got everything working if your network.
@@digital_aloha This threw me off a little too. It might help if you included a summary of the Docker container configuration in the description of the video.
@@carlocabrera489 I may do that. Thanks for the suggestion.
I know this video is 3 years old and the interface/software has a changed a bit but this is the only video/article I found that actually got Pi-hole working for me. Thank you for the detailed video and a to the point video! Cheers!
Super helpful, and learned that the command for macvlan is much easier / faster than my way via pertained.
@nixxblikka Awesome!! Glad the video was helpful and that you learned about the command line setup of a macvlan network as well.
Aloha from North Shore and mahalo for the tutorial. Been wanting to try this out on my DS1817+ for a while but wasn't sure if it'd break anything. Also, nice to see a fellow Islander on YT with tech content. Subbed and looking forward to more.
Aloha jamauai (from rainy Hilo) and mahalo for subscribing. Hope the video gets you going with Pi-hole on your DS1817+. More videos coming and nice to connect with another UA-camr in the state!!
I already had a Pihole running on a PI4b along with my PVR, that sends its queries via a stubby instance so DOT, however, occasionally as with all things it fails. Replacing my dying 416j with a ds920+ gave me the opportunity to have a second instance running for redundancy so thanks for the tutorial. I did find the NAS would not 'see' the Pihole address behind the macvlan, in the end I've put in a static route so it goes via the router otherwise it is working albeit only a fraction of the traffic is going through it 3k Vs 500K I suspect the bare metal one responds faster so is preferred, I'll wait until it is just me in the house and disable that one to make 100% sure I have really redundancy.
EDIT - of course the address I need for the NAS is the bridge address not the actual pihole address as seen by the rest of the lan.
Hi IMBlakeley, You've been busy going through many of my videos. Thanks for leaving feedback and happy to hear you you've got your Pihole redundancy setup. I should try that out in my network. 🤔
this works. very good explanation / walkthrough. i was able to adapt this to a ubuntu 22.04 running docker compose
Thank you for the videos !🙂
Hi TaraD0nBr4n, You're welcome!! Glad you like my videos!!
Great work, thanks for sharing!
Hi Eugene, glad you found the video helpful and thanks for the complement.
Excellent and detailed
Thank you!! Hope things are working out in your setup.
After setting up Pi-hole per your instructions all worked well except that Adlists could not be updated. I kept getting " [✗] List download failed: no cached list available" in the Pihole container log files. In the Pihole GUI, the error message was "connection refused". The problem turned out to be that the Synology firewall was not allowing the pihole-bridge through. In your example, 192.168.82.2 must be allowed through the Synology firewall. Now all works great. Thanks for the excellent tutorial.
Hi @IIWII9, Glad you figured out that the problem was with the Synology firewall and you're welcome on the tutorial.
can you please specify again, which ip adress is to set in the correct spot? i'm using 192.168.155.1 as for my fritz!box and set up the macvlan 192.168.154.1 ... now i'm using 192.168.155.76 for the pihole and 192.168.155.77 for the unbound-pihole within the fritz!box ... as for the dns server adresses: which ones do i have to put in my NAS and my fritz!box to tunnel everything of the getgo? other than that thanks a lot for your videos, great help!!
I have to thank you for this wonderful tutorial. I have a question regarding the dnsmasq.d. I setup dnsmasq in my edgeRouter and I am wondering if it will have conflict when running another on the Docker Pi Hole that I setup in the Synology? If there will be a conflict, can I setup Pi Hole without the dnsmasq? Thanks.
Hi Peter, You're welcome and thanks for your feedback.
Regarding your dnsmasq.d question actually Pi-hole will run dnsmasq because it is what Pi-hole uses for it's DNS/DHCP server. In the video the /etc/dnsmasq.d mount point is actually a physical location where you could add in custom configurations if needed, but even if it weren't created Pi-hole will run dnsmasq.
There shouldn't be any conflicts with dnsmasq running on your edgeRouter and you just need to point your client to your Pi-hole to make use of it.
Good luck with your setup!!
How do you setup unbound for recursive DNS o. Pihole running on macvlan?
@oppailover3087 I actually cover setting up unbound with pi-hole in a couple of my videos, but I think this one would be the best to follow -> ua-cam.com/video/nOlx10aRZjk/v-deo.html. Hope this helps? Best of luck in your setup!!
I have successfuly used Pi hole as per your video. However, since the NAS controls the DNS, if it is down, like loss of power or recently Synology had an update that basically broke everything until you updated all the aps, its is frustrating. Is there a way to have it use an alternate DNS, if the NAS is off? It happens enough so that it is a problem.
@Jp421JP What I do in my setup is add Pi-hole as the first DNS server, then add a secondary DNS server to the DHCP configuration as well. In my case I actually run a BIND server on my network, but you should be able to add Google's (8.8.8.8) or Cloudflare's (1.1.1.1) public DNS server. That setup should get you through the downtime of your Synology NAS and Pi-hole. Hope that helps?
With the recent change from Docker to Container manger, Pihole does not seem to be blocking as much as much it used to. It used to block everything well, now ads are getting through and it blocks only a small percent. I saw somewhere that with the change it affects the Bridge network somehow?
Hi thanx for the tutorial, it was clear.
FYI i had an issue, PiHole container was in a infinite reboot loop
Logs says that i had to change DNSMASQ_USER to root
After that, it works fine.
Hi sticky-fingers, You're welcome on the video and thanks for sharing your experience and your solution. I never did run into that problem.
I had the same issue, changed to root corrected it.
I am stranding with the part phihole-bridge (in your video at 6:00). I get a warning during the setup that the gateway is used for another Docker network. I removed docker completely to start over again but I get the same warning. Any idea what's causing this issue?
Hi Cees, Not exactly sure the cause but what happens if you try another subnet? Maybe you are using a network that is already in use. Alternatively you could SSH into your Synology NAS and try to figure out what Docker networks are already created. The commands that I'd try are "sudo docker network ls" to list the existing Docker networks and "sudo docker network inspect " to display the network's information which should show its Subnet and Gateway. Hope this helps and good luck in trying to resolve the problem.
@@digital_aloha TX for pointing me out. It was indeed a used subnet. Great vid.
@@CeesWarmerdam Perfect!! I'm glad the tip helped you resolve the issue you were having and thanks for the complement on the video.
i already have my pihole with raspi and want to make another for pihole backup in case my raspi goes down. i already followed this guide and successfully deployed my pihole with macvlan and bridge network. but my pihole on synology cannot query anything if i try nslookup with its own bridge ip as a server? kindly help on this?
Great video! Can you also explain, how to get the setup running with IPv6, since I set my Piholes IP on the local DNS of my Fritz!Box for the whole network traffic?
Hi Eddy, Thanks for the compliment on the video!! I'll definitely look into setting up Pi-hole using IPv6 and will create a video when I do (can't promise you a quick turn around though). Good luck in trying to figure things out in the meantime!!
@@digital_aloha Thank you! I got it working already 👍
@@eddymouser4575 Great!! Glad you got things going. Did you setup IPv6 when setting up the Pi-hole container or after the container was created using the Web GUI? Just curious :)
Hii There! Great tutorial, very easy to follow and well explained :) unfortunately i cannot figure out why my pihole is not working. i made it to the part at 9:50 where you nslookup this does not work for me unfortunately and i followed your instructions 1:1 accept for that i had to use the local ip of (192.168.1.8 for my macvlan and 192.168.2.8 for my bridge network). am i missing something here? my router (that handles my dhcp) has the local ip of 192.168.1.1 and my subnet mask is 255.255.255.0. Thank you for any suggestions. would love to get this running finnaly :)
Hi _UNWIRE, Thanks for the compliment on the video. Much appreciated!! Regarding your setup, it sounds like you did everything properly!! One thing I can't tell is if you have the firewall enabled on your Synology NAS. If you do see if things work after disabling it. Also, just confirming that you did the nslookup command from a terminal NOT ssh'd into your Synology NAS. This should be done from a local terminal from your computer. Hope this helps a little. Best of luck in figuring out your setup.
@@digital_aloha Thank you so much! I've been trying to figure this out and I was finally able to make it work with your guide!
It was the firewall of my nas that was causing it to not work... what do i have to allow in my firewall rules for it to still work without having to disable the firewall completely like i am doing currently?
Thank you and have a delightful day :)
@@aintnoair Glad the info that was provided helped you out! Regarding the firewall I think you need to enable access to the custom bridge network and possibly the MacVLAN network as well. I have a video that covers setting up the Synology NAS firewall as it relates to Docker which I think will help you. Here is a link to the specific time within the video that I think is relevant in your setup -> ua-cam.com/video/-my0ilNnxR4/v-deo.html. Hope this helps and good luck in getting your firewall configured properly!!
Excellent video and thanks for your detailed explanation of each part of the setup. Thanks, The bridge network part solved my VPN issues in Synology. One minor question is that only one client (gateway IP of the bridge network) is displayed on the PipHole Admin page even though there are many devices that are using its service through VPN connection. Could it be possible to get a real device id and added to the client list of the Piphole?
Hi Hello World 9527, You're welcome and I'm happy that you got things working once the bridge network was configured. As for your question regarding only the gateway IP of the bridge network being displayed in the Pi-hole admin page, that is how the bridge network works. It won't pass individual client IP addresses directly to Pi-hole. On your LAN though your devices should show up individually because of the MacVLAN network that was setup. Hope this helps?
Thx. Why can t use my dns-server (in nas). The host (only him) ping failed . Without proposed dns in pihole (google..) no resolv..
@anthonycoppet8788 You're welcome!! This is a limitation of MacVLAN networks and the reason why you'd need to setup a bridge network. The NAS would need to use the bridge network to access Pi-hole.
Is there any technical reason to define a custom bridge (in your example you used 192.168.82.0/24 subnet) vs the default bridge of 172.17.0.0/16? Isnt that what the docker0 interface is for to allow host to container connectivity? Or is the custom bridge subnet a preference?
Hi ArmBradPitt 😊, Great question... Other then isolating the Pi-hole container from the rest of the containers running on the default bridge network and making it simple to figure out the IP address assigned to the container (being that it is on a /32 subnet) there isn't a technical reason not to use the default bridge network.
I have not been able to find a tutorial like this for a container that has both pihole and unbound using docker on synology NAS. I've been searching for a week and can't seem to get em running individually (one container with pihole and another with unbound cause I can seem to get the networks to both for both containers), or one container with both pihole and unbound. Any suggestions?
Hi Vic, I was hoping this video would stand out in detailing the setup of running Pi-hole through Docker on a Synology NAS and thanks for the confirmation (although not specifically in what you are looking for with both Pi-hole and Unbound). I'll look to put together a video on using Unbound and Pi-hole on a Synology NAS some time in the future.
Regarding your specific question, what I would suggest is using a MacVLAN network setup but instead of using a /32 network like in the video use a /30 network which would provide you 2 assignable IP addresses that you can assign to the Pi-hole and Unbound containers respectively. For example if I used 192.168.81.8/30 I'd be able to assign the Pi-hole container 192.168.81.9 and the Unbound container 192.168.81.10. At this point you should be able to point Pi-hole to Unbound as your upstream DNS provider.
Hopefully that does the trick and let me know if this helps? I could use your feedback as I put together the Unbound video.
@@digital_aloha I just saw this. Thanks so much for the reply. It would be wonderful if you made a video showing that. Thanks a lot.
Hi Vic, You're welcome! And I did release a video on setting up Unbound with Pi-hole running on a Synology NAS. Check it out if you haven't already -> ua-cam.com/video/-546g1w_L3w/v-deo.html and good luck with the setup if you are still trying to get it going.
@@digital_aloha oh I didn’t know. Fantastic. Thank you so much. Will work on this next week!!! THANK YOU!!!
Good luck with your setup!!
do I have to crate pihole-bridge? what would happen if I didn't to this step?
@mohamedfarhanal-subaey1670 Good question!! Technically you don't and you could just use the default bridge network to provide your Synology NAS access to Pi-hole. What I like about creating the pihole-bridge is that you specify the IP address that will be used so you don't have to inspect the Pi-hole Docker container to figure out what default bridge network IP address was assigned to it. I hope that makes sense?
@@digital_aloha thank you for your reply and I would like to ask you if you have time to make tutorial in detail in how to install pihole with unbound because I try to flow all your video regarding synology , pihole and unbound but I'm really confused. my device synology DS220+ DSM 7.1.1 Ram 6GB 16TB HDD it will be a grate helpful. best regards
@@mohamedfarhanal-subaey1670 Actually I did create a video that sets up both Pi-hole and Unbound using Git and docker-compose. See if that one works well for you. Here is the link -> ua-cam.com/video/nOlx10aRZjk/v-deo.html. Let me know how it goes!!
Great video! One question: is there a way to use the local DNS in pihole this way? It doesn't seem to work for me 😞
Hi Michel, I actually just ran through the setup of pi-hole on a new Synology NAS I've been working with and the local DNS seems to be working fine for me. I logged into the pi-hole web interface, went to Local DNS and added a DNS entry. I then changed my Macbook to use pi-hole for it's DNS server and the local DNS entry I added into pi-hole worked fine.
In your situation are you able to resolve external hosts using pi-hole? Just curious if pi-hole is working properly to start off with.
In any case good luck with your setup!!
@@digital_aloha Hey Aloha, thanks for the quick reply.
Yeah, thats what I did but I didn't change the DNS server on my device/s. I changed in on the level of my router (Fritzbox). The queries are properly blocked by pi-hole on any device. However, any IP I try to entry in the pihole DNS records is later on not reachable / cannot be found with a DNS_PROBE_POSSIBLE error (including the one from pihole itself).
@@michelwork I did a little bit of research and others that have the same DNS_PROBE_POSSIBLE error seem to have some issue with the router they are using. I found this post on reddit from a person that uses a Fritzbox as well -> www.reddit.com/r/pihole/comments/n1wrdq/local_dns_not_working_after_domain_change/. Hopefully this helps you out? Good luck in trying to solve the issue.
Super easy thanks for sharing this information with us 🤩
You're welcome, glad the video made setting up Pi-hole easier for you!!
Thanks for the great video, I have all macs on my network, and I use Unifi for DHCP. In your example, what IP address would I give my DHCP server on my Unifi to use the PIHole server
Hi Jack, You're welcome and I'm happy the video was helpful. Regarding your question the IP address you should assign your DHCP server is the MacVLAN IP address that you assigned to Pi-hole. Hope this helps and good luck in your setup!
As someone new to networking, this was well explained and detailed. Thank you. Could you explain why this installation is better than simply running pihole normally? With the macvlan and bridge? Perhaps you did, but I did not understand it.
Hi J P, You're welcome and thank you for your comment as well. I'm going to link to a UA-cam video (ua-cam.com/video/jaYlhE_EEyA/v-deo.html) and Pihole Discourse post (discourse.pi-hole.net/t/setup-on-synology-docker/18067) that really dive into why you should use a macvlan and bridge network when setting up Pihole on a Synology NAS if you want to deep dive into the topic.
My short summary on why you should set things up this way, regarding the macvlan network, is it provides the Pihole docker container it's own separate IP address, removing the restrictions you would have if it were set up in the default bridge network that you get with Docker. This removes any chance of port conflicts (for example Pihole runs on port 53, but if you had port 53 used on your Synology NAS you'd have to map Pihole to a non-standard port number like 5353 for example). Regarding the bridge network this is required because your Synology NAS can't access the macvlan IP address directly so the bridge network gives the Synology NAS access to the Pihole container.
Hopefully this makes sense and doesn't confuse things further?
@@digital_aloha Thanks, that was helpful. It did not cover the bridge network, as I saw. Why does synology need access to the pihole container via the bridge? While it runs on the synology, the NAS would seem to be "out of the loop" so to speak.
@@Jp421JP You're welcome!! The bridge network is needed because of the limitations of the MacVLAN network. The MacVLAN network within Docker is explicitly setup with isolation in mind (even from the host) and the work around is adding in the bridge between Docker and the Synology NAS itself. I think there are workarounds to get things working, but the bridge was the simplest option to use in my opinion.
@@digital_aloha Thanks for the explanation. This makes me think that I don't actually need the bridge configuration since I just point my router to the Pi-hole's MacVLAN IP address, while my Synology NAS already refers to my router to resolve domain names. Is that correct, or am I missing something here?
@@carlocabrera489 Hi Carlo, I believe that should work! If your Synology NAS doesn't need to refer to your Pi-hole directly then it should be fine and you won't need a bridge network setup. If you tried this let us know how it went!!
Great tutorial. The Bridge step was really hard to follow though because the print is too small to read and the video can't be zoomed because the res is too low. Hopefully I'll figure it out somehow.
Update: It wasn't clear that it was "/24" for the subnet and "/32" for the range. Also, same problem with folder names. Way too small to get the spelling right.
Hi Michael, Thanks for the feedback on the video. I'll keep in mind that the text was pretty small and adjust accordingly in future videos. Unfortunately my equipment doesn't allow for higher resolution. Hopefully you got your Pi-hole setup configured and and working properly!!
Thank you very much for your great tutorials. Unfortunately in this one, when I try to create pihole-bridge network I receive an error saying that the Docker uses the same address for a gateway or the subnet overlaps with the existing Docker network in the address space. QUICK update - I have just realised that I created "homebridge container" that uses host mode. That's why I cannot create pihole-bridge network. I will try to find the solution.
Hi Marcin, You're welcome!! I'm happy to hear that my tutorials have been helpful to you. Hopefully you find (or have found) a solution to your issue where you couldn't create the pihole-bridge network!!??
Everything worked great except I can't get the blacklist to block anything? I have my test computer pointed to the pihole and netflix is blocked but still comes up. even says it blocked in pihole. Any help?
Hi Donnie, Sorry for the slow response. Hopefully you resolved the issue already but, if not, the problem is likely due to the blacklist rule for netflix not being assigned to a client group. To check on this, from the Pi-hole UI, go to Group Management -> Domains. Here you should see your netflix rule and what you want to do is look for the Group assignment column and assign the rule to a group, which should be the Default group if you haven't created other groups. Hope this helps and good luck to you in your setup.
what was that app you used to find a free ip address?
Actually that is the web interface for my router. You'll want to log on to your router or DHCP server to get the details of what IP addresses are available. Hope that helps? Good luck to you in your set up!!
Great video. However, I'm running into an issue in where the FTL is failing to start. When I open the admin panel, the pi-hole diagnosis screens shows this error - "FTL failed to start due to failed to create listening socket for port 53: Permission denied". When I go to the docker logs themselves, I see three repeating lines. First line is "Starting pihole-FTL (no daemon) as pihole". 2nd line is "Stopping pihole-FTL". 3rd line is pihole-FTL: no process found. I do have a docker with pihole working using the same bridge as my Synology but I have that turned off. Thoughts?
I know this question is months old but I was just looking through the comments to help solve this as I just experienced the same issue. After several hours of troubleshooting I was able to figure out what caused this problem for me. It occurred after I restarted the NAS. It turns out that Unbound and pihole swapped IP addresses. Originally in my setup, Unbound's IP was 192.168.1.9 and Pihole's was 192.168.1.8. Subsequently Unbound was 192.168.1.8 and pihole was 192.168.1.9. This likely occurred because their IP addresses are not static, so whichever container started first got first dibs on IP address. As I am not sure how to make the addresses static, I kept the current settings and accordingly changed the IP settings on my router and other devices. Certainly making the addressed static would be ideal because this problem is likely to return the next time I restart the NAS.
Hello. Thanks for you tutorial. followed it, made a macvlan x.x10.25/32 made a bridge x.x11.25/32, set the server to the macvlan adress and started the container. could log in the pihole at x.x.10.25 but afaik pi hole would not filter anything. nslookup with x.x.11.25 would work fine but macvlan x.x.10.25 would not respond to the nslookup. if I point dns of my pc or router to x.x.11.25 nothing would happen. what would be dns server for the other clients? how to resolve macvlan nslookup not working? ping from my pc to macvlan x.x.10.25 would work fine.
Hi Neinhalt004, You're welcome and it looks like you are pretty close in your setup!!
I think the issue is the IP address you are using and from what terminal you are running the nslookup command from. The macvlan x.x.10.25 IP address should be used by external clients and your router. The bridge x.x.11.25 IP address should only be used by your Synology NAS and services running on the NAS.
Regarding your specific questions your PC, router and other clients should use the macvlan x.x.10.25 IP address (this should be the address that you would use the majority of the time). The bridge x.x.11.25 IP address should be set on your Synology NAS so it makes use of the pi-hole install and if you run services like a VPN server on your Synology NAS you'd use the bridge IP address there as well.
Hope this helps? And good luck in getting everything working!!
@@digital_aloha thank you again for you kind answer. so external clients (or better yet vlan dns in router) receive the dns with the ip of the host (nas in my case), the host receives the internal container ip. is there a strategy in assinging the container ip's in the bridge? I have just setup a the bridge with whatever unused subnet (by other containers). I think the pi-hole would have worked with the setting sugested but I can't wrap my mind why would the nslookup would not work, when in your video it clearly did.
did you made a route from host to container outside of this tutorial?
Hmm... Actually the external clients should use the macvlan IP address assigned to the pi-hole container.
As for a strategy for assigning bridge IPs I'd just use an unused subnet or at least one that is different from the subnet that your NAS is on.
Regarding any additional routes I actually didn't do anything more then what you saw in the video.
Hope this helps?
@@digital_aloha sure it does. I will remake the settings. thank you very much for helping.
@@digital_aloha It helped. I realise that the first setup was ok and the pihole was installed correctly. I did not pay attention when you tested nslookup outside of the nas host and that led me to the wrong conclusions. remade the container and put the macvlan in the primary dns of the vlan router settings. it all seems to work ok. thank you again for this great tutorial, you have a new suscriber.
> Finding a free address that can be used for a macvlan network
I'm not sure how to do this; could you recommend any resources that go into more detail about this step?
Hi Dru, Hard to say what resource to provide you because it will be different for each situation. You should watch the "Setup The Docker MacVLAN Network" section of the video for hopefully some help. Essentially what you'll need to do is look at the configuration of your DHCP server and find an IP address that isn't used by any other system on your network. Then you'll use that IP address when creating your MacVLAN network. Hopefully that helps a little? Good luck to you!!
When I am trying to add "pihole-bridge" in docker network - I cannot add gateway "IPv4 gateway 192.168.1.254 is already in use by other Docker network." pihole-macvlan Gateway is also same
Hi Getur, The pihole-bridge network can't be the same as the pihole-macvlan network. That is probably why you are getting the error message. Also make sure the pihole-macvlan subnet that you set up is on the same network as your Synology NAS. Hope that makes sense? Good luck!!
Can you do a video on how to properly update it without losing settings?
Hi Connor, I like that idea!! I'll look into creating a video on updating Pi-hole (or maybe in general Docker containers) running on a Synology NAS. Thank you for the suggestion!!
@@digital_aloha Cool, thanks! I’ve had Pi-hole running on my NAS in a docker container for a while, I just can’t figure out the right way to update it… so I haven’t. And there’s tons of initial set up videos, just not for how to do updates. I think a video like that would help a lot of people out.
@@connor-betts I responded to another viewer regarding upgrading Pi-hole (and Unbound for that specific viewer) and I'm basically cutting and pasting my response here. Hopefully this helps... Still planning a video on upgrading Docker containers running on a Synology NAS though. 😀
1. Go to Docker within DSM and bring up Registry.
2. Search for Pihole and click Download to download the latest image. This will replace the image that you currently have downloaded.
3. Go to Container and stop the Pihole container.
4. After the container is stopped click on Action and Reset. This will give you a warning that all data will be lost on reset, but that is fine because of the volumes you setup earlier. Click Yes.
5. After the reset is completed click Action and Start which should bring up the container using the updated image.
Good luck!!
Tried this in container manager but it doesn't work.
I could only get this to work running the container as a privileged container.
Hi tomski182, I've been trying to figure out why you would need to run the Pi-hole container as a privileged container, but I can't find anything. All of my Pi-hole installs don't require a privileged container and I've done a bunch of installs. Maybe you did some tweak to your Docker installation at some point? Sorry I can't be of much help on this. Good luck in finding a solution!!
unfortunately, it's beyond my grasp. Wish it could all be automated, like in a script.
I don't have a video that automates setting up just Pi-hole, but if you want to include Unbound in your setup you could try the setup from this video -> ua-cam.com/video/nOlx10aRZjk/v-deo.html.
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.
I have a problem.when I key nslookup,server is 9:05 DNS ip.then,youtube.com .The reason is I used virtual machine?IF only macvlan one IP ,just don't create macvlan bridge and change DNS, it has internet.Then,I want macvlan two IP~
I would double check what IP address was assigned to the Pi-hole container on the MacVLAN network. To do this SSH into your Synology NAS and run `sudo docker container inspect pihole` (or the name you gave your Pi-hole container) and confirm the IP Address. Then try the nslookup command using that IP address. Hope this helps? Good luck to you!!