The dispatcher script only checks whether Unbound has a specific zone configured already, and if yes, doesn't check whether it contains the same data as the connection. When for example the connection name server list is changed, this change is not propagated to Unbound.
Just filed a related upstream bug report: https://www.nlnetlabs.nl/bugs-script/show_bug.cgi?id=567
The dnssec-script part fixed in 0.12 except that bug #1100796 was introduced. The unbound part fixed upstream but not ported to Fedora.
I want to track this for F20 instead. The blocker is fixed in rawhide. Unbound part is tracked by bug #1067856 but we don't strictly depend on it.
Fixed in rawhide, will update F20 when ready.
dnssec-trigger-0.12-12.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/dnssec-trigger-0.12-12.fc20
Package dnssec-trigger-0.12-12.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing dnssec-trigger-0.12-12.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-7942/dnssec-trigger-0.12-12.fc20 then log in and leave karma (feedback).
dnssec-trigger-0.12-13.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/dnssec-trigger-0.12-13.fc20
dnssec-trigger-0.12-13.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.