happyDomain/checker-alias
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
0 releases 6 tags
  • v0.3.2 da6def100c

    checker: report transient apex-lookup failures as Unknown, not Crit
    All checks were successful
    continuous-integration/drone/push Build is passing
    Details
    continuous-integration/drone/tag Build is passing
    Details

    nemunaire released this 2026-06-18 01:29:30 +00:00 | 1 commits to master since this release

    apexLookupRule mapped every findApex failure to Crit, including transport
    and resolver faults like "lookup nemunai.re on 127.0.0.11:53: server
    misbehaving" — a flaky recursive resolver, not a broken delegation. That
    made the check flap into Crit whenever the resolver hiccuped, the same
    class of false negative the chain path already fixed.

    Mark apex-lookup failures that stem from a transport/resolver fault
    (resolveZoneNSAddrs net errors, recursiveExchange transport errors, and
    SERVFAIL/REFUSED seen during the SOA walk) as transient via a typed
    error, surface it as ApexLookupTransient, and have apexLookupRule report
    Unknown for those. Definitive failures (NXDOMAIN-only walk, no resolvable
    NS) still drive Crit.

    Downloads