DNS adding reverse zone issue (tested on FD 1.0.10) in class B and class A

Hi, I have upgraded my 1.0.9.3 FD to 1.0.10 and everything went good. But when I tried to add new Reverse Zone that does not work. The same issue is with new DNS zone created at demo.fusiondirectory.org

Reproduction steps: -Goto Systems/DNS in left Main menu -click on existing zone (ie. testzone.dom) -in reverse zones add 168.192.in-addr.arpa. -click Apply and you will see there is no more your added reverse zone in list.

This mean you can not add new reverse zones and apply them.

Thanks.

(from redmine: issue id 4630, created on 2016-03-21, closed on 2016-03-23)

• Changesets:
  • Revision be3a106f by Côme Chilliet on 2016-03-22T05:42:53.000Z:

Fixes #4630 reverse zone was not saved if records are not modified

• Revision ce94ff26 by Côme Chilliet on 2016-03-22T05:45:21.000Z:

Fixes #4630 reverse zone was not saved if records are not modified

• Custom Fields:
  • Bug in version: 1.0.10
• Uploads:
  • class c
  • class c

Additional info:

• if I manually (with Apache Directory Studio) edit ldap tree and add reverse zone, then that reverse zone is shown in reverse zone list.

BUT still if I try to delete any existing reverse zones, after APPLY they are not deleted (like you have read only perms on them) and also if you want to create new reverse zone, after Apply there is no more that zone in list.

(from redmine: written on 2016-03-21)

hello,

tested this and this seem to reproduce when the reverse is not in class c mode, because in class C its works like show in the attached screenshot

we will look into it

Cheers

(from redmine: written on 2016-03-21)

I have tested with class C and it works, but please fix it to work with /16 or even with /8 (10.x.x.x subnet).

(from redmine: written on 2016-03-21)

The problem I was able to reproduce is the following: If I add a reverse zone and do not modify any record, the reverse zone is not saved.

But if I add a reverse and use it for a A record, it’s correctly saved. even for B or A class.

I checked on demo.fusiondirectory.org and it’s the same behaviour, you have to modify at least one record for reverse zone modification to be saved. Fix incomming, but in the mean time the work around is just to modify a record when adding/removing reverse zones.

(from redmine: written on 2016-03-22)

Fixed.

An other effect of this bug was that when renaming a zone all records but the root ones were lost, if no record was modified.

(from redmine: written on 2016-03-22)

Say on IRC that it was fixed.

Close issue

(from redmine: written on 2016-03-23)

closed

added Fixed label