Explictly start unbound after reconfigure

Change-Id: Icf2533ad2b3f099ff3fee6bce1b645e265c0b80a
(cherry picked from commit 8c5183b43d17c03401623ede25e1cb09f57cb187)
diff --git a/roles/dns-unbound/handlers/main.yml b/roles/dns-unbound/handlers/main.yml
index 858b7c0..fa864ae 100644
--- a/roles/dns-unbound/handlers/main.yml
+++ b/roles/dns-unbound/handlers/main.yml
@@ -15,9 +15,15 @@
 
 # dns-unbound/handlers/main.yml
 
-- name: restart-unbound
+- name: start-unbound
   service:
     name: unbound
     enabled: yes
-    state: restarted
+    state: started
+
+- name: reload-unbound
+  service:
+    name: unbound
+    enabled: yes
+    state: reloaded
 
diff --git a/roles/dns-unbound/tasks/main.yml b/roles/dns-unbound/tasks/main.yml
index e33a167..d2fe1a6 100644
--- a/roles/dns-unbound/tasks/main.yml
+++ b/roles/dns-unbound/tasks/main.yml
@@ -33,7 +33,8 @@
     group: "{{ unbound_group }}"
     # validate='unbound-checkconf %s' - can't use, checks path, not just config.
   notify:
-   - restart-unbound
+   - start-unbound
+   - reload-unbound
 
 - name: flush unbound handlers
   meta: flush_handlers