Hello !
Tried to run recommended install but I cannot get the unbound to work.
Initial deployment : ubuntu 24 LTS minimized
unbound would fail health check. I found that its access control was not up to scratch (127.0.0.2/8 network was not there) and it was doing dns lookups via 127.0.0.11 not 127.0.0.1 .
so I tinkered it up to the point where it was able to resolve DNS nut no other container can.
So I have scrapped the vm, built new one on ubuntu 25, gave it fixed manual IPv4 address, configured DNS , disabled IPv6.
I have not installed any firewall. I have followed all steps from the documentation to the letter, using stable build.
yet, unbound will be marked as unhealthy and I am not greeted with the admin login screen.
rather than poke around this time, I would like to get community help please so I understand where does it go wrong.
I have not done any testing to the configuration apart from enabling 0.0.0.0 in access-control in unbound.conf (after docker compose down -> edited unbound.conf ->restarted docker -> docker compose up -d)
does anyone have an idea how to troubleshoot it ?
I did see similar problem on serverfault(https://serverfault.com/questions/642981/docker-containers-cant-resolve-dns-on-ubuntu-14-04-desktop-host) so I have installed bridgeutils prior to docker deployment - but this has not yielded any improvement.