Removing a reverse zone in FD does not actually remove the configuration in the DNS master
Description
Argonaut-ldap2zone does not remove configuration if we remove a reverse zone.
Distribution Name and Version
RHEL 7.3
Argonaut Version
1.2
PERL version used
v5.16.3
Origin of perl packages
Epel, Redhat channels (server-optionnal / server) and argonaut-libs
Steps to Reproduce
- Create a reverse
- Add records in that reverse
- Update via argonaut
- Delete the reverse
- Update again with ldap2zone
Expected behavior:
At least cleaning /etc/named/named.conf.ldap2zone to not include the /etc/named/named.conf.ldap2zone.reverse file
Removing the corresponding file would be the less
Removing the refering zone file would be a plus (at least on the master side, because it is not handled by argonaut in the slave servers)
Actual behavior:
Neither the /etc/named/named.conf.ldap2zone file including /etc/named/named.conf.ldap2zone.reverse and the related file, nor the /var/named/db.reverse. zone file are deleted
The reverse lookup works while the forward may be inconsistent
Reproduces how often:
100%