Comment 2 for bug 988513

Lately, we found out that this issue makes it virtually impossible to deploy unbound using automated tools (specifically: puppet), since this issue requires you to:
- install unbound (daemon gets started)
- edit config file
- restart unbound
- continue doing other stuff

When the daemon gets started the first time, all DNS lookups fail. When using puppet for deployment, you can do all these steps automated, but since puppet tries to delay the unbound restart until the end of the run, any action from puppet that tries to use DNS (f.i. download another package) will fail until unbound is restarted, which will not happen because puppet fails its run (because of broken DNS). There is virtually no way (AFAIK) that will get unbound running using puppet without modifying the package that ubuntu provides.