Post by @docwhozee
#freebsd jails & unbound
jails, unbound, & ip-transparent
#littlefedi (and other stuff) is running inside its #freebsd #jail on xyzzy.cafe and gets its intertubes traffic through #caddy, which is also running inside a jail. DNS resolution is done by unbound running on the host.
After updating my #freebsd instance today, I noticed that #littlefedi's work queue was "exploding" — and a look into its log showed that DNS resolution was failing. A drill on the jail console failed as well.
The root cause seems to have been that unbound could not bind to the jail interface as that was not up yet (bastille running later, much later). Just using
interface: 0.0.0.0
interface: ::0
and suitable access-control lines did not help. What did help is
`ip-transparent: yes`
and specific interface lines.
unbound.conf(5) was a bit confusing. nlnetlabs man page was a bit more enlightening:
Allows you to bind to non-local interfaces. For example for non-existent IP addresses that are going to exist later on, with host failover configuration.
And that did the trick.