BIND doesn't need to restart, and causes service disturbance when restarted vs reloaded (i.e. if something breaks in a restart, you're down, however in a reload if you break, you just don't load the change but at least you're still up).
- Add (I've done this in my own branch thus far...)
action :reload do
service new_resource.service_name do
action :reload
end
end
- Address when to reload vs restart. Zone changes should be a reload. Zone additions and deletions can technically also be an rndc command, specifically
rndc reconfig, however it won't reload existing zones (you still need rndc reload. We can also be more targeted on the reload to do rndc reload <ZONE> and if this cookbook is supporting views (not sure that it is), then we'd add the view context to resulting in rndc reload <ZONE> <VIEW>. I haven't made updates for this but as referenced above, I've done number 1.
BIND doesn't need to restart, and causes service disturbance when restarted vs reloaded (i.e. if something breaks in a restart, you're down, however in a reload if you break, you just don't load the change but at least you're still up).
rndc reconfig, however it won't reload existing zones (you still needrndc reload. We can also be more targeted on the reload to dorndc reload <ZONE>and if this cookbook is supporting views (not sure that it is), then we'd add the view context to resulting inrndc reload <ZONE> <VIEW>. I haven't made updates for this but as referenced above, I've done number 1.