bind_zone_dir not acknowledged on Ubuntu and last host is always updated

[oisteink]

I'm trying this out and have two ubuntu targets. In the config i set bind_zone_dir to /var/lib/bind as it's a dynamic updatable zone and not a slave zone. They still end up in /var/cache/bind I don't plan any deletes of the /var/cache/bind directory, but it would be nice if the setting was honored so backup scripts would not have to be altered.

Also if I run the playbook twice the last host in the list gets updated both times while the first stays as it is and is only updated on first run.

This is on a cloud test rig so I can provide access if needed for debug.

[oisteink]

Here's output of 2nd replay. There has been 0 interaction with any of the targets between first and second run. In the hosts file xxx2 is declared first and xxx1 is declared second. Seems like there's no hashing of the last one, only the first one. I'll try to spin up another target tomorrow and see if it's just the first or all but the last.

Edit: removed text and moved it to a file output.txt

[oisteink]

Removing the run_once on those tasks seems to fix it.

[bertvv]

bind_zone_dir is defined in vars, not in defaults. Consequently, it cannot be changed by your own playbook. Would your issue be resolved if we moved it to defaults, or if we at least allowed a custom path for bind_zone_dir?