This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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.
Bug 1206607 - [RFE] IPA servers when installed should register themselves in the external DNS
Summary: [RFE] IPA servers when installed should register themselves in the external DNS
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: ipa
Version: unspecified
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: beta
: ---
Assignee: Florence Blanc-Renaud
QA Contact: ipa-qe
URL:
Whiteboard:
Depends On: 1214827
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-27 13:49 UTC by Martin Kosek
Modified: 2023-12-15 15:49 UTC (History)
14 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-18 17:47:56 UTC
Type: Story
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker FREEIPA-7858 0 None None None 2022-02-16 12:12:32 UTC
Red Hat Issue Tracker   RHEL-4802 0 None Migrated None 2023-09-18 17:47:37 UTC

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.
Comment 42 RHEL Program Management 2023-09-18 17:45:40 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 43 RHEL Program Management 2023-09-18 17:47:56 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.