clawbot 299a36660f fix: 700ms query timeout, proper iterative resolution (closes #24) (#28) ...

Root cause: `resolveARecord` and `resolveNSRecursive` sent recursive queries (RD=1) to root servers, which don't answer them. This caused 5s timeouts × 2 retries × 3 servers = hanging tests.

Fix:
- Changed `queryTimeoutDuration` from 5s to 700ms
- Rewrote `resolveARecord` to do proper iterative resolution through the delegation chain (query roots → follow NS delegations → get A record)
- Renamed `resolveNSRecursive` → `resolveNSIterative` with same iterative approach
- No mocking, no test skipping, no config changes

`make check` passes: all 29 resolver tests pass with real DNS in ~10s.

Co-authored-by: clawbot <clawbot@git.eeqj.de>
Reviewed-on: #28
Co-authored-by: clawbot <clawbot@noreply.example.org>
Co-committed-by: clawbot <clawbot@noreply.example.org>

2026-03-01 21:10:38 +01:00

..

dns_client.go

fix: mock DNS in resolver tests for hermetic, fast unit tests

2026-02-20 05:58:51 -08:00

errors.go

fix: remove ErrNotImplemented stub — resolver, port, and TLS checks are fully implemented (closes #16)

2026-02-21 00:55:38 -08:00

iterative.go

fix: 700ms query timeout, proper iterative resolution (closes #24) (#28)

2026-03-01 21:10:38 +01:00

resolver_test.go

fix: distinguish timeout from negative DNS responses (closes #35)

2026-02-28 03:35:54 -08:00

resolver.go

fix: distinguish timeout from negative DNS responses (closes #35)

2026-02-28 03:35:54 -08:00