Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • fusiondirectory-plugins fusiondirectory-plugins
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 50
    • Issues 50
    • List
    • Boards
    • Service Desk
    • Milestones
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • fusiondirectoryfusiondirectory
  • fusiondirectory-pluginsfusiondirectory-plugins
  • Issues
  • #5729
Closed
Open
Issue created Nov 08, 2017 by Côme Chilliet@cchillietReporter

SOA is not updated in reverse zones if there is no record change

Description

If only the SOA is modified it’s not updated in the reverse zones

FusionDirectory Version

1.2

Plugin with the defect

dns

Steps to Reproduce

  1. Edit a DNS zone which has a reverse and change SOA only
  2. Check LDAP content

Expected behavior:

SOA should be updated in both zone and reverse

Actual behavior:

Only forward gets the update

Assignee
Assign to
Time tracking