Last updated on 27 February 2025
Web portal settings
You do not need to enable anything on the ‘Web portal settings’ screen click ‘Next’ again.
On the final screen click ‘Done’ which will begin the download of the container images and once downloaded they will be launched!
The image will now be downloaded and extracted. You should see ‘Code 0’ when it has finished.
You will now see your Pi-hole running and should have a green status on the left-hand side.
Accessing the Web UI
The web interface will now be available via the following methods. If you use the https address you will need to accept the self-signed certificate warning in your browser.
| Network Mode | Access method |
|---|---|
| Host | http://nasIP:8000/admin |
| Bridge | http://nasIP:8000/admin https://nasIP:8443/admin |
| Macvlan | http://macvlanIP/admin https://macvlanIP/admin |
You can access the UI with the password you specified in the compose.
Point Pi-hole at your Unbound instance (Optional)
Click on Settings, then DNS. You will need to turn off any existing public DNS providers if any are ticked (Usually Google). Then click the Custom DNS drop down and enter your NAS IP address followed by #5335
For example 192.168.0.18#5335
Now “Save & Apply” the changes.
Update your Router DNS
Now you need to add the appropriate IP address to your router or DHCP Server settings the IP you use will depend on which network method you used to set up Pi-hole
Note: some routers have both WAN and LAN DNS settings, you will just be changing your local LAN setting.
Bridge or Host = Use your NAS IP address.
Macvlan = The address you chose for the container on the line ‘ipv4_address:’
It can take some time for all of your devices to move over the new DNS settings so be patient, and you will gradually start to see your stats begin to start.
Add some block lists
Don’t go crazy with block lists as adding 10 million blocked URLs is largely a waste of time stick to some good quality core lists from these sites
That’s it you are now blocking ads network wide!
Looking for some help, join our Discord community
If you are struggling with any steps in the guides or looking to branch out into other containers join our Discord community!
Buy me a beverage!
If you have found my site useful please consider pinging me a tip as it helps cover the cost of running things or just lets me stay hydrated. Plus 10% goes to the devs of the apps I do guides for every year.
I’ve used plenty of your guides and today I’ve encountered my first problem — I made my changes to the pihole YAML code, pasted it in and all looked fine, but when I paste the YAML for the unbound portion of the project I get the error “Property unbound is not allowed” and can not progress any further this is on a Synology DS1819+ running DSM 7.2.2.-72806 update 3.
Given the updated guide was just posted today I’m hoping there might be a minor syntax/formatting issue that I’m just not seeing. Any help you can offer will be appreciated.
Hey – I have double tested the compose, and they seem to paste in OK for me, can you reply with your compose.
https://paste.drfrankenstein.co.uk
It will give you a URL to use.
Amazing job, I finally managed to put a pihole on my Synology. Now, quick question. Few days after 6.0 upgrade and reinstall everything from scratch, they updated again to some 6.0.3 build. Following your guide, I used the docker update feature, it worked fine and pihole is working properly, but now I have two containers:
pihole-pihole-1 pihole/pihole:latest greyed out
pihole-macvlan pihole/pihole:latest green
Question is, am I supposed to delete the first one?
Hey – So the update should have removed the first install. You can safely delete it.