DMARC Record Not Found: How to Fix It

Why a DMARC record is not found

A DMARC lookup does not search the root of your domain. Receivers query a TXT record at _dmarc.example.com. Publishing the value at example.com, adding the full domain twice in a DNS panel, or creating the record in the wrong DNS provider are the most common reasons a checker returns not found.

The error can also be temporary. DNS changes need time to reach recursive resolvers, and a previous negative answer may remain cached until its TTL expires. Check which nameservers are authoritative before editing records so you do not update an inactive DNS zone.

Publish a valid starter record

Create one TXT record with the host _dmarc and a value such as v=DMARC1; p=none; rua=mailto:dmarc@example.com. Replace the reporting address with a mailbox that exists and can receive aggregate reports. Some DNS panels want only _dmarc in the host field; others accept the full name.

Start with p=none while identifying legitimate senders. A monitoring policy does not block spoofed mail, so move toward quarantine or reject only after real sending services pass aligned SPF or DKIM.

Verify the repair

Run a fresh DMARC lookup and confirm that exactly one v=DMARC1 record is returned. Then send a message through each mail platform and inspect Authentication-Results. DNS publication alone is not proof that DMARC passes; SPF or DKIM must also align with the visible From domain.