Skip to content

fix: debounce DNS health over time, and let refusals reach the verdict #26

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
thedancingdeveloper merged 1 commit into from
Aug 18, 2026
Merged

fix: debounce DNS health over time, and let refusals reach the verdict #26

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion docs/CONFIGURATION.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -98,7 +98,14 @@ checks and is the stricter choice if you want the container marked unhealthy.

`udp_attempts` retries transient UDP loss before falling back to TCP to
the same in-tunnel resolver. `failure_threshold` and `success_threshold`
provide global check hysteresis while individual failures remain logged.
provide global check hysteresis while individual failures remain logged. They
are counts of queries, so on a busy gateway they describe a fraction of a
second; a degraded verdict is therefore held for a minute before a recovery may
clear it, long enough for a scrape or a status poll to land on it. Queries
refused by admission control count towards the verdict alongside queries the
upstream failed to answer — to a client they are the same event — and are
reported with the `dns.queries_refused` reason code rather than
`dns.upstream_udp_failures`.
Enrolled clients should use only the gateway listener; firewall policy rejects
other plain DNS destinations.

Expand Down
Loading