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 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
  • Issues
  • #3415
Closed
Open
Issue created Jun 17, 2022 by Thomas Beati@beati

"rndc reconfig" does not reload http statements

Summary

When we add an endpoint in an http statement in named.conf and run rndc reconfig, the new endpoint is not effective.
Bind needs to be restarted for the endpoint to be effective.
The reconfig was working in 9.18.2.

BIND version used

Bug introduced in 9.18.3 BIND 9.18.3 (Stable Release) id:16aefa3

Steps to reproduce

  1. Bind is started as an http server:
http local-http-server {
    endpoints {
        "/endpoint1/dns-query";
    };
};

option {
    ...

    listen-on port 8443 tls tls_conf http local-http-server {any;};

    ...
}
  1. Add an endpoint in named.conf :
http local-http-server {
    endpoints {
        "/endpoint1/dns-query";
        "/endpoint2/dns-query";
    };
};
  1. Run rndc reconfig

What is the current bug behavior ?

Configuration is not reloaded, the new endpoint responds with 404 error.

What is the expected correct behavior?

Configuration is reloaded, the new endpoint responds to dns queries.

Assignee
Assign to
Time tracking