More than one DMARC record
A second service asked you to add a DMARC record, and now there are two. Receivers throw both away, even when each is correct on its own.
RFC 9989 section 4.10: "If multiple DMARC Policy Records are returned for a single target, they are all discarded." On your main domain that leaves no DMARC policy and no reports. On a subdomain, receivers go on to the parent's record and apply its policy, so check the parent's result too.
It usually happens when a second service asks you to "add a DMARC record" and the new one goes in beside the old one. Other TXT records at the same name don't count, as long as they don't start v=DMARC1.
dig +short TXT _dmarc.example.com
Put your domain in place of example.com, then count the lines that contain v=DMARC1, including V=DMARC1 or v = DMARC1. More than one is this finding. On Windows, use nslookup -type=TXT _dmarc.example.com. Details → on your result shows the same records.
Merge them
- Pick one record to keep. Ending the conflict puts its policy into force at once:
p=quarantinesends mail from any service you haven't set up to spam, andp=rejectrefuses it. Unless your reports already show every service you send through passing DMARC, set the kept record top=nonebefore you delete the other. The same goes forsp=andnp=in the kept record, which cover subdomains: set them tononeunless you've checked your subdomains' mail. - Copy every report address from the other record into its
rua=tag, separated by commas, so no recipient is lost. - Delete the other record at your DNS provider.
- Run the check again. One record should remain.
- Once the reports show your services pass, tighten the policy to
p=quarantine, thenp=reject.
The result shows:
More than one DMARC record
Receivers ignore DMARC when there is more than one record.Last updated .