The problem lies in the NodeJS resolver's implementation of DNS resolution timing measurement, which does not account for retry timeouts. The Checkly API check is configured to trigger alerts when the DNS resolution time exceeds 5 seconds, but since the resolver times out after 5 seconds, it appears as if the DNS resolution took longer than expected. To fix this issue, a change was made to the NodeJS resolver's timeout value to reduce it from 5 seconds to 5000 milliseconds (or 5 seconds), and an additional retry mechanism was implemented to handle cases where the initial request times out. This modification has resolved the problem of DNS resolution timeouts exceeding 5 seconds, which triggered degradation alerts on Checkly.