Hi @diginc and all. I can't figure out why my Pi-hole forwarding to Unbound fails. This is setup as two containers, both on Docker's bridge network. Pi-hole is 192.168.1.13 (172.17.0.2) on port 53 tcp and udp, while Unbound is 192.168.1.13 (172.17.0.3) on port 50053 tcp and udp. Pi-hole's Upstream …

[image] musicsnob: --network=bridge \ That's probably your problem, 2 containers on the default bridge network will often have trouble talking to each other since they lock it down a bit more than a user created bridge network. I'd suggest creating your own network with bridge mode or using …

Thanks for responding to the op. I was banging my head on this same issue all weekend and thanks to your post I was able to get it working. Here's an excerpt from my CloudFormation template : Metadata: AWS::CloudFormation::Init: configSets: myCfnConfigSet: - "sta…

I'm super late here, but thank you @diginc for pointing out the issues with the legacy bridge network. For anyone else that may run into a similar networking issue: I've placed unbound and pihole in a user-defined network named "dns-net". I had to change the docker run DNS1 parameter from the host …

[image] musicsnob: --env DNS1=$(docker inspect -f '{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}' 'unbound') \ better late than never, how can I accomplish the same using docker-compose?

Pi-hole Userspace

Pi-hole to Unbound forwarding fails

Help docker

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled