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 568
    • Issues 568
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 94
    • Merge requests 94
  • 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
  • Issues
  • #2895
Closed
Open
Issue created Sep 08, 2021 by Ondřej Surý@ondrejOwner

named can create unrecoverable managed-keys.jnl file

  1. Run named in a way it can't reach the internet (f.e. set the query-source port to the listening port).
options {
	query-source address 10.10.10.20 port 53054;
	port 53;
	listen-on port 53053 { 10.10.10.20; };
};
  1. Stop it after you see running in the log immediately, but before resolver priming query complete is printed
  2. Verify that managed-keys.jnl is bogus with $ bin/tools/named-journalprint managed-keys.bind.jnl
del .            0    IN    SOA    . . 0 0 0 0 0
add .            0    IN    SOA    . . 1 0 0 0 0
add .            0    IN    TYPE65533 \# 16 00000000000000000000000000000000
  1. Now fix your config:
options {
	query-source address 10.10.10.20 port 0;
	port 53;
	listen-on port 53053 { 10.10.10.20; };
};
  1. Run named again and it will not recover from the broken managed-keys.bind.jnl file:
08-Sep-2021 09:50:48.172 running
08-Sep-2021 09:50:49.784 managed-keys-zone: DNSKEY set for zone '.' could not be verified with current keys
08-Sep-2021 09:50:49.788 validating ./NS: no valid signature found
08-Sep-2021 09:50:49.788 no valid RRSIG resolving './NS/IN': 198.97.190.53#53
08-Sep-2021 09:50:49.796 validating ./NS: no valid signature found
08-Sep-2021 09:50:49.796 no valid RRSIG resolving './NS/IN': 199.7.83.42#53
08-Sep-2021 09:50:49.804 validating ./NS: no valid signature found
08-Sep-2021 09:50:49.804 no valid RRSIG resolving './NS/IN': 193.0.14.129#53
08-Sep-2021 09:50:53.028 validating ./NS: no valid signature found
08-Sep-2021 09:50:53.028 no valid RRSIG resolving './NS/IN': 198.41.0.4#53
08-Sep-2021 09:50:53.040 validating ./NS: no valid signature found
08-Sep-2021 09:50:53.040 no valid RRSIG resolving './NS/IN': 192.33.4.12#53
08-Sep-2021 09:50:58.168 resolver priming query complete
08-Sep-2021 09:51:13.172 managed-keys-zone: DNSKEY set for zone '.' could not be verified with current keys

This is low-priority issue, but it should be recorded somewhere.

Assignee
Assign to
Time tracking