Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • BIND BIND
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 526
    • Issues 526
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 101
    • Merge requests 101
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • 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 Projects
  • BINDBIND
  • Issues
  • #529

Closed
Open
Created Sep 06, 2018 by Michael McNally@McNally

Negative Trust Anchors can disappear after "rndc reconfig" or "rndc reload"

Summary

Reported by a customer who is running BIND Supported Preview Edition 9.10.6-S3: Negative Trust Anchors (NTAs) can disappear after an "rndc reconfig" or "rndc reload"

Steps to reproduce

We asked the customer to list their NTAs, reconfigure, and list again:

$ rndc nta -dump |wc -l
100
$ rndc reconfig

$ rndc nta -dump |wc -l
0

What is the current bug behavior?

Named appears to lose track of the NTAs after "rndc reconfigure". Per the customer, also after "rndc reload"

What is the expected correct behavior?

Per the ARM, NTAs should persist through their valid lifetime, even across named restarts.

Assignee
Assign to
Time tracking