Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
I
ISPConfig 3
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 492
    • Issues 492
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 32
    • Merge Requests 32
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • ISPConfig
  • ISPConfig 3
  • Issues
  • #4695

Closed
Open
Opened Jul 08, 2017 by Lubos@lzahradil

3.1.5 - Dnssec signing zone - multiserver

When installing ispconfig with multiserver where ispconfig is on one server and bind9 as master on the other server.

When a zone is created, the zone is signed.

After a few days the signature expires and the zone will cease to be trustworthy and then inactive.

The .signed file is unchanged.

When Tools> Resync DNS, the zone is properly signed and starts working. At this point, it is visible that the .signed file has changed.

Assignee
Assign to
3.1.7
Milestone
3.1.7
Assign milestone
Time tracking
None
Due date
None
Reference: ispconfig/ispconfig3#4695