unbound default configuration only works after reload

[Alexander Solla]

Fresh Saucy Salamander Install:

$ sudo apt-get install unbound
...
Setting up unbound (1.4.20-1) ...
 * Starting recursive DNS server unbound

$ dig @localhost ubuntu.com
; <<>> DiG 9.9.3-rpz2+rl.13214.22-P2-Ubuntu-1:9.9.3.dfsg.P2-4ubuntu1.1 <<>> @localhost ubuntu.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 43274
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
...

$ sudo /etc/init.d/unbound restart
 * Restarting recursive DNS server unbound [ OK ]

$ dig @localhost ubuntu.com

; <<>> DiG 9.9.3-rpz2+rl.13214.22-P2-Ubuntu-1:9.9.3.dfsg.P2-4ubuntu1.1 <<>> @localhost ubuntu.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 36193
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

$ sudo /etc/init.d/unbound reload
 * Reloading recursive DNS server unbound [ OK ]

; <<>> DiG 9.9.3-rpz2+rl.13214.22-P2-Ubuntu-1:9.9.3.dfsg.P2-4ubuntu1.1 <<>> @localhost ubuntu.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 35538
...
;; ANSWER SECTION:
ubuntu.com. 600 IN A 91.189.94.156

I'm not sure what is causing this. I am pretty sure it is going on in the Trusty Tahr branch, too (since I was running Trusty when my cloud mysteriously decided to stop working)

Is this expected behavior? It looks like a regression to me. I understand that a reload is supposed to make unbound look at the new configuration, but why wouldn't a restart do that too?

[Jonathan Davies (jpds)]

I can't reproduce this issue on 1.4.22-1ubuntu4/trusty packages.