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 565
    • Issues 565
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 92
    • Merge requests 92
  • 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
  • #359
Closed
Open
Issue created Jun 22, 2018 by Michael McNally@McNally

Question about 'using hashtable size' log messages for RPZs

Summary

Jinmei has a question about the appropriate logging level for an RPZ log message.

On ISC Support ticket #13060, he asks:

BIND 9.11.3-S2 emits the following log message at the info level for every RPZ when updating the RPZ:

isc_log_write(dns_lctx, DNS_LOGCATEGORY_GENERAL, DNS_LOGMODULE_MASTER, ISC_LOG_INFO,
"rpz: %s: using hashtable size %d", domain, hashsize);

Is this intentional? I'm asking this because this can be quite verbose for heavily changing zone and the log message is cryptic for typical operators. There was a similar case we discussed before (support ticket #12854), so I'm wondering whether this may be another instance of such "leftover".

Assignee
Assign to
Time tracking