argonaut-ldap2zone does not take the right SOA when refreshing a zone and its reverse
Description
When refreshing a zone for exemple argonaut-project.org, the zone is correctly written but the soa in the reverse is wrong
Distribution Name and Version
Debian jessie
Argonaut Version
1.2-fixes
PERL version used
perl 5.20
Origin of perl packages
Debian jessie
Steps to Reproduce
- Update and save the zone in FusionDirectory by adding a record
- Run argonaut-ldap2zone --norestart --dumpdir dnszone/ argonaut-project.org.
- the soa serial is not the one from the zone refreshed in the reverse file
Expected behavior:
The soa of the reverse file should have the serial of the zone refreshed
Actual behavior:
the soa got an other serial from another zone
Reproduces how often:
100%
Additional information
dn: zoneName=argonaut-project.org.,ou=dns,dc=opensides,dc=be
objectClass: dNSZone
zoneName: argonaut-project.org.
relativeDomainName: @
dNSClass: IN
sOARecord: dnsmaster.opensides.be. hostmaster.opensides.be. 2017100502 3600 18
00 720000 6400
aRecord: 195.154.20.140
mXRecord: 10 smtp
nSRecord: dns1.opensides.be.
nSRecord: dns2.opensides.be.
nSRecord: dnsmaster.opensides.be.
dn: zoneName=128-27.20.154.195.in-addr.arpa.,zoneName=argonaut-project.org.,ou
=dns,dc=opensides,dc=be
objectClass: dNSZone
zoneName: 128-27.20.154.195.in-addr.arpa.
relativeDomainName: @
dNSClass: IN
sOARecord: dnsmaster.opensides.be. hostmaster.opensides.be. 2017100502 3600 18
00 720000 6400
nSRecord: dns1.opensides.be.
nSRecord: dns2.opensides.be.
nSRecord: dnsmaster.opensides.be.
;
; Database file unknown for 128-27.20.154.195.in-addr.arpa. zone.
; Zone version: 2017092702
;
$ORIGIN 128-27.20.154.195.in-addr.arpa.
$TTL 500
@ 500 IN SOA dnsmaster.opensides.be. hostmaster.opensides.be. (
2017092702 ; serial number
3600 ; refresh
1800 ; retry
720000 ; expire
6400 ; minimum TTL
)
;
; Zone NS Records
;