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.
Bug 2111181 - CNAME records missing in DNS of locations-enabled domain
Summary: CNAME records missing in DNS of locations-enabled domain
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: ipa
Version: 9.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Julien Rische
QA Contact: ipa-qe
URL:
Whiteboard:
Depends On:
Blocks: 2104185 2148382
TreeView+ depends on / blocked
 
Reported: 2022-07-26 16:29 UTC by Julien Rische
Modified: 2022-11-25 09:31 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-10-31 09:52:25 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker FREEIPA-8567 0 None None None 2022-07-26 16:32:43 UTC
Red Hat Issue Tracker RHELPLAN-129139 0 None None None 2022-07-26 16:32:49 UTC

Description Julien Rische 2022-07-26 16:29:57 UTC 
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
Comment 2 Julien Rische 2022-07-27 14:15:10 UTC 
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.
Comment 3 Julien Rische 2022-07-27 15:10:25 UTC 
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
Comment 4 Julien Rische 2022-07-27 16:30:28 UTC 
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).
Comment 5 Julien Rische 2022-10-31 09:52:25 UTC 
This is actually not a bug. Restarting bind9 is required after assigning a location to a server, as explained in the documentation:

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/working_with_dns_in_identity_management/managing-dns-locations-in-idm_working-with-dns-in-identity-management#assigning-an-idm-server-to-a-dns-location-using-the-idm-web-ui_managing-dns-locations-in-idm
Note You need to log in before you can comment on or make changes to this bug.