Bug 1328811

Summary: [RFE] ipa-{server,replica,dns}-installshould preserve include files in /etc/named.conf
Product: Red Hat Enterprise Linux 8 Reporter: Luc de Louw <ldelouw>
Component: ipaAssignee: Thomas Woerner <twoerner>
Status: CLOSED WONTFIX QA Contact: ipa-qe <ipa-qe>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.0CC: mkosek, pasik, pcech, pvoborni, rcritten, tscherf
Target Milestone: rcKeywords: FutureFeature
Target Release: 8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-09 12:47:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Luc de Louw 2016-04-20 10:34:56 UTC
Description of problem:

Since ipa does not support native LDAP based DNS slave mode, some organization are adding file based slave DNS conifgurations in /etc/named.conf i.e. adding include "/etc/named.external.zones.conf"; where out-of-band slave zones are configured. 

However, ipa-{server,replica,dns}-install overwrites named.conf. 


Version-Release number of selected component (if applicable):
4.2

How reproducible:
Always

Steps to Reproduce:
1. alter named.conf
2. run ipa-{server,replica,dns}-install
3. find named.conf with removed include statement

Actual results:


Expected results:
include statements in /etc/named.conf should be preserved when running ipa-{server,replica,dns}-install 

Additional info:
Slave DNS support via LDAP was NACKed in upstream ticket https://fedorahosted.org/freeipa/ticket/5364 
Configuring named.conf is a nice workaround.

Comment 2 Petr Vobornik 2016-04-28 13:36:26 UTC
Upstream ticket:
https://fedorahosted.org/freeipa/ticket/5858

Comment 3 Petr Vobornik 2016-04-28 13:38:26 UTC
Fixing it will require replacing legacy regexes with proper named.conf parser, e.g. augeas. It is out of scope of upcoming 4.4 upstream release and therefore the upstream ticket was triaged in "Future releases" milestone.

Comment 7 Petr Čech 2020-07-09 12:47:06 UTC
Thank you taking your time and submitting this request for Red Hat Enterprise Linux. It was unfortunately not given priority Red Hat Enterprise Linux.
Given that this request is not planned for a close release, it is highly unlikely it will be fixed in this major version of Red Hat Enterprise Linux. We are therefore closing the request as WONTFIX.
To request that Red Hat reconsiders the decision, please reopen the Bugzilla with the help of Red Hat Customer Service and provide additional business and/or technical details about it's importance to you.