An old thread but I’m trying my luck since I’m facing the exact same problem. I’ve tried the steps proposed @Carlos_Estrada but with no luck. Unbound will still not start.
Excerpt from systemctl status unbound:
systemd[1]: Started Unbound recursive Domain Name Server.
unbound[6913]: Oct 24 23:25:39 unbound[6913:0] error: can't bind socket: Cannot assign request...or ::1
unbound[6913]: Oct 24 23:25:39 unbound[6913:0] error: cannot open control interface ::1 8953
unbound[6913]: Oct 24 23:25:39 unbound[6913:0] fatal error: could not open ports
systemd[1]: unbound.service: main process exited, code=exited, status=1/FAILURE
systemd[1]: Unit unbound.service entered failed state.
systemd[1]: unbound.service failed.
Any sugestion as to what might be causing this problem?
unbound[6913]: Oct 24 23:25:39 unbound[6913:0] error: cannot open control interface ::1 8953
Same is suggested for control-interface option when unbound remote control is enabled (enabled by default by upstream Unbound package and by NethServer but control-interface not explicitly specified).
If IPv6 was disabled (and must remain that way) by any particular reason, do-ip6: no unbound option could be of use.
/var/log/messages and jounalctl -u unbound might provide more clues about why the service does not start.
When trying any of the unbound options remember the conf file is templated.
I split off this later discussion because the root cause is different. And I think @dnutan deserves another accepted fix… @bragrabb, can you please mark the post of @dnutan as solution?