Saved port state is removed when every nameserver of a hostname fails #193

New Issue

2026-10-01T23:44:13+02:00

clawbot commented

2026-10-01 23:44:13 +02:00

Found while working on #190.

The port and TLS checks do not call ResolveIPAddresses; they take a hostname's addresses from the records saved for it. When every nameserver of the hostname times out or fails, each one is saved as error with empty records, so for that check the hostname has no addresses. The port check then removes the saved port state of the hostname's addresses (unless another target still resolves to them), and no TLS check runs for the hostname. When the nameservers answer again, the port state is recorded afresh, so a port that opened or closed in the meantime is not notified.

Definition of done

When no nameserver of a hostname answered, its saved port state is kept, not removed; a hostname whose nameservers answer with no addresses still has its port state removed as today.
A test covers both cases, with hostname state built in the test (no lookup) or live DNS. No stand-in resolver.

Model: opus-5-5

Found while working on https://git.eeqj.de/sneak/dnswatcher/issues/190. The port and TLS checks do not call `ResolveIPAddresses`; they take a hostname's addresses from the records saved for it. When every nameserver of the hostname times out or fails, each one is saved as `error` with empty `records`, so for that check the hostname has no addresses. The port check then removes the saved port state of the hostname's addresses (unless another target still resolves to them), and no TLS check runs for the hostname. When the nameservers answer again, the port state is recorded afresh, so a port that opened or closed in the meantime is not notified. ## Definition of done - When no nameserver of a hostname answered, its saved port state is kept, not removed; a hostname whose nameservers answer with no addresses still has its port state removed as today. - A test covers both cases, with hostname state built in the test (no lookup) or live DNS. No stand-in resolver. Model: opus-5-5

clawbot referenced this issue

2026-10-01 23:44:29 +02:00

resolver: error from ResolveIPAddresses when no nameserver answered (closes #190) #194

clawbot referenced this issue

2026-10-01 23:44:37 +02:00

ResolveIPAddresses returns no addresses and no error when every nameserver fails #190

clawbot added this to the 1.0 milestone 2026-10-01 23:51:23 +02:00

clawbot referenced this issue from a commit

2026-10-02 00:04:16 +02:00

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

clawbot referenced a pull request that will close this issue

2026-10-02 00:05:25 +02:00

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

clawbot commented

2026-10-02 00:05:31 +02:00

Fixed in #195: when none of a configured name's nameservers answered, the port state saved for its addresses is kept; a name whose nameservers answer with no addresses still loses it.

Model: opus-5-5

Fixed in https://git.eeqj.de/sneak/dnswatcher/pulls/195: when none of a configured name's nameservers answered, the port state saved for its addresses is kept; a name whose nameservers answer with no addresses still loses it. Model: opus-5-5

clawbot referenced this issue

2026-10-02 00:12:50 +02:00

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

clawbot referenced this issue from a commit

2026-10-02 00:17:30 +02:00

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

clawbot referenced this issue from a commit

2026-10-02 00:44:20 +02:00

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

clawbot closed this issue

2026-10-02 00:44:51 +02:00

clawbot referenced this issue from a commit