Hide Forgot
Description of problem: When removing one dns record from zone map via cli (ipa dnsrecord-add) we can force the reverse entry, although when removing, the information still on reverse map. Version-Release number of selected component (if applicable): 4.4.0 How reproducible: 100 Steps to Reproduce: 1. Below I can show all steps to remove the entry (zone and reverse) // The command to add a new entry on IDM (via idm server / cli) --- [root@idm ~]# ipa dnsrecord-add domain.example waldirio --a-rec=192.168.56.200 --a-create-reverse Record name: waldirio A record: 192.168.56.200 [root@idm ~]# --- // The command to delete the entry on IDM (via idm server / cli) --- [root@idm ~]# ipa dnsrecord-del domain.example waldirio --del-all ------------------------- Deleted record "waldirio" ------------------------- [root@idm ~]# --- // The command to delete the entry on IDM - reverse map (via idm server / cli) --- [root@idm ~]# ipa dnsrecord-del 56.168.192.in-addr.arpa. --ptr-rec=waldirio.domain.example. Record name: 200 -------------------- Deleted record "200" -------------------- [root@idm ~]# --- Actual results: Necessary execute two steps, one to remove from zone and another one to remove from reverse Expected results: In one simple command, remove from zone and reverse map. Additional info:
Hi Team Actually when creating new dns record in zone map, we can use --a-create-reverse, just to add the new entry in reverse map / ptr entry, the idea should be something similar to remove entry from reverse map *--a-delete-reverse* Best Regards -- Waldirio M Pinheiro | Senior Software Maintenance Engineer
Upstream ticket: https://fedorahosted.org/freeipa/ticket/6516
Thank you taking your time and submitting this request for Red Hat Enterprise Linux. The request was cloned to the upstream tracker a long time ago (see link to the upstream ticket above), but it was unfortunately not given priority either in the upstream project, nor in 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. Please note that you can still track this request or even offer help in the referred upstream Pagure ticket to expedite the solution.