Conduit behavior

These cases exercise Conduit (lookup/cache path, request rules, dataplane runtime, backend health) rather than peer-product interoperability. They run against a single stub peer (thekelleys-dnsmasq-2.90 (dnsmasq 2.90)) so results are not spread across every publisher column. Cache hit proofs that use peer-query-count rely on that stub’s dnsmasq query logs — not a general multi-peer count facility. Peer contract cases remain under By publisher.

Last tested 2026-08-06 · All executed cases passed

Results

Test	cache-forward	forward-only	forward-split-io
cache-forward-a	pass	skip	skip
cache-lmdb-durability-restart-hit	pass	—	—
cache-miss-then-hit-a	pass	skip	skip
cache-nxdomain-miss-then-hit	pass	skip	skip
cache-rotate-rrset	pass	skip	skip
dataplane-split-io-forward	skip	skip	pass
health-drain-avoids-backend	skip	pass	skip
health-drain-resume-returns	skip	pass	skip
health-fail-open-all-down	skip	pass	skip
health-live-dead-prefer-live	skip	pass	skip
health-passive-fast-trip	skip	pass	skip
rhai-soft-drop	skip	pass	skip
rules-clear-drop	skip	pass	skip
rules-drop-now	skip	pass	skip
rules-soft-drop	skip	pass	skip

Stub peer id: thekelleys-dnsmasq-2.90. Cases declare matrix: conduit and pin this peer in applicability.peers.