Bug 1206607

Summary:	[RFE] IPA servers when installed should register themselves in the external DNS
Product:	Red Hat Enterprise Linux 9	Reporter:	Martin Kosek <mkosek>
Component:	ipa	Assignee:	Florence Blanc-Renaud <frenaud>
Status:	ASSIGNED ---	QA Contact:	ipa-qe <ipa-qe>
Severity:	unspecified	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	abokovoy, afarley, asakure, fcami, fperalta, jappleii, ldelouw, pasik, pvoborni, rcritten, shetze, smeyer, tscherf
Target Milestone:	beta	Keywords:	FutureFeature, PrioBumpPM, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Feature Request
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:	1214827
Bug Blocks:

Description Martin Kosek 2015-03-27 13:49:50 UTC

This bug is created as a clone of upstream ticket:
https://fedorahosted.org/freeipa/ticket/4424

When IPA is installed in the environment managed by some other DNS server and IPA DNS is not used then IPA should update its DNS entries in this external DNS during installation.

We should make IPA servers send update requests to create/store SRV/TXT/other
records needed by FreeIPA itself to a separate DNS infrastructure. This is
missing. The framework can use TSIG (not necessarily GSS-TSIG) updates to a different DNS server when replicas are added/removed/changed.

Comment 4 Akshay Sakure 2016-07-13 09:45:49 UTC

Hello Martin,

This RFE looks like to be addressed for IPA server when it is installed with external DNS server its records shoudl be updated in DNS.

Do you think that a separate RFE should be filed to address similar issue from ipa-client point of view so that whenever, ipa client is installed (using ipa-client-install) it should update its DNS records in external DNS server(may be using 'nsupdate') ?

Thanks in advance!!!

Comment 5 Martin Kosek 2016-07-14 07:18:38 UTC

Good question. We probably have several use cases to be considered:

1) client DNS zone is managed by IPA, client is joined to IPA --> should work already
2) client DNS zone is managed by AD, client is joined to AD --> should work already
3) client DNS zone is managed by AD, client is joined to IPA, IPA-AD are in trust --> to be investigated
4) client DNS zone is managed by external DNS, clients are joined to IPA --> I assume this should work already also, but not sure.

Petr Spacek, can you please comment on above? Do you want to handle RFEs for these scenarios in separate Bugzilla?

Comment 6 Petr Spacek 2016-07-18 07:41:11 UTC

(In reply to Martin Kosek from comment #5)
> 1) client DNS zone is managed by IPA, client is joined to IPA --> should
> work already
Definitelly.

> 2) client DNS zone is managed by AD, client is joined to AD --> should work
> already
AFAIK there is not way to join ipa-client to AD domain to this sounds like invalid use case to me.

> 3) client DNS zone is managed by AD, client is joined to IPA, IPA-AD are in
> trust --> to be investigated
This will certainly not work. IPA does not add 'Domain Computers' membership SID to PAC issued to 'host/' principals from IPA domain. In the end this means that AD refuses all the updates from clients joined to IPA.

This can be changed if we decide so (but it can work only with bi-directional trust).


> 4) client DNS zone is managed by external DNS, clients are joined to IPA -->
> I assume this should work already also, but not sure.

This depends on configuration of external DNS. External DNS servers need to be joined to IPA domain and configured for GSS-API authentication.

> Petr Spacek, can you please comment on above? Do you want to handle RFEs for
> these scenarios in separate Bugzilla?
I would create separate RFE for each client use-case which is not covered yet.

Comment 7 Martin Kosek 2016-07-18 08:11:32 UTC

(In reply to Petr Spacek from comment #6)
> (In reply to Martin Kosek from comment #5)
...
> > 2) client DNS zone is managed by AD, client is joined to AD --> should work
> > already
> AFAIK there is not way to join ipa-client to AD domain to this sounds like
> invalid use case to me.

By "client", I actually meant SSSD. Sorry for confusion.

> > 3) client DNS zone is managed by AD, client is joined to IPA, IPA-AD are in
> > trust --> to be investigated
> This will certainly not work. IPA does not add 'Domain Computers' membership
> SID to PAC issued to 'host/' principals from IPA domain. In the end this
> means that AD refuses all the updates from clients joined to IPA.
> 
> This can be changed if we decide so (but it can work only with
> bi-directional trust).

Ok, I filed Bug 1357429.

> > 4) client DNS zone is managed by external DNS, clients are joined to IPA -->
> > I assume this should work already also, but not sure.
> 
> This depends on configuration of external DNS. External DNS servers need to
> be joined to IPA domain and configured for GSS-API authentication.

I this something that can be configured with DNS boxes like Infoblox or cloud DNS servers like AWS Route 53 or OpenStack Designate?

Comment 8 Petr Spacek 2016-07-18 14:14:25 UTC

(In reply to Martin Kosek from comment #7)
> (In reply to Petr Spacek from comment #6)
> > (In reply to Martin Kosek from comment #5)
> > > 2) client DNS zone is managed by AD, client is joined to AD --> should work
> > > already
> > AFAIK there is not way to join ipa-client to AD domain to this sounds like
> > invalid use case to me.
> 
> By "client", I actually meant SSSD. Sorry for confusion.
Okay, DNS updates from SSSD joined directly to AD must work already.


> > > 4) client DNS zone is managed by external DNS, clients are joined to IPA -->
> > > I assume this should work already also, but not sure.
> > 
> > This depends on configuration of external DNS. External DNS servers need to
> > be joined to IPA domain and configured for GSS-API authentication.
> 
> I this something that can be configured with DNS boxes like Infoblox or
> cloud DNS servers like AWS Route 53 or OpenStack Designate?

This needs to be answered on case-by-case basics. I just played with Infoblox 6.12 and is able to import keytab generated by IPA so it should just work.

AFAIK Amazon does not support it.