basic-a-forward
Purpose
Confirm the minimal forward path: a client asks Conduit for a simple A record, Conduit forwards to the peer under test, and the client gets a successful answer. This is the baseline proxy contract for every supported peer role (stub, authoritative, and recursive).
How it works
- For this run, the peer is configured with a local smoke name
(
www.smoke.test→192.0.2.20) so the answer does not depend on the public Internet. - A client queries Conduit (forward-only profile); Conduit forwards to that peer.
- Checks require NOERROR and at least one answer section RR.
- A parity check also queries the peer directly and compares response code and answer count with the via-Conduit result — Conduit should not invent or drop success/failure relative to talking to the peer alone.
Outcomes
| Outcome | Meaning for operators |
|---|---|
| pass | Conduit returned a successful A answer for the smoke name, and that success matches querying the peer directly (same rcode and answer count). |
| fail | Unexpected: Conduit failed the query, returned no answer, or disagreed with a direct query to the peer. Investigate Conduit forwarding, the peer image/config for this run, or a peer version regression. |
| skip | This peer/profile combination is out of scope for the case (not applicable). |
| 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: smoke, full
Oracles: property, parity