sneak 4ff5f85320 resolver: try servers in a random order on each resolution (closes #138) ...

Every resolution walked the root servers in a fixed order, so
a.root-servers.net got every first query and its timeouts were paid on
every lookup. Each list of servers the resolver walks is now walked in a
random order from rand.Shuffle, chosen anew each time; a server that does
not reply, refuses, or gives an error reply or a referral that leads no
closer is still passed over for the next. When a referral names a zone's
nameservers without their addresses, all of them are now looked up, not
only the first that resolves, so the zone is not given up because one
randomly picked nameserver failed. No test fails if the walk stops
shuffling: which server a live query reached is not observable.

Model: opus-5-5

2026-10-02 00:01:15 +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

resolver: pass over a server that answers SERVFAIL or refers no closer (closes #197)

2026-10-02 01:17:37 +02:00

export_test.go

resolver: try servers in a random order on each resolution (closes #138)

2026-10-02 00:01:15 +00:00

iterative_test.go

resolver: try servers in a random order on each resolution (closes #138)

2026-10-02 00:01:15 +00:00

iterative.go

resolver: try servers in a random order on each resolution (closes #138)

2026-10-02 00:01:15 +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: try servers in a random order on each resolution (closes #138)

2026-10-02 00:01:15 +00:00

resolver_test.go

resolver: try servers in a random order on each resolution (closes #138)

2026-10-02 00:01:15 +00:00

resolver.go

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

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