Bug 783287

Summary: Check configured DNS servers during ipa-client-install
Product: Red Hat Enterprise Linux 6 Reporter: Dmitri Pal <dpal>
Component: doc-Identity_Management_GuideAssignee: Deon Ballard <dlackey>
Status: CLOSED CURRENTRELEASE QA Contact: ecs-bugs
Severity: medium Docs Contact:
Priority: medium    
Version: 6.3CC: jskeoch, mkosek
Target Milestone: rcKeywords: Documentation
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-07-09 20:34:05 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Dmitri Pal 2012-01-19 20:49:48 UTC
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/freeipa/ticket/1408

If a client is in a subnet not controlled by an IPA DNS server then the nsupdate may fail to add the client.

One option would be to perform a DNS query to see who is authoritative for the reverse zone and warn the user if it is not one of the IPA servers.

We'd also have to see if DNS is configured in IPA at all. The IPA servers can be found in cn=masters,cn=ipa,cn=etc,$BASEDN.

Comment 3 John Skeoch 2012-07-06 01:17:00 UTC
Verified the additional troubleshooting in:

http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Identity_Management_Guide/troubleshooting-client-install.html#id4629718

Red_Hat_Enterprise_Linux-Identity_Management_Guide-6-en-US-2.2.0-2

---