Error message for wrong domain or wrong AD servername used is similar[[BR]]
[root@wazwan ~]# ipa trust-add --type=ad badadlabs.com --admin Administrator --password Active directory domain administrator's password: ipa: ERROR: Unable to resolve domain controller for 'badadlabs.com' domain. Additional instructions: IPA manages DNS, please verify your DNS configuration and make sure that service records of the 'badadlabs.com' domain can be resolved. Examples how to configure DNS with CLI commands or the Web UI can be found in the documentation. [root@wazwan ~]# ipa trust-add --type=ad adlabs.com --admin Administrator --password --server=zombie.adlabs.com Active directory domain administrator's password: ipa: ERROR: Unable to resolve domain controller for 'adlabs.com' domain. Additional instructions: Forward policy is defined for it in IPA DNS, perhaps forwarder points to incorrect host? [root@wazwan ~]# dig +short SRV _ldap._tcp.adlabs.com 0 100 389 win-i94qhqmthd4.adlabs.com. [root@wazwan ~]# ipa trust-add --type=ad adlabs.com --admin Administrator --password --server=win-i94qhqmthd4.adlabs.com Active directory domain administrator's password: --------------------------------------------------- Added Active Directory trust for realm "adlabs.com" --------------------------------------------------- Realm name: adlabs.com Domain NetBIOS name: ADLABS Domain Security Identifier: S-1-5-21-3069109027-1612402048-776712048 SID blacklist incoming: S-1-0, S-1-1, S-1-2, S-1-3, S-1-5-1, S-1-5-2, S-1-5-3, S-1-5-4, S-1-5-5, S-1-5-6, S-1-5-7, S-1-5-8, S-1-5-9, S-1-5-10, S-1-5-11, S-1-5-12, S-1-5-13, S-1-5-14, S-1-5-15, S-1-5-16, S-1-5-17, S-1-5-18, S-1-5-19, S-1-5-20 SID blacklist outgoing: S-1-0, S-1-1, S-1-2, S-1-3, S-1-5-1, S-1-5-2, S-1-5-3, S-1-5-4, S-1-5-5, S-1-5-6, S-1-5-7, S-1-5-8, S-1-5-9, S-1-5-10, S-1-5-11, S-1-5-12, S-1-5-13, S-1-5-14, S-1-5-15, S-1-5-16, S-1-5-17, S-1-5-18, S-1-5-19, S-1-5-20 Trust direction: Two-way trust Trust type: Active Directory domain Trust status: Established and verified
Is this better contained in a FAQ rather than hardcoding tips into error messages?
Rename "trusts" component to "Trusts" to achieve correct sorting.
Moving open tickets to next month bucket.
Decreasing priority, this is just an error message improvement.
We no longer have capacity in 3.3 development, moving to 3.4.
3.4 development was shifted by one month, moving tickets to reflect reality better.
Adjusting time plan - 3.4 development was postponed as we focused on 3.3.x testing and stabilization.
Moving unfinished November tickets to January.
No one picked that effort. Given the low priority and scope of this change, I am moving it to Future Releases.
Metadata Update from @steeve: - Issue assigned to someone - Issue set to the milestone: Future Releases
Login to comment on this ticket.