Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • BIND BIND
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 638
    • Issues 638
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 92
    • Merge requests 92
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
    • Model experiments
  • 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
  • Issues
  • #2506
Closed
Open
Issue created Feb 19, 2021 by Chuck Stearns@chuckDeveloper

Catalog zones ignores already loaded non primary zones on secondary

Sequence of events:

  1. A forward zone foo.com not loaded in named as part of named.conf on Primary;
  2. A forward zone foo.com already loaded in named as part of named.conf on Secondary only.
  3. A Primary zone foo.com is added to Catalog Zones as primary zone on Primary server -- Success
  4. Catalog zone transfer took place
  5. Secondary servers added zone foo.com as Primary zone though Forward zone foo.com is already loaded.

According to the draft RFC for DNS Catalog Zones https://tools.ietf.org/html/draft-ietf-dnsop-dns-catalog-zones-01:

" If there is a clash between an existing member zone's name and an incoming member zone's name (via transfer or update), the new instance of the zone MUST be ignored and an error SHOULD be logged." (6.1)

It appears that the catalog zone code is probably checking the zone table for an existing zone called foo.com, but it's not checking the forwarder table.

Assignee
Assign to
Time tracking