Onboarding client domains for DMARC begins with an operational intake record completed before anyone edits production DNS: it documents what work the client approved, who can edit zone files, who may view report telemetry, and who can order a rollback. With dated evidence and a named lead for each domain, the record lets an MSP move one client domain into monitoring while an unverified one stays on hold.
This workflow is MSP practice for independent clients. Assigning clear roles and getting written sign-off is operational hygiene, not something specified in the RFCs. One term needs care from the start: DMARC’s operational “Domain Owner” concerns domain control and delegation, and RFC 9989 defines it without settling legal ownership.
Which four responsibilities does the intake record name?
Assign every client and domain an immutable identifier, then formally assign four core responsibilities. While one person may cover several roles, each needs a name:
- The client decision contact approves service scope and verifies the business purpose of each sender.
- The DNS executor has an authorized operational path to publish approved records.
- The client data contact approves report destinations, designates viewers, and establishes data governance boundaries.
- The rollback decision maker can order restoration within an agreed change scope; name the executor who implements that restoration as well.
Beside those contacts, name the MSP analyst on the ticket, the engineer taking over operations, and an escalation contact. Verify access privileges separately across DNS hosting, outbound email platforms, and reporting collectors using named accounts with least-privilege permissions. Permission to read DMARC reports gives no right to edit DNS records.
Work with the client to catalog every sending domain and subdomain, the operational purpose of each service, critical notifications versus occasional sends, provider and tenant identifiers, and any sender whose ownership is still unresolved. This inventory must come from client stakeholders directly. Passing authentication does not tell you whether a service is still approved for company business; RFC 9989 limits authentication to that narrower scope. For architectural advice on separating streams, see how to structure sending domains and subdomains.
Keep a clear audit trail for everything you collect: log the client/domain ID, source, observation time and the original reference. For DNS records, capture owner name, type, value, and TTL. For messages, keep the authorized samples. For DMARC aggregate reports, log the generator, report ID, UTC interval, and evaluated policy domain, which match the core fields that RFC 9990 defines for a report. Report data can be forged, so before you make a consequential decision, check where a report came from and compare it with other evidence (RFC 9990 on false information).
Who approves a new DMARC report destination?
Routing DMARC telemetry to a new destination is a data decision, not only a DNS one. Confirm with the data contact which client container the destination belongs to, verify who can access the reporting workspace, and confirm that cross-tenant controls isolate that stream. Agree on telemetry storage, export procedures, and retention schedules under organizational privacy policies. Failure reports require extra caution because forensic samples can expose message content and personal data; request failure reports only for a specific diagnostic need. The model below relies exclusively on aggregate reports. For protocol background, review RFC 9990: third-party report recipients and RFC 9991: privacy considerations.
When the policy domain and the report collector reside in distinct Organizational Domains, RFC 9990 requires DNS authorization on the destination side. If that record is absent, receiving mail servers must ignore the unverified destination. This check proves only that the collector is willing to receive reports. Client approval and correct account routing remain separate checks.
Before publishing records in DNS, document previous and proposed TXT strings, the approver, the executor, the change window, verification checks, and rollback triggers. Leave existing policies and destinations untouched until prerequisites are signed off. After publication, compare DNS with the approved value and inspect where reports are being routed. If report streams stop arriving, investigate before you attribute the silence to the change.
A synthetic intake register for two clients
Everything in this example is fictional: the people, permissions, approvals, DNS responses, reports and handoff events. No live DNS query, message test or client work was performed. The scenario snapshot is 2026-09-15T09:00:00Z.
Northline uses client container CL-A; Harbor uses container CL-B. The shared collector host is msp.example.org. Jules is the MSP analyst and rollback decision maker, with Mara assuming operational ownership. For Northline, Priya approves scope, Omar executes DNS modifications, and Lina governs data access. For Harbor, Theo authorizes scope, incumbent provider contact Nina controls DNS, and Eva governs data access.
| Row / client / domain | Evidence and permitted work | Handoff or unresolved action |
|---|---|---|
A1 / CL-A / example.com | Priya confirms staff mail and Internet mailing-list use in A-SCOPE-1. The existing DNS and report evidence supports managed observation; no policy change is authorized. | Mara accepts A-HAND-1. Priya checks rare senders by 2026-09-18. |
A2 / CL-A / notices.example.com | Priya confirms the receipts service’s purpose in A-SCOPE-2. Lina approves the destination in A-DATA-2; Omar executes A-CHG-2. The supplied DNS and report evidence demonstrates the reporting path. | Mara accepts A-HAND-2, with review on 2026-09-18. Jules can order Omar to restore the prior TXT within this ticket. |
B1 / CL-B / example.net | Acquired brand with unknown sender use in B-SCOPE-1. Theo permits investigation, but Eva has not approved external reporting and destination authorization is missing. Only research is permitted. | Exception B-EX-1: Theo obtains Eva’s decision and Nina’s authorized change/rollback path by 2026-09-17. Mara tracks the hold. |
For row A1, ticket A-DNS-1 documents _dmarc.example.com with TXT v=DMARC1; p=none; rua=mailto:reports@example.com, TTL 3600, recorded at 2026-09-14T10:00:00Z. Nothing changes here. Lina permits Jules, Mara, and herself to view the CL-A workspace, while security rule A-ACL-1 denies access to CL-B personnel.
For row A2, ticket A-DNS-2 captures the identical existing TXT value and TTL at _dmarc.notices.example.com. The approved replacement string is v=DMARC1; p=none; rua=mailto:northline@msp.example.org, keeping owner name, type, and TTL unchanged. Assume policy retrieval directly at notices.example.com, with example.com and example.org as distinct Organizational Domains. The external authorization query combines policy domain and destination host:
TXT notices.example.com._report._dmarc.msp.example.org
The simulated DNS response in ticket A-EXT-2 returns v=DMARC1. Change ticket A-DNS-2b records the replacement at 2026-09-14T10:10:00Z. If report data reaches the wrong workspace, or the published value contains errors, Jules orders Omar to restore the complete prior TXT and check the restoration. Keep in mind that DNS caching means the rollback takes time to propagate across all resolvers.
Telemetry references A-RPT-1 and A-RPT-2 track report generator receiver.example.org, identifiers syn-A1-0914 and syn-A2-0914, and policy domains example.com and notices.example.com respectively. Both files cover 2026-09-14T00:00:00Z through 2026-09-15T00:00:00Z and map exclusively to container CL-A. These sample reports confirm the reporting path works, but they do not guarantee you have caught every sender or that messages reached the inbox.
For row B1, ticket B-DNS-1 records _dmarc.example.net with TXT v=DMARC1; p=none, TTL 3600, observed at 2026-09-14T10:20:00Z. An unapproved draft proposal suggests adding rua=mailto:harbor@msp.example.org. However, validation query B-EXT-1 finds no usable TXT record at example.net._report._dmarc.msp.example.org and no applicable wildcard. So no change and no transfer occurs. Even if a valid confirmation record appears in DNS later, Eva’s decision and the change authorization would still be outstanding. Domain B1 cannot inherit A2’s approval or routing evidence through the collector they share.
Handing over the record and the open items
When transferring responsibility to an operational successor, hand over the intake register, evidence artifacts, exact DNS change records, restoration instructions, and dated exceptions. Agree on administrative credentials, establish telemetry export procedures, and set a sunset date for legacy access grants. Separately record three operational milestones: whether business scope is signed off, whether reporting telemetry has been demonstrated, and whether policy enforcement has been authorized. If a report never arrives, treat it as missing data rather than a clean pass. In this scenario, A1’s mailing list usage and infrequent sender audit remain open items, and none of the rows authorizes moving to quarantine or reject. Advancing DMARC policy requires a distinct risk assessment, which RFC 9989 treats as a step of its own.
Frequently asked questions
Which four responsibilities should a client domain intake record name?
Four distinct roles: the client decision contact who confirms service scope and sender purpose, the DNS executor who publishes approved records, the data contact who approves report destinations and viewers, and the rollback decision maker who can order restoration. One person can hold multiple roles, but every role requires a named individual.
Does read access to DMARC reports give someone authority to edit DNS?
No. Permission to read DMARC reports gives no right to edit DNS records. Permissions in DNS hosting, sending platforms, and reporting tools must be configured separately using named accounts with least-privilege access.
What does the _report._dmarc DNS authorization check prove?
It proves the collector’s willingness to receive reports, nothing more. Client approval and correct account routing remain separate checks.
Should an MSP request DMARC failure reports for client domains?
Failure reports deserve extra caution, because they can expose message content and personal information. Request them only for a separately justified diagnostic need.
Can one client inherit another client’s report destination approval through a shared collector?
In the example, B1 cannot inherit A2’s approval or routing evidence through the collector they share. Even if a valid TXT appeared later, Eva’s decision and the change authorization would still be outstanding.


