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.

Document URL: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/windows_integration_guide/trust-during#dns-realm-settings

Section Number and Name: 5.2.1.2. DNS and Realm Settings

Describe the issue: The Note talks about the bug that is currently already fixed.

Suggestions for improvement: Change the wording of the note mentioning that there was an issue but it is already addressed in 7.5.

Additional information:

(In reply to Dmitri Pal from comment #0)
> Document URL:
> https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/
> html/windows_integration_guide/trust-during#dns-realm-settings
> 
> Section Number and Name: 5.2.1.2. DNS and Realm Settings
> 
> Describe the issue: The Note talks about the bug that is currently already
> fixed.
> 
> Suggestions for improvement: Change the wording of the note mentioning that
> there was an issue but it is already addressed in 7.5.
> 
> Additional information:

Hi Dmitri,

After discussing the possibilities with other, more senior writers and with the subsystem at the weekly meeting, I propose to deal with this issue in the following way:
a/ Write a release note for BZ#1421869;
b/ extend the list in WIG, adding a link to the RN as follows:
"""
 Each system must have its own unique primary DNS domain configured. For example:

    ad.example.com for AD and idm.example.com for IdM
    example.com for AD and idm.example.com for IdM 
    ad.example.com for AD and example.com for IdM (__link to the RN__)
"""

I hope this solution is OK for you.

The update is now available on the Customer Portal.