[BUG] SOA of reverse zone not updated after A record deletion

[millallo]

fM Version : 4.5.0 fmDNS: v5.3.3

• [X] I have read and understood the contributors guide.
• [X] I have checked that the bug-fix I am reporting can be replicated, or that the feature I am suggesting isn't already present.
• [X] I have checked that the issue I'm posting isn't already reported.
• [X] I have checked that the issue I'm posting isn't already solved and no duplicates exist in closed issues and opened issues
• [X] I have checked the pull requests tab for existing solutions/implementations to my issue/suggestion.

---

(BUG | ISSUE) Expected Behavior: The deletion of an A record with linked PTR, should trigger SOA update of the reverse zone and the reload config hint.

(BUG | ISSUE) Actual Behavior: The deletion of an A record with linked PTR, deletes A and PTR records correctly, but updates only the SOA of the forward zone.

(BUG | ISSUE) Steps to reproduce: Create an A record with 'Create PTR' checkbox and deploy new configuration. Delete the A record just created.

[WillyXJ]

This is now fixed in fmDNS 6.0.0 and later.