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 1310013 - DNS server installation procedures are missing last step: DNS delegation
Summary: DNS server installation procedures are missing last step: DNS delegation
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: doc-Linux_Domain_Identity_Management_Guide
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Aneta Šteflová Petrová
QA Contact: Namita Soman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-19 09:23 UTC by Petr Spacek
Modified: 2019-03-06 00:56 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-18 13:46:05 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Petr Spacek 2016-02-19 09:23:03 UTC
Description of problem:
Section
⁠3.2.4.1. Installing with an Integrated DNS Service Interactively
(Current) Last step of the procedure should be followed by additional step:

and

⁠3.2.4.2. Installing with an Integrated DNS Service Non-Interactively
(Current) Last step of the procedure should be followed by additional step:

---
9. Add DNS delegation from parent domain to the IdM DNS domain. E.g. if the IdM DNS domain is named ipa.example.com, the delegation (NS record) needs to be added into parent domain example.com.

This step needs to be repeated each time a IdM DNS server is installed or uninstalled.
---

Actual results:
User might omit DNS delegation step which will case hard-to-debug breakage later on.

Expected results:
We should remind the user to do DNS delegation properly.

Comment 2 Aneta Šteflová Petrová 2016-02-24 07:06:52 UTC
Step 9 of "Installing with Integrated DNS Interactively" and step 7 of "Installing with Integrated DNS Non-Interactively" (both are part of section 3.2.4. Configuring DNS Services) now include the following:

-----
Add DNS delegation from the parent domain to the IdM DNS domain. For example, if the IdM DNS domain is ipa.example.com, add a name server (NS) record to the example.com parent domain to ensure the delegation.
Note that this step must be repeated each time an IdM DNS server is installed. 
-----

In addition, 3.3. Uninstalling an IdM Server now includes:

-----
If the server included integrated DNS, update the name server (NS) records in the parent domain to ensure they do not point to the uninstalled server. 
-----

The SME acked the updated, so I'm moving this BZ directly to VERIFIED.

Comment 4 Aneta Šteflová Petrová 2016-04-18 13:46:05 UTC
The update is available on the Customer Portal.


Note You need to log in before you can comment on or make changes to this bug.