I made this account just to start sharing my experience moving pi-hole to my Synology docker. Many of you may have seen Free your Synology ports for Docker | Tony Lawrence and this got me doing some research on macvlan with docker. If you ssh into your Synology as a root user and use the following…

Ah I think you are spot on with this, I since gave up on this but its now obvious I should not have chosen eth0. I have an aggregation on eth0 and eth1, so should have chosen bond0! Will give it another attempt when I get the chance. EDIT: @Beefyfish all working now thanks for your help. Fantas…

Ok a little more messing around tonight I have managed to do a complete setup of Pi-hole using synologies docker UI besides creating the macvlan in SSH above. I mean complete setup by binding volumes for the etc/pihole and etc/dnsmasq.d to maintain settings even after deleting my docker image or re…

Ok here is a little write up I did. I was unable to load the word version to the site so I uploaded the a zip file with the original document but attached pictures of the write up. The only downside of this is it will only show an IP for the Synology in the pi-hole interface because the Synology us…

Thank you so much for this guide. I tried a lot of guides, and nothing would work. This is by far the most easy and elegant way of installing Pi-Hole on a Synology NAS with Docker. Good job!

Thanks Morten, It may not be the cleanest write-up, but to me was the nicest way as to avoid doing a majority of the work in a headless environment as I really dont like to keep SSH available on the NAS and the Tony Lawrence how-to didn't address the issue of the NAS not being able to talk to its ow…

Only issue I encountered was that setting the DNS for the NAS to 192.168.100.2 didn't work. It would break quickconnect functionality and also couldn't connect to the docker repository. I fixed it by just setting the DNS for the NAS to 8.8.8.8 as it doesn't need adblocking anyways.

I had that issue when first trying this install. In your setup of the docker image did you make sure to set DNSMASQ_LISTENING: Local? Without it set to local pihole will not listen to the bridge interface you created and will only listen over the mcvlan which the host device is unable to do because …

For me this also did not work (defining 192.168.100.2 as DNS server). I did set DNSMASQ_LISTENING to local. Did you look into it further?

I havent had time to look at it but I definitely will tonight. If you happen to be around your pihole could you try going to you pi.hole page and in the setup change it to listen to all interfaces and apply that to see if it works?

ok, I looked at this tonight. I have to ask but did you make sure to add your docker image to both the pihole and pihole_bridge networks? If so can you please look to see if listen on all interfaces is selected like below? [Untitled] Resolving this issue so your Synology can use pihole is more …

Hello I am really happy that you evolved the Lawrence guide and I am happily going to follow it. But first I need to know if I can use it with my set up. In my case I use my own DNS that runs on a OpenWRT device with Secure DNS,DNSSEC, TLS 1.3 and Encrypted SNI. At the moment I just use custom DNS: …

Pi-hole Userspace

Setup on Synology Docker

Help Synology

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled