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.
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
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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
yes, obviously. update the readme.