Bug 813383 - [Web UI] Do not offer A/AAAA records in a root zone record
[Web UI] Do not offer A/AAAA records in a root zone record
Status: CLOSED DEFERRED
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa (Show other bugs)
7.0
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Martin Kosek
IDM QE LIST
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-04-17 11:41 EDT by Dmitri Pal
Modified: 2015-01-21 10:07 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-01-21 10:07:08 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Dmitri Pal 2012-04-17 11:41:26 EDT
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/freeipa/ticket/2633

Web UI currently offers A/AAAA/CNAME records as "Standard records" in DNS zone root record ("@"). But it generally does not make much sense to have these records in the zone record (especially for the CNAME record).

We should rather offer records standard for zone record, like NS, MX or LOC. CLI interactive help already does that. You can check it with:

{{{
# ipa dnsrecord-add example.com @
}}}
Comment 6 Martin Kosek 2015-01-21 10:07:08 EST
Thank you taking your time and submitting this request for Red Hat Enterprise Linux. Unfortunately, this bug was not given a priority and was deferred both in the upstream project and in Red Hat Enterprise Linux.

Given that we are unable to fulfill this request in following Red Hat Enterprise Linux releases, I am closing the Bugzilla as DEFERRED. To request that Red Hat re-considers the decision, please re-open the Bugzilla via appropriate support channels and provide additional business and/or technical details about its importance to you.

Note that you can still track this request or even contribute patches in the referred upstream Trac ticket.

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