Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1314837
Description of problem: Running `ipa-server-install --forwarder=<host>` creates an entry in /etc/named.conf and a working configuration, however it does not place that entry in 389 Directory, making therefore inaccessible by the IdM Web UI and the `ipa dnsconfig-show` command. Version-Release number of selected component (if applicable): IdM 4.2.0 on RHEL 7.2 How reproducible: Tested once Steps to Reproduce: 1. Set up an IdM Sever and specify DNS forwarder. # ipa-server-install --forwarder=<host> 2. Validate the forwarder host is present in /etc/named.conf [GOOD] 3. Validate name resolution requiring forwarder using dig [GOOD] Note: pcap confirms resolution is using forwarders 4) Probe 389 Directory for forwarder entries [BROKEN] # ipa dnsconfig-show EXPECTED: display forwarder host address 5) Probe WebUI for forwarder entries [BROKEN] Network Services > DNS > DNS Global Configuration EXPECTED: display forwarder host address Actual results: no forwarder host address displayed Expected results: display forwarder host address Additional info: We configured IPA server to use 2 DNS forwarders.
Will be side effect of DNS locations.
This part in #2008 is ready and can be consumed by webUI
We need to add upgrade path for #2008 so the values show in Web UI even for upgraded servers.
master:
We decided to split upgrade into separate ticket:5997.
Metadata Update from @pvoborni: - Issue assigned to pvomacka - Issue set to the milestone: FreeIPA 4.4
Login to comment on this ticket.