unbound-docker-rpi VS unbound-config

- Unbound

In Pi-Hole, all the queries are sent to and answered by the Unbound docker container, as confirmed by the Pi-Hole logs. I am not seeing any query in Pi-Hole going outside my network for resolution, so I am stumped as to what the cause of this is. The best guess that I could come up with is that somehow Unbound got configured in forwarding mode instead of a recursive resolver. I am not an expert on networking or Unbound, so I am looking for anyone who has an idea as to how to solve this. If it helps, I used https://github.com/MatthewVance/unbound-docker-rpi as the docker image to set up unbound.

If your using a pi, you need to use the pi image. Also I remember that I created these files before deploying the container: config files for unbound * a-records.conf ```

mvance/unbound-rpi is a image that is updated regularly and used by many. The code he uses to create the image is here.

I'm not certain I'm coming at this from the right angle, but you can perform local-data redirects quite trivially with unbound.

Just so you're aware, unbound can be configured to serve expired records (with limitation), putting a wager on the balance of probabilities of the record still being the same value.

Maybe you might find this interesting.

You might know me as that Unbound guy, or maybe even that dnsproxy guy. Today I would like to make myself known as that Munin guy, and introduce munin-pihole-plugins for Munin Monitoring.

I have compiled a sort of educational/foundational/framework config repository that tracks my work with Unbound.

I think you might like this commit.

I have example configuration here, as well as source compiled binaries from Unbound git head (currently 1.13.3) if you happen to be running it on aarch64 hosts.

Somewhat tentatively posting binaries built from unbound git master/head for aarch64 available here.

More yes with an if, no with a but. You may be doing something like this in your Unbound deployment for instance.