watcher: a hostname whose zone's nameservers all stop answering gets NS Failure (closes #284)
check / check (push) Waiting to run

When none of the nameservers of a hostname's zone answered, the walk to
them failed and the check was only logged. The walk now returns a
NoAnswerError naming the nameservers of the zone it reached through a
referral when none of them answers. When those are the nameservers the
previous check saved for the name, each is saved as failed with the
reason, so it gets an NS Failure and later an NS Recovery. A domain with
no delegation of its own, whose NS lookup is that same walk, gets the
same. A walk that fails before that zone, as when the host loses its
network, is still only logged.

Model: opus-5-5
This commit was merged in pull request #290.
This commit is contained in:
2026-10-14 00:27:29 +02:00
parent aaccabad50
commit b79726acc6
10 changed files with 328 additions and 24 deletions
+3 -1
View File
@@ -31,9 +31,11 @@ func NewWithQueryTimeout(log *slog.Logger, timeout time.Duration) *Resolver {
func (r *Resolver) FollowDelegation(
ctx context.Context,
domain string,
zone string,
nameservers []string,
servers []string,
) ([]string, error) {
return r.followDelegation(ctx, domain, servers)
return r.followDelegation(ctx, domain, zone, nameservers, servers)
}
// FindAuthoritativeNameserversFrom exports findAuthoritativeNameservers