Last week I set up Pi-hole mainly for blocking ads and handling a few internal DNS requests. This works fine, when OCD kicked in. I thought it would be nice to add Unbound to the mix to not have to use external DNS server and this hiding my traffic from those who doesn't concern. After some struggles, this is now running fine, except for a few things.
I have set my router to hand out the DNS server via DHCP to my clients and set devices and virtual servers with a static IP to use it too. This also works. My Synology NAS however won't use the internal DNS server and so do my Docker containers. I work around I found was having my router use the internal DNS server, set all devices to use my router as DNS server which then forwards the requests to my internal server. This also works fine, but that shouldn't have to be, right?
My setup:
- USG Pro
- Unifi Switch
- 3 Unifi Access Points
- Synology NAS running Docker and VMM
Docker runs Pi-hole and Unbound in separate containers that are able to talk to each other via a MacVLAN. Before adding Unbound, I had Pi-hole running in bridge mode and when using 127.0.0.1 as DNS server on the Synology, all worked fine. My router does have a config.gateway.json file that handles guests setting an outside DNS server, but this is only for guests and other VLANs so this shouldn't interfere with the main LAN.
Any thoughts?