#1591 ipa-server-install creates wrong reverse zone record in LDAP
Closed: Fixed None Opened 10 years ago by dpal.


Description of problem:
ipa-server-install creates wrong reverse zone record in LDAP

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. run ipa-server-install --selfsign --setup-dns --forwarder <ip>
2. select that you want to create reverse zone

Actual results:
Reverse zone record in LDAP looks:

# 24.34.10.in-addr.arpa., dns, atkac.brq.redhat.com
dn: idnsname=24.34.10.in-addr.arpa.,cn=dns,dc=atkac,dc=brq,dc=redhat,dc=com
idnsZoneActive: TRUE
idnsSOAexpire: 1209600
nSRecord: ipa.atkac.brq.redhat.com.
idnsSOAserial: 2011080801
idnsSOAretry: 900
idnsSOAminimum: 3600
idnsUpdatePolicy: grant ATKAC.BRQ.REDHAT.COM krb5-subdomain 24.34.10.in-addr.a
 rpa.. PTR;
idnsSOArefresh: 3600
objectClass: top
objectClass: idnsrecord
objectClass: idnszone
idnsName: 24.34.10.in-addr.arpa.
idnsAllowDynUpdate: TRUE
idnsSOArName: root.24.34.10.in-addr.arpa.
idnsSOAmName: ipa.atkac.brq.redhat.com.

Please check the idnsUpdatePolicy attribute. It contains "24.34.10.in-addr.a
 rpa.. PTR" which contains double dot. It is wrong, FQDN must be terminated
only with one dot.

Expected results:
idnsUpdatePolicy attribute contains FQDN with only one dot. In my case it will

idnsUpdatePolicy: grant ATKAC.BRQ.REDHAT.COM krb5-subdomain
24.34.10.in-addr.arpa. PTR;

I would like this ticket to get to 2.1 - if the review is made in time.

Metadata Update from @dpal:
- Issue assigned to mkosek
- Issue set to the milestone: FreeIPA 2.1 - 2011/07

5 years ago

Login to comment on this ticket.