clawbot 623e7b2c69 resolver: a nameserver is asked at each of its addresses in turn (closes #285) ...

A nameserver's queries went only to the first IPv4 address its name
resolves to, so one unreachable address made it fail whenever that
address came first in the answer. Each record type is now asked at the
addresses one at a time until one gives a usable reply, and the next
type is asked first at the address that gave it. The README's DNS
Resolution Strategy says which addresses are asked.

Model: opus-5-5

2026-10-15 10:17:14 +00:00

..

dns_client.go

tests: remove the DNS stand-ins from the watcher and resolver tests (closes #159)

2026-09-29 08:44:07 +02:00

errors.go

watcher: a hostname whose zone's nameservers all stop answering gets NS Failure (closes #284)

2026-10-14 00:27:29 +02:00

export_test.go

resolver: a nameserver is asked at each of its addresses in turn (closes #285)

2026-10-15 10:17:14 +00:00

iterative_internal_test.go

resolver: a nameserver with a failed record type is not nodata (closes #253)

2026-10-02 13:16:42 +02:00

iterative_test.go

resolver, watcher: a record type whose query fails keeps its previous records (closes #231)

2026-10-02 10:51:23 +02:00

iterative.go

resolver: a nameserver is asked at each of its addresses in turn (closes #285)

2026-10-15 10:17:14 +00:00

livedns_harness_test.go

tests: remove the DNS stand-ins from the watcher and resolver tests (closes #159)

2026-09-29 08:44:07 +02:00

livedns_test.go

resolver, watcher: a domain's nameservers are only its own delegation (closes #222)

2026-10-02 12:38:45 +02:00

resolver_test.go

resolver: a nameserver is asked at each of its addresses in turn (closes #285)

2026-10-15 10:17:14 +00:00

resolver.go

resolver, watcher: a record type whose query fails keeps its previous records (closes #231)

2026-10-02 10:51:23 +02:00