P H O T O N

CONSOLE

Loading

DNS Authentication Blueprint

How to Set Up DMARC for Email Deliverability
Step-by-Step DNS Implementation & Policy Rollout

Publish a valid DMARC TXT record in under 5 minutes. Learn tag syntax, configure aggregate reporting mailboxes, and safely enforce spoof protection without dropping legitimate emails.

6 min read • RFC 7489 Compliance • Tested DNS Blueprints
Direct Answer: Setting Up a DMARC Record

To set up a DMARC record, add a DNS TXT record at _dmarc.yourdomain.com with the value v=DMARC1; p=none; rua=mailto:dmarc-reports@yourdomain.com; pct=100. This enables monitoring without blocking legitimate mail before moving to p=quarantine or p=reject once all legitimate sending sources pass SPF and DKIM alignment.

1. What Does DMARC Do and Why Is It Mandatory?

DMARC (Domain-based Message Authentication, Reporting, and Conformance - RFC 7489) ties together SPF and DKIM authentication by validating that the domain visible in the From: header matches the authenticated domain.

Without DMARC, cybercriminals can easily spoof your domain in phishing attacks. Mailbox providers like Google, Yahoo, and Microsoft use DMARC to determine what to do with messages that fail authentication checks.

2. Anatomy of a DMARC Record: Tag Reference Table

A DMARC record is a standard DNS TXT record composed of semicolon-separated key-value pairs:

Tag Required? Valid Values Purpose
v Yes DMARC1 Specifies protocol version (must be uppercase)
p Yes none, quarantine, reject Policy applied to emails failing alignment
rua Recommended mailto:address@example.com Destination URI for daily aggregate XML reports
pct Optional 0 to 100 Percentage of messages subjected to policy (default: 100)
sp Optional none, quarantine, reject Policy specifically applied to subdomains
adkim Optional r (relaxed), s (strict) DKIM alignment mode (relaxed allows subdomains)

3. The 3 Phases of a Safe DMARC Rollout

Never jump directly to p=reject on day 1. Follow this proven 3-phase ramp:

Phase 1: Monitor (p=none)

Collect aggregate XML reports for 14–30 days. Identify all legitimate outbound email streams (CRM, transactional relay, helpdesk).

Phase 2: Quarantine (p=quarantine)

Instruct receiving mailboxes to route failing messages to Spam/Junk folder. Verify zero legitimate emails are impacted.

Phase 3: Reject (p=reject)

Instruct receiving servers to permanently reject any unauthenticated messages, achieving complete brand spoof protection.

4. Step-by-Step DNS Instructions

Log in to your DNS management console and add a new TXT record with the following values:

Type: TXT
Name / Host: _dmarc
Value: v=DMARC1; p=none; rua=mailto:dmarc-reports@yourdomain.com; pct=100
TTL: 3600 (or Auto)

5. Verifying Your DMARC Record from the Terminal

Once published, confirm your DNS record has propagated globally:

# Linux / macOS / Unix
dig +short TXT _dmarc.yourdomain.com

# Windows PowerShell
Resolve-DnsName -Name _dmarc.yourdomain.com -Type TXT | Select-Object -ExpandProperty Strings

Verify Your DMARC & DNS Health in 5 Seconds

Use Photon Console's free Deliverability Checker to inspect DMARC alignment, SPF lookup limits, and 2048-bit DKIM configuration.

6. Frequently Asked Questions

Starting with an observational policy (p=none) only collects aggregate XML reports and will never block legitimate emails. Senders should only transition to p=quarantine or p=reject after verifying that all third-party tools (CRMs, transactional relays, helpdesks) pass SPF and DKIM alignment.

rua specifies the email address for aggregate daily XML reports (e.g., mailto:dmarc-rua@yourdomain.com), which summarize overall authentication passes and failures. ruf specifies the address for real-time forensic failure alerts generated for individual spoofed messages.

Run 'dig +short TXT _dmarc.yourdomain.com' in Linux/macOS or 'Resolve-DnsName -Name _dmarc.yourdomain.com -Type TXT' in PowerShell. A successful response will return your published DMARC policy string.