Bug 461300

Summary: Client install does not function properly on networks that use AD DNS.
Product: [Retired] freeIPA Reporter: Zak Berrie <zbrown>
Component: ipa-clientAssignee: David O'Brien <daobrien>
Status: CLOSED DUPLICATE QA Contact: Chandrasekar Kannan <ckannan>
Severity: high Docs Contact:
Priority: medium    
Version: 1.0CC: benl, dpal, jgalipea, liko
Target Milestone: v2 releaseKeywords: Documentation
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 646204 (view as bug list) Environment:
Last Closed: 2010-11-25 23:03:50 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 431020, 489811, 646204, 646217    

Description Zak Berrie 2008-09-05 17:42:51 UTC
The ipa-client-install command is unable to find the IPA server on a network that uses AD DNS.

Comment 1 Brian Likosar 2008-12-23 16:27:10 UTC
This is probably due to the fact that AD has its own SRV records for kerberos and ldap that it adds in, so ipa-client-install gets those records instead of any that you might have added for IPA.

Comment 4 Rob Crittenden 2010-09-14 16:33:02 UTC
David, the problem is that we can't know that the SRV records are not for IPA. Please ensure that this it is documented that when running ipa-client-install in an AD environment you may have to manually provide the server to use.

Comment 5 David O'Brien 2010-11-25 23:03:50 UTC

*** This bug has been marked as a duplicate of bug 646204 ***