sneak/dnswatcher
1
0
Fork 0
Code Issues 3 Pull Requests 2 Actions Packages Projects Releases Wiki Activity

docs: health check wording follows the code (rework for #302)
check / check (push) Canceled after 0s
Details

Browse Source 
The README, the comments and TODO.md say the health check gives error
only when every lookup in a round failed because no root server gave a
usable reply, and the README drops the claim that the other failures
are reported as notifications.

Model: opus-5-5
This commit is contained in:
sneak
2026-10-18 14:04:04 +00:00
parent a70b173a48
commit cc27d8d957
4 changed files with 27 additions and 25 deletions
Download Patch File Download Diff File Expand all files Collapse all files
TODO.md
+4 -3
View File
@@ -19,9 +19,10 @@ milestone: https://git.eeqj.de/sneak/dnswatcher/milestone/7
# Completed Steps
- 2026-10-18: the health check answers 503 with `status` `error` when no lookup
in the most recent round of DNS checks got a reply from a root server, as on a
network that intercepts DNS queries (closes #302).
- 2026-10-18: the health check answers 503 with `status` `error` when every
lookup in the most recent round of DNS checks failed because no root server
gave a usable reply, as on a network that intercepts DNS queries (closes
#302).
- 2026-10-16: the first reply marked "recursion available" from a root server's
address, a refusal included, stops the lookup with "this network intercepts
DNS queries", so on a network that sends DNS to a resolver dnswatcher and its