[DNS plugin] Reverse DNS Zones unusable with bind-sdb

In FD 1.0.20 an option can be use to store, or not, a final dot to the zoneName ("Issue 2636":https://forge.fusiondirectory.org/issues/2636)

With bind-sdb it is necessary to not store the zoneName with a final dot, but this option is active to the reverses zones too. For the reverse zones, if the zoneName (in-addr.arpa) doesn't have a final dot, bind add the domain name to the value it returned.

for example: test.example.com -> 1.0.168.192.in-addr.arpa.example.com

To sum up, for Bind-sdb a zoneName need to not have a final dot and a reverse zone need to have a final dot (in-addr.arpa.)

(from redmine: issue id 5484, created on 2017-04-25, closed on 2017-05-02)

• Changesets:
  • Revision 2e52d318 by Côme Chilliet on 2017-04-25T13:35:08.000Z:

Fixes #5484 Adding final dot to PTR records ignoring the dns final dot setting

• Revision d53ffb9f6192670f6a9eb516dcaeb81c6e0c0515 by Côme Chilliet on 2017-04-26T07:37:19.000Z:

Fixes #5484 Adding final dot to PTR records ignoring the dns final dot setting

• Custom Fields:
  • Bug in version: 1.0.20
  • Support contract: None

In FD 1.0.20 an option can be use to store, or not, a final dot to the zoneName ("Issue 2636":https://forge.fusiondirectory.org/issues/2636)

With bind-sdb, it's necessary to store the pTRRecord with a final dot even if the zone name is not store withe a final dot.

For the reverse zones, if the pTRRecord(in-addr.arpa) doesn't have a final dot, bind add the domain name to the value it returned.

for example: 192.168.0.1 -> "test.example.com.in-addr.arpa." instead of "test.example.com."

To sum up, for Bind-sdb a aRecord need to not have a final dot and for a reverse zone the pTRRecord need to have a final dot (test.example.com.)

(from redmine: written on 2017-04-25)

Could you give a short example of which LDAP fields will need to contain the final dot and which will not?

(from redmine: written on 2017-04-25)

Applied in changeset commit:fusiondirectory-plugins|2e52d318.

(from redmine: written on 2017-04-25)

Can you test on demo-dev.fusiondirectory.org and tell me if it’s correct? (You’ll need to first edit the configuration to deactivate the final dot)

(from redmine: written on 2017-04-25)

Sorry for the late answer.

The working example is the configuration with the "Store final dot in domains" option unchecked, and the field pTRRecord with a final dot.

The demo-dev.fusiondirectory.org seems to store the good value but i can only test tomorrow at work. I will confirm you the modification.

(from redmine: written on 2017-04-25)

I tried this morning, but my problem is that i'm using the 1.0.20 packages version for centos, so i applied the diff which are related to the "$zoneNameWithFinalDot" modifications, and it work like a charm.

Is it possible to add the 1.1 dns plugin to an 1.0.20 installation ?

Thanks for this really really fast correction.

(from redmine: written on 2017-04-26)

The fix was integrated in 1.0.20-fixes, you can use this repo: https://integration.fusiondirectory.org/repos/fixes-releases/rpm/

(from redmine: written on 2017-04-26)

Applied in changeset commit:fusiondirectory-plugins|d53ffb9f6192670f6a9eb516dcaeb81c6e0c0515.

(from redmine: written on 2017-04-26)

I tried the 1.0.20 fixed version and it works perfectly.

(from redmine: written on 2017-05-01)

Close issue

(from redmine: written on 2017-05-02)

closed

added Fixed label

removed Bugs label

added PJ1802-0188 label