fixture-auth-nodata-mx

Purpose

For an existing name that has no MX, authoritative peers return NODATA (NOERROR with an empty answer). Through Conduit, clients should see that same empty successful answer — Conduit does not invent MX or change the rcode.

How it works

1. The peer loads fixture zone example.test (www has A/AAAA, no MX).
2. A client asks Conduit for www.example.test MX.
3. The reply must be NODATA and match a direct query to the peer.

Outcomes

Outcome	Meaning for operators
pass	Through Conduit, MX on www is NODATA, matching the peer.
fail	Unexpected rcode or answers, or Conduit disagreed with the peer.
skip	Peer is not authoritative for this matrix (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: property, parity