resolver: a nameserver with a failed record type is not nodata (closes #253)

classifyResponse set nodata when every record type that answered had no records, even when another type's query got no usable reply. That type is listed in FailedTypes and its records are unknown, so the nameserver has not said it has none. It now stays ok, the status README describes for a nameserver with a failed type, and nodata is set only when no type failed. The watcher saved nodata as ok already, so saved state is unchanged; the live test that rejects nodata no longer fails when one of a nameserver's queries is lost. Model: opus-5-5
2026-10-02 13:16:42 +02:00
parent 67b67b8475
commit 6822996134
3 changed files with 40 additions and 17 deletions
@@ -19,6 +19,8 @@ trial run of the finished image: https://git.eeqj.de/sneak/dnswatcher/issues/149

 # Completed Steps

+- 2026-10-02: a nameserver whose query for one record type failed while the
+  others answered with no records is `ok`, not `nodata` (closes #253).
 - 2026-10-02: a domain that does not exist is shown so, with no nameservers; no
  name gets a parent's nameservers when its own did not answer (closes #222).
 - 2026-10-02: the refused-query test sends one query to four operators' public