https://bugzilla.redhat.com/show_bug.cgi?id=818764 (Red Hat Enterprise Linux 6)
Description of problem: Since there is no value check for "Record name", user can create PTR record like this: ptr201 PTR 192.168.122.201 Please check screen shot for details Version-Release number of selected component (if applicable): [yi@fig (RH6.3-x86_64) /] rpm -qi ipa-server Name : ipa-server Relocations: (not relocatable) Version : 2.2.0 Vendor: Red Hat, Inc. Release : 12.el6 Build Date: Mon 30 Apr 2012 11:52:52 AM PDT Install Date: Wed 02 May 2012 11:00:38 AM PDT Build Host: x86-004.build.bos.redhat.com Group : System Environment/Base Source RPM: ipa-2.2.0-12.el6.src.rpm Size : 3778371 License: GPLv3+ Signature : (none) Packager : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla> URL : http://www.freeipa.org/ Summary : The IPA authentication server How reproducible: always Steps to Reproduce: 1. Go to Identity->DNS->DNS ZONES 2. select one reverse dns zone 3. click "Add" to add one new record (a new dialog will pop up) 4. for Record name, enter "test" 5. for Record Type: select "PTR" 6. for Hostname, enter "test.redhat.com" 7. Click "Add" button to add this record Actual results: record being created Expected results: data being rejected Additional info: please check screenshot
Situation similar to #2712:
Actually, all record types, names and values are allowed in DNS. We should not disallow them, just give a hint to user.
We can issue some kind of warning, if our assumptions are not met. See #2732 about warnings.
Moving my tickets back to free-to-take pool.
Metadata Update from @mkosek: - Issue assigned to someone - Issue set to the milestone: Tickets Deferred
Thank you taking time to submit this request for FreeIPA. Unfortunately this bug was not given priority and the team lacks the capacity to work on it at this time.
Given that we are unable to fulfil this request I am closing the issue as wontfix. To request re-consideration of this decision please reopen this issue and provide additional technical details about its importance to you.
Metadata Update from @rcritten: - Issue close_status updated to: wontfix - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.