Skip to content

dnsdist: Document that flushing the cache is allowed in read-only mode - #17291

Merged
rgacogne merged 1 commit into
PowerDNS:masterfrom
rgacogne:ddist-document-api-read-write-flush
May 6, 2026
Merged

dnsdist: Document that flushing the cache is allowed in read-only mode#17291
rgacogne merged 1 commit into
PowerDNS:masterfrom
rgacogne:ddist-document-api-read-write-flush

Conversation

@rgacogne

@rgacogne rgacogne commented May 5, 2026

Copy link
Copy Markdown
Member

Short description

As reported by Prasanna Dabi (thanks!) one might expect that a read-only API would not allow the flushing of the packet cache. This is not the case, the read-only flag controls whether the API is allowed to alter the configuration, but flushing the content of the packet cache is always allowed.

Checklist

I have:

  • read the CONTRIBUTING.md document
  • read and accepted the Developer Certificate of Origin document, including the AI Policy, and added a "Signed-off-by" to my commits
  • compiled this code
  • tested this code
  • included documentation (including possible behaviour changes)
  • documented the code
  • added or modified regression test(s)
  • added or modified unit test(s)

As reported by Prasanna Dabi (thanks!) one might expect that a read-only
API would not allow the flushing of the packet cache. This is not the case,
the read-only flag controls whether the API is allowed to alter the configuration,
but flushing the content of the packet cache is always allowed.

Signed-off-by: Remi Gacogne <remi.gacogne@powerdns.com>
@rgacogne rgacogne added this to the dnsdist-2.2.0 milestone May 5, 2026
@rgacogne
rgacogne merged commit eef174a into PowerDNS:master May 6, 2026
165 of 167 checks passed
@rgacogne
rgacogne deleted the ddist-document-api-read-write-flush branch May 6, 2026 15:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants