Skip to content

[dns] Wrong role behavior with Ansible 2.17

If we change the variables of a DNS zone and run the role from an environment with Ansible 2.17, everything apparently works fine:

  • We see the yellow color indicating the change in the DNS zone
  • We see the new serial in the NS' zone file:
root@catanga:/etc/bind/zones# cat db.extension.udelar.edu.uy | grep series
                2024072601; serial

However, in the operating system, the file maintains a previous modification date:

root@catanga:/etc/bind/zones# ls -altr | grep extension
-rw-r--r-- 1 root link 1124 July 24 14:16 db.extension.edu.uy
-rw-r--r-- 1 root link 920 July 24 14:16 db.extension.udelar.edu.uy

And this causes the new records to not be loaded until we restart bind service.

This doesn't happen If we run the same in an Ansible 2.16 environment.

This already happened to @valem and me.