Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • BIND BIND
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 593
    • Issues 593
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 93
    • Merge requests 93
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source ProjectsISC Open Source Projects
  • BINDBIND
  • Merge requests
  • !7122

Resolve "TLS settings for primaries not saved for catalog zone entries." [v9_18]

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Mark Andrews requested to merge 3638-tls-settings-for-primaries-not-saved-for-catalog-zone-entries-v9_18 into v9_18 Nov 24, 2022
  • Overview 1
  • Commits 6
  • Pipelines 3
  • Changes 11

Extract the tlss values if present from the ipkeylist entry and add the resulting tls setting to the constructed configuration for the primary.

When comparing catalog zone entries for reuse also check the masters.tlss values for equality.

Backport of !7010 (merged)

Closes #3638 (closed)

Edited Dec 02, 2022 by Michał Kępień
Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: 3638-tls-settings-for-primaries-not-saved-for-catalog-zone-entries-v9_18