#7197 dns failes to load zone if it finds a broken record of a deleted replica
Closed: wontfix by rcritten. Opened by pvoborni.

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

Description of problem:
I know this bug could tend to be closed but I wanted to document a very bad
behavior.
We have a customer with a removed replica where the dns records have not been
deleted.
I remember this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1296898
 [RFE] it could be nice to have a way to clean dns zones and records of deleted
records references.
so, the problem is that a dnsrecord of a deleted replica is broken. We see
there is not an A record for idm02 replica.
######
  Record name: idm01
  A record: <ip address1>
...
  Record name: idm02
...
  Record name: idm04
  A record: <ip address 4>
######
And named.run:
28-Aug-2017 03:15:07.810 zone <master zone x>/IN: NS 'idm02.domain' has no
address records (A or AAAA)
28-Aug-2017 03:15:07.810 zone <master zone x>/IN: not loaded due to errors.
28-Aug-2017 03:15:07.810 4 master zones from LDAP instance 'ipa' loaded (5
zones defined, 0 inactive, 1 failed to load)
28-Aug-2017 03:15:07.815 zone xxx.yyy.in-addr.arpa/IN: sending notifies (serial
1503882907)
28-Aug-2017 03:15:07.815 zone zzzz.wwww.zzz.in-addr.arpa/IN: sending notifies
(serial 1503882907)
28-Aug-2017 03:15:07.815 zone <master zone Y>/IN: sending notifies (serial
1503882907)
28-Aug-2017 03:15:08.457 zone <master zone x>/IN: NS 'idm02.domain' has no
address records (A or AAAA)
28-Aug-2017 03:15:08.457 zone <master zone x>/IN: not loaded due to errors.
28-Aug-2017 03:15:08.457 update_zone (syncrepl) failed for master zone DN
Version-Release number of selected component (if applicable): RHEL7.4

Metadata Update from @pvoborni:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1488199

From the BZ:

Note 1: when removing a broken replica with ipa-replica-manage del, the command properly removes the NS record. I am not sure how the customer got into this situation but could not reproduce.

Note 2: ipa commands are still working on the remaining master, and there are 2 possible paths to fix the issue:
- either remove the broken replica with "ipa-replica-manage del --clean"
- or remove the NS record pointing to the missing replica with "ipa dnsrecord-del ipadomain.com. '@' --ns-rec=dummy.ipadomain.com."

Metadata Update from @rcritten:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

Metadata