fixture-auth-a
Purpose
Confirm that when Conduit forwards to an authoritative peer serving a published fixture zone, the A answer clients see matches the committed fixture RRset — not merely “some” successful answer. This guards zone loading and end-to-end authoritative data fidelity through Conduit.
Applies only to peers in the auth role (recursive and stub peers skip).
How it works
- The authoritative peer loads fixture zone
example.test. - A client queries Conduit for an A name in that zone; Conduit forwards to the peer.
- The returned answer RRset must match the committed expected records.
Outcomes
| Outcome | Meaning for operators |
|---|---|
| pass | The A answer through Conduit matches the published fixture RRset for example.test. |
| fail | Unexpected: wrong, missing, or empty answer relative to the fixture — zone not loaded as intended on the peer, Conduit altered or failed the answer, or peer/auth behavior changed. |
| skip | Peer is not authoritative for this matrix (or profile out of scope). Expected for recursive/stub columns. |
| characterized | Not used for this case today. If it appeared, it would mean a documented peer-specific quirk rather than a Conduit regression. |
Matrix: peer (by publisher)
Suites: full
Oracles: fixture