watcher: keep port state when no nameserver of a name answered (closes #193)

The port check removed the saved port state of every address no configured name resolves to. A name whose nameservers all timed out or failed is saved with no records, so its addresses looked gone and lost their port state; when the nameservers answered again it was recorded afresh, and a port that opened or closed meanwhile was not notified. An entry is now kept when one of the names saved on it is configured and none of its nameservers answered on its last check, and such a name stays on the entry when the port is checked again for another name. A name whose nameservers answer with no addresses still loses it, and so does a name no longer configured. Model: opus-5-5
2026-10-02 00:44:49 +02:00
parent d2f154b2cf
commit 97c8138c85
5 changed files with 176 additions and 5 deletions
@@ -110,7 +110,9 @@ Contributions that introduce mocked, faked, or stubbed DNS will be rejected.
    - Port transitioned from open to closed (or vice versa).
    - New IP appeared (from DNS change) and its port state was recorded.
    - IP disappeared (from DNS change) — noted in the DNS change notification;
-      port state for that IP is removed.
+      port state for that IP is removed. When none of a name's nameservers
+      answered, its addresses are not known, so the port state saved for them is
+      kept.

 ### TLS Certificate Monitoring