Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
When an IPA server is added to a certain location, CNAME records are supposed to replace the following SRV records:
_ldap._tcp.example.com.
_kerberos._tcp.example.com.
_kerberos._udp.example.com.
_kerberos-master._tcp.example.com.
_kerberos-master._udp.example.com.
_kpasswd._tcp.example.com.
_kpasswd._udp.example.com.
However, in the majority of cases, these records are not replaced:
$ dig @server-a.example.com _kerberos._udp.example.com. SRV +noall +answer
_kerberos._udp.example.com. 86400 IN SRV 0 100 88 server-a.example.com.
_kerberos._udp.example.com. 86400 IN SRV 0 100 88 server-b.example.com.
While it should be:
$ dig @server-a.example.com _kerberos._udp.example.com. SRV +noall +answer
_kerberos._udp.example.com. 86400 IN CNAME _kerberos._udp.a._locations.example.com.
_kerberos._udp.a._locations.example.com. 86400 IN SRV 0 100 88 server-a.example.com.
_kerberos._udp.a._locations.example.com. 86400 IN SRV 50 100 88 server-b.example.com.
The issue seems to be occurring during the synchronization from 389ds to bind9, because the CNAME template is there:
$ ldapsearch -H ldaps://server-a.example.com -QY GSSAPI -LLL -o ldif-wrap=no -s one -b 'idnsname=example.com.,cn=dns,dc=example,dc=com' idnsTemplateAttribute
dn: idnsname=_ldap._tcp,idnsname=example.com.,cn=dns,dc=example,dc=com
idnsTemplateAttribute;cnamerecord: _ldap._tcp.\{substitutionvariable_ipalocation\}._locations
dn: idnsname=_kerberos._tcp,idnsname=example.com.,cn=dns,dc=example,dc=com
idnsTemplateAttribute;cnamerecord: _kerberos._tcp.\{substitutionvariable_ipalocation\}._locations
dn: idnsname=_kerberos._udp,idnsname=example.com.,cn=dns,dc=example,dc=com
idnsTemplateAttribute;cnamerecord: _kerberos._udp.\{substitutionvariable_ipalocation\}._locations
dn: idnsname=_kerberos-master._tcp,idnsname=example.com.,cn=dns,dc=example,dc=com
idnsTemplateAttribute;cnamerecord: _kerberos-master._tcp.\{substitutionvariable_ipalocation\}._locations
dn: idnsname=_kerberos-master._udp,idnsname=example.com.,cn=dns,dc=example,dc=com
idnsTemplateAttribute;cnamerecord: _kerberos-master._udp.\{substitutionvariable_ipalocation\}._locations
dn: idnsname=_kpasswd._tcp,idnsname=example.com.,cn=dns,dc=example,dc=com
idnsTemplateAttribute;cnamerecord: _kpasswd._tcp.\{substitutionvariable_ipalocation\}._locations
dn: idnsname=_kpasswd._udp,idnsname=example.com.,cn=dns,dc=example,dc=com
idnsTemplateAttribute;cnamerecord: _kpasswd._udp.\{substitutionvariable_ipalocation\}._locations
On IPA servers, there are no traces of locations-related CNAME records in /var/named/data/update.log log file.
The zone dump in /var/named/dyndb-ldap/ipa/master/example.com/raw does not contain expected CNAME records either.
CNAME records are created when configuration and zones are reloaded manually
# rndc reload
However this command is not supposed to have impact on dynamic zones:
# rndc reload example.com.
rndc: 'reload' failed: dynamic zone
It seems that when assigning a location to a server, the bind9 configuration has to be reloaded using "rndc reconfig" (reloading the configuration after server installation is not enough).
When an IPA server is added to a certain location, CNAME records are supposed to replace the following SRV records: _ldap._tcp.example.com. _kerberos._tcp.example.com. _kerberos._udp.example.com. _kerberos-master._tcp.example.com. _kerberos-master._udp.example.com. _kpasswd._tcp.example.com. _kpasswd._udp.example.com. However, in the majority of cases, these records are not replaced: $ dig @server-a.example.com _kerberos._udp.example.com. SRV +noall +answer _kerberos._udp.example.com. 86400 IN SRV 0 100 88 server-a.example.com. _kerberos._udp.example.com. 86400 IN SRV 0 100 88 server-b.example.com. While it should be: $ dig @server-a.example.com _kerberos._udp.example.com. SRV +noall +answer _kerberos._udp.example.com. 86400 IN CNAME _kerberos._udp.a._locations.example.com. _kerberos._udp.a._locations.example.com. 86400 IN SRV 0 100 88 server-a.example.com. _kerberos._udp.a._locations.example.com. 86400 IN SRV 50 100 88 server-b.example.com. The issue seems to be occurring during the synchronization from 389ds to bind9, because the CNAME template is there: $ ldapsearch -H ldaps://server-a.example.com -QY GSSAPI -LLL -o ldif-wrap=no -s one -b 'idnsname=example.com.,cn=dns,dc=example,dc=com' idnsTemplateAttribute dn: idnsname=_ldap._tcp,idnsname=example.com.,cn=dns,dc=example,dc=com idnsTemplateAttribute;cnamerecord: _ldap._tcp.\{substitutionvariable_ipalocation\}._locations dn: idnsname=_kerberos._tcp,idnsname=example.com.,cn=dns,dc=example,dc=com idnsTemplateAttribute;cnamerecord: _kerberos._tcp.\{substitutionvariable_ipalocation\}._locations dn: idnsname=_kerberos._udp,idnsname=example.com.,cn=dns,dc=example,dc=com idnsTemplateAttribute;cnamerecord: _kerberos._udp.\{substitutionvariable_ipalocation\}._locations dn: idnsname=_kerberos-master._tcp,idnsname=example.com.,cn=dns,dc=example,dc=com idnsTemplateAttribute;cnamerecord: _kerberos-master._tcp.\{substitutionvariable_ipalocation\}._locations dn: idnsname=_kerberos-master._udp,idnsname=example.com.,cn=dns,dc=example,dc=com idnsTemplateAttribute;cnamerecord: _kerberos-master._udp.\{substitutionvariable_ipalocation\}._locations dn: idnsname=_kpasswd._tcp,idnsname=example.com.,cn=dns,dc=example,dc=com idnsTemplateAttribute;cnamerecord: _kpasswd._tcp.\{substitutionvariable_ipalocation\}._locations dn: idnsname=_kpasswd._udp,idnsname=example.com.,cn=dns,dc=example,dc=com idnsTemplateAttribute;cnamerecord: _kpasswd._udp.\{substitutionvariable_ipalocation\}._locations