#4957 IdM - Add DNS Resource Record - Unexpected behavior (A added even if PTR failed)
Closed: wontfix 5 years ago Opened 9 years ago by pvoborni.

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1202187

Please note that this Bug is private and may not be accessible as it contains confidential Red Hat customer information.

Description of problem:
Using the IdM interface "Add DNS Resource Record":
Adding an A record entry and checking the box to create the reverse (ptr)
record.
If the reverse zone doesn't exist, an error appears, but the A record is still
created.


Version-Release number of selected component (if applicable):
IdM on RHEL7

How reproducible:
Consistent

Steps to Reproduce:
1. In the IdM interface: Network Services > DNS
2. Click on a zone to view its entries, and click "+Add" to add a new record.
3. Complete the "Record name" and "IP address" details. Record Type=A, "Create
reverse" is checked. For the IP address entry, ensure the address isn't covered
by a reverse zone.
4. Click Add.

Actual results:
Receive the error below (substitute x.x.x.x for the IP address you chose):

"Cannot create reverse record for "x.x.x.x": DNS reverse zone for IP address
x.x.x.x not found"

However, the A record is still created.

Expected results:
I would expect the IdM interface to view this process as a single transaction,
where the failure to add a reverse record would result in the A record not
being created either.

Additional info:

Not critical.

Since PTR record is not critical in this operation, the right solution probably is to turn the error into a warning so that user can see the created A record.

Metadata Update from @pvoborni:
- Issue assigned to someone
- Issue set to the milestone: Future Releases

7 years ago

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)

5 years ago

Login to comment on this ticket.

Metadata