A multi-client DMARC rollout starts once onboarding has produced each client’s domain inventory and authorized permission paths: the next step is a queue of policy changes, each evaluated and approved on its own. Rows lacking evidence or client sign-off stay on hold. Ready domains are scheduled by business consequence, technical dependencies, and staff availability to execute an emergency rollback. A good portfolio pass rate cannot clear an individual domain whose questions remain unresolved. This queue is an operational template, not an RFC standard. The guide on how to roll out DMARC without breaking your email covers the general case.
Before ranking a change, identify which hostnames its policy actually governs: inspect explicit records and inherited effects before bundling a parent change with subdomains. RFC 9989 defines DNS Tree Walk for policy discovery (checked 2026-09-15), and its publication does not establish that receivers have adopted it. For updated inheritance rules, review what DMARCbis (RFC 9989) changes.
What each row needs before it can be ranked
Every row in the rollout register records exact current and proposed DNS strings, client-approved sender inventory, evidence version, sending cycles covered, missing paths, and business consequence. It also names the client decision maker, DNS executor, report data owner, and rollback decision maker, with permissions and availability. Consequence does not equal volume: an invoice stream can deserve more scrutiny than a larger stream that matters less.
Known legitimate streams with missing or unaligned authentication MUST be repaired before enforcement, and an exception cannot waive this (remediation). Readiness also depends on sending cadence, which forms part of the enforcement decision.
Preserve header provenance for checks on received messages: an Authentication-Results header is trustworthy only when you trust the reporting server and path, as RFC 8601 explains. Reporting is optional for receivers. Aggregate reports can be incomplete or forged and do not establish inbox placement, so business approval, ownership, delivery evidence, and permission to inspect client data stay distinct from authentication results (report limitations; placement limits).
A synthetic queue for two clients
Everything below is invented: the clients, people, approvals, dates, records and observations. It is a planning snapshot for 2026-09-15, and no tests or changes were performed.
For Cedar, Ada authorizes policy decisions, Ben executes DNS changes, and Cora owns report data. For Marlin, those roles belong to Emil, Farah, and Gia. Both clients separately delegate rollback authority to Dara. Ben and Farah each hold zone permission and window availability for their own client. Cora and Gia allow analyst Rowan to access only their respective client workspaces; the synthetic evidence packets confirm report receipt and permissions. Dara supervises only one active observation window at a time.
Every domain in the table publishes an explicit TXT record at _dmarc.<domain>. Replace <domain> with that row’s domain in record names and values:
Previous: v=DMARC1; p=none; rua=mailto:dmarc@<domain>; adkim=s; aspf=s
Proposed: v=DMARC1; p=quarantine; rua=mailto:dmarc@<domain>; adkim=s; aspf=s
Restoration: v=DMARC1; p=none; rua=mailto:dmarc@<domain>; adkim=s; aspf=s
The proposed quarantine update applies exclusively to C-11 and M-21; held rows keep previous values. Both parents publish v=DMARC1; p=none; sp=none. There are no further sending subdomains and no proposed parent modifications, making the four scopes independent.
Evidence packages CE-11 and MA-21 cover 2026-08-17 through 2026-09-13 UTC from mx1.receiver.example and mx2.receiver.example, with no missing feed periods and zero reported alignment failures for approved senders or unclassified traffic. Each package includes direct and alias inspections from 2026-09-14: valid DKIM signatures use the exact domain in d= on both paths, direct SPF passes with an identical MAIL FROM domain, and alias forwarding fails SPF. Both paths pass DMARC via aligned DKIM under RFC 9989’s evaluation rules.
| Client and change | Evidence and consequence | Queue decision and condition |
|---|---|---|
Cedar: C-11, notice.cedar.example | CE-11: daily status notices, low consequence. Ada confirms the complete known inventory and no user or list posting. | Batch 1: Ada approves C-11-r1, none to quarantine, subject to fresh checks at the window. Ben executes; Dara controls rollback. |
Cedar: C-12, billing.cedar.example | CE-12: quarterly invoices, high consequence; no invoice run was observed in the stated period. A manual sample passes aligned SPF but has no DKIM. | Hold at p=none; no enforcement revision approved. Ada owns EX-12; application owner Ivo must enable valid aligned DKIM and supply evidence from a production run or a representative path. Review 2026-09-18; expected invoice run 2026-09-30. Neither date authorizes promotion. |
Marlin: M-21, alerts.marlin.example | MA-21: daily maintenance notices, with a higher support consequence than C-11. Emil confirms the known inventory and no user or list posting. | Batch 2: Emil separately approves M-21-r1, none to quarantine; Farah executes. Wait for Dara’s batch-1 release and confirm that fresh evidence still matches. |
Marlin: M-22, staff.marlin.example | MA-22: high-consequence staff mail; direct messages have aligned DKIM. Users may post to Internet lists, whose paths are uncharacterized. | Remain at p=none, outside the reject queue. Emil owns EX-22; review on 2026-10-01 after assessing staff and list use. The date grants no approval. |
C-12’s missing cycle does not block the independent C-11 change. M-21 waits for staffing capacity, with its own approval intact. The evidence window here is an example only: your observation window will depend on how often the client sends mail.
Moving to reject demands an independent decision. Domains publishing p=reject MUST configure valid DKIM and MUST NOT rely solely on SPF. Domains where employees participate in discussion lists SHOULD NOT use reject; if choosing reject, they SHOULD compare dispositions after at least a month at none and an equally long window at quarantine. Domains choosing reject SHOULD restrict list postings or warn users that participation may be disrupted (RFC 9989 on reject and mailing lists). This conditional advice is not a rollout clock for every client.
When is a batch released, who orders the restoration, and how is the queue handed over?
In this queue, Dara releases batch 2 only after Rowan confirms the exact new TXT string in DNS, repeats both passing paths, and reviews the first complete post-change UTC reporting period across both feeds. There must be no new unexplained failure on an approved path and no related confirmed service incident. A missing feed pauses batch progression for investigation, though silence alone is not a delivery incident. If a shared process flaw undermines the evidence or the rollback path of several dependent rows, reassess all of them.
Suppose an authorized sample on a supported path fails DMARC after C-11-r1 and the service owner confirms disruption. Rowan preserves revision, timestamp, header provenance, and handling logs. Under Cedar’s delegation, Dara orders restoration, and Ben restores the complete previous C-11 value in DNS. Rowan checks DNS, re-tests the path, and continues observation. Unrelated client domains are not restored automatically.
Compare subsequent reports against change timestamps, because a transition can contain old or mixed-policy results (RFC 9990 on policy transitions). A DNS rollback has to be verified, does not bring back mail already rejected, and promises no instant recovery.
Finally, Cora releases Cedar’s artifacts to Ada’s designated lead, while Gia releases Marlin’s telemetry exclusively to Emil’s designee. Obtain an acknowledgement of the observed value and its check time, the completed checks, the coverage gaps, the exceptions and review dates, the normal and emergency DNS contacts, and who replaces Dara or when Dara’s delegation ends. That way the change register stays usable after the temporary rollout staff leave.
Two companion documents accompany this queue: the DMARC readiness checklist and DMARC enforcement decisions.
Frequently asked questions
Does a good DMARC pass rate across the portfolio clear an individual client domain?
A good pass rate across the portfolio cannot clear a client domain whose own questions are unresolved. Each policy change is approved on its own, and rows that lack evidence or authority stay on hold.
Can an exception waive repairing a known legitimate stream before enforcement?
No. Known legitimate streams with missing or unaligned authentication MUST be repaired before enforcement, and no operational exception can waive this requirement.
Is sending volume the same as business consequence when ranking a change?
Consequence is not volume: an invoice stream can deserve more scrutiny than a larger stream that matters less.
Does a missing report feed mean a delivery incident?
No. Silence in reporting feeds pauses rollout progression for investigation, but missing telemetry alone does not indicate that live email delivery has failed.
Does restoring p=none recall mail that was already rejected?
Restoration needs verification, cannot recall mail that was already rejected and promises no instant recovery. Unrelated client domains are not restored automatically.


