fixture-auth-api-a
Purpose
When Conduit forwards to an authoritative peer serving the published
fixture zone, api.example.test must return its committed A answer — a
second positive name beyond www, so zone fidelity is not a single-name
accident.
Applies only to peers in the auth role.
How it works
- The peer loads fixture zone
example.test. - A client asks Conduit for
api.example.testA. - The response must match the committed fixture records.
Outcomes
| Outcome | Meaning for operators |
|---|---|
| pass | The api A through Conduit matches the published fixture. |
| fail | Unexpected response code or answers — zone contents, auth peer, or Conduit path. |
| skip | Peer is not authoritative (or profile out of scope). |
| 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