Why two v=DMARC1 records at _dmarc make receivers ignore the policy, why a checker says no DMARC record found (wrong host name, doubled domain, bad v= tag), and how RFC 7489 and RFC 9989 handle each case.
Home › Guides › Multiple DMARC records / not found
Last updated 18 November 2026
Receivers look for exactly one TXT record starting with v=DMARC1 at _dmarc. plus the From domain, for example _dmarc.example.com.
_dmarc. (not on the root domain, and not with the host name doubled) and whether it starts with v=DMARC1. Publish one correct TXT record at _dmarc.example.com.The DMARC Record Checker reports both: it flags multiple DMARC records, and it shows where it looked when it finds none.
RFC 7489 section 6.6.3:
_dmarc. + the RFC5322.From domain.v= tag naming the current version of DMARC.news.example.com, that is _dmarc.example.com).RFC 9989 obsoletes RFC 7489 and replaces step 3 with a DNS Tree Walk: if there is no valid record at the Author Domain, the receiver queries each parent name in turn, at most eight queries in total. At every step, records that don't start with the DMARC v tag are discarded, and "If multiple DMARC Policy Records are returned for a single target, they are all discarded."
| What is published | RFC 7489 | RFC 9989 |
|---|---|---|
Two v=DMARC1 records at _dmarc.example.com, mail From example.com | DMARC not applied | Both discarded; the walk continues to the parent name (_dmarc.com), so your own policy is not applied |
Two records at _dmarc.news.example.com, one good record at _dmarc.example.com, mail From news.example.com | DMARC not applied (the Organizational Domain is only queried when the first set is empty) | The two are discarded and the example.com record applies, using its sp policy if set |
No record at _dmarc.news.example.com, one at _dmarc.example.com | The example.com record applies to the subdomain. RFC 9989: the sp tag applies to existing subdomains, np to non-existent ones, otherwise p. Microsoft: subdomains inherit the parent's DMARC settings unless they publish their own record. | |
A v=DMARC1 record plus another TXT at _dmarc that doesn't start with v=DMARC1 | The other TXT is discarded, so only one DMARC record remains. Not a duplicate. | |
| One record split into several quoted strings | One record. RFC 9989: the strings MUST be concatenated in order and parsed as a single string. | |
dig +short TXT _dmarc.example.com, or Microsoft's Resolve-DnsName -Name "_dmarc.contoso.com" -Type TXT.p= you are ready for, and every report address in a single comma-separated rua= list. Google's example is rua=mailto:postmaster@example.com, mailto:dmarc@example.com.dmarc=temperror or dmarc=permerror.contoso.com._report._dmarc at the vendor's domain). That is a different name, not a second DMARC record for you.DMARC is never read from the root domain's TXT records. RFC 9989 says the record is published at the name created by prepending the label _dmarc to the domain. A v=DMARC1 TXT at example.com itself is ignored. Google's setup steps give the host as _dmarc.example.com.
In a zone file, a name that doesn't end in a dot is relative and gets the zone origin appended (RFC 1035 section 5.1). DNS control panels that treat the host field as relative turn _dmarc.example.com into _dmarc.example.com.example.com. Query that doubled name with DNS Lookup; if the record is there, change the host to just _dmarc.
RFC 9989: v MUST be the first tag, its value is case sensitive, and the only possible value is DMARC1. If the tag isn't first, is missing, or isn't DMARC1, the entire record MUST be ignored. So p=none; v=DMARC1 or v=dmarc1 counts as no record at all.
This isn't "not found", but it has a similar effect. Both RFCs say that if the record has no valid p tag (or an invalid sp, or in RFC 9989 np), the receiver treats it as p=none when there is a syntactically valid rua, and otherwise applies no DMARC processing.
RFC 7489 defines dmarc=none as: no DMARC policy record was published for the aligned identifier, or no aligned identifier could be extracted. Microsoft 365 also shows dmarc=bestguesspass when no DMARC record is published for the From domain; Microsoft's advice is to publish an explicit DMARC record.
dig +short TXT _dmarc.example.com returns exactly one answer and it starts with v=DMARC1. Check public resolvers with the DNS Propagation Checker.p= and no errors.dmarc=pass, not none or bestguesspass.Need SPF, DMARC and MX checks across a whole client list? Run the Bulk SPF / DMARC / MX Auditor on Apify ($2 per 1,000 domains).
Check the record with the DMARC Record Checker, build a new one with the DMARC Record Generator, read aggregate reports in the DMARC Report Analyzer, query any TXT name with DNS Lookup, and check SPF, DKIM and DMARC together with the Email Deliverability Checker. Related guides: DMARC for Microsoft 365, p=none to p=reject rollout, DMARC fail with SPF pass, SPF multiple records and SPF, DKIM and DMARC for Google Workspace.
No. Under RFC 7489, more than one DMARC record at the same _dmarc name means DMARC processing is not applied. Under RFC 9989 the duplicates are all discarded and the receiver keeps walking up the DNS tree. Keep exactly one record.
Common causes: the record was added to the root domain instead of _dmarc.example.com, the DNS panel appended the domain twice (_dmarc.example.com.example.com), or the record does not start with v=DMARC1. Query _dmarc.yourdomain with a TXT lookup to see what is actually published.
A single TXT record at _dmarc followed by your domain, for example _dmarc.example.com, with a value starting v=DMARC1; p=. Subdomains without their own record use the parent domain record.
Use one record with both addresses in a single comma-separated rua tag, for example rua=mailto:a@example.com, mailto:b@example.net. Do not publish a second DMARC record for the second vendor.
Microsoft shows it when no DMARC record is published for the From domain and it infers a pass. It is not a real DMARC result; publish an explicit DMARC record.
Runbooks, checklists and helpdesk templates: IT Admin Packs on Gumroad.