> Can you tell please which version did you upgrade from? > Please note that before, unbound in Debian had a patch > to secretly enable remote-control socket which by default > is tcp. In this release I just made it explicit instead of > doing it secretly. Right you are, the socket was open before. I don't know which unbound version I had before. The tcp socket only came to my attention now being explicit in the config. Now that I'm aware I do believe a unix socket would be the more sensible default.
> Actually it was my thought to enable control socket (I'm not > sure /var/lib/unbound is a good place for it, /run sounds > better but I need to check if it works when unbound is > chrooted. Tested it, as far as i can tell it works for me with chroot: "/var/lib/unbound" and control-interface: "/run/unbound-control.socket" (and BindPaths=/run/systemd/notify:/var/lib/unbound/run/systemd/notify in the systemd service file) My test was `unbound-control stats` says something. Cheers ceddral
