fix: enforce DNS-first ordering for port and TLS checks #64

Merged
sneak merged 1 commits from fix/issue-58-check-ordering into main 2026-03-02 00:10:49 +01:00

1 Commits

Author SHA1 Message Date
user
461ab7e06c fix: enforce DNS-first ordering for port and TLS checks
All checks were successful
check / check (push) Successful in 46s
DNS checks now always complete before port or TLS checks begin,
ensuring those checks use freshly resolved IP addresses instead of
potentially stale ones from a previous cycle.

Changes:
- Extract runDNSChecks() from runDNSAndPortChecks() so DNS resolution
  can be invoked independently
- Run DNS before TLS on the TLS ticker (previously TLS ran alone with
  whatever IPs were in state from the last DNS cycle, up to 12h stale)
- RunOnce uses explicit 3-phase ordering: DNS → ports → TLS
- Add TestDNSRunsBeforePortAndTLSChecks to verify fresh IPs propagate
- Update README monitoring lifecycle to document DNS-first ordering

closes #58
2026-03-01 15:03:02 -08:00