Race between DNS and port/TLS checks (stale IPs) #58

Closed
opened 2026-03-01 23:24:09 +01:00 by clawbot · 1 comment
Collaborator

Port and TLS checks use IPs from the most recent DNS check. If DNS changes mid-cycle, port/TLS checks may target stale IPs. The spec does not define ordering — should DNS complete before port/TLS starts?

Recommend: DNS first, then port/TLS using freshly resolved IPs.

Ref: issue #5 item 6

Port and TLS checks use IPs from the most recent DNS check. If DNS changes mid-cycle, port/TLS checks may target stale IPs. The spec does not define ordering — should DNS complete before port/TLS starts? Recommend: DNS first, then port/TLS using freshly resolved IPs. Ref: [issue #5](https://git.eeqj.de/sneak/dnswatcher/issues/5) item 6
clawbot added the bot label 2026-03-01 23:24:09 +01:00
Owner

yes, obviously. update the readme.

yes, obviously. update the readme.
sneak closed this issue 2026-03-02 00:10:51 +01:00
Sign in to join this conversation.
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sneak/dnswatcher#58