Set up a DMARC record for your domain quickly using this simple step-by-step process in DirectAdmin. Ensure SPF and DKIM are already set up for the domain before adding DMARC.
Step 1: Create a Mailbox for DMARC Reports
Create an email address to receive DMARC reports, such as dmarc@yourdomain.com or spam-reports@yourdomain.com.
Step 2: Log in to DirectAdmin
Sign in to your DirectAdmin control panel.
Step 3: Open DNS Management
In DirectAdmin, go to DirectAdmin -> DNS Management.
Step 4: Click Add Record
Click the ADD RECORD button.
Step 5: Select TXT as the Record Type
For Record Type, select TXT.
Step 6: Enter the DMARC Host Name
In the Name field, enter _dmarc.
Leave the TTL set to 3600 unless you need to use a different value.
Step 7: Select DMARC as the TXT Record Type
For TXT Record Type, select DMARC.
Step 8: Choose the Policy Type
For Domain policy type, select None.
For Subdomain policy type, select None.
This creates a monitoring-only DMARC policy for both the main domain and its subdomains.
Step 9: Enter the Aggregate Report Address
In the Aggregate Email (RUA) field, enter the email address where you want to receive DMARC reports, such as dmarc@yourdomain.com.
Step 10: Leave the Optional Forensic Report Field Blank
Leave Forensic Email (RUF) blank unless you specifically want failure reports.
Step 11: Leave the Remaining Settings at Their Default Values
Leave Report Format as Authentication Failure Reporting Format.
Leave Reporting Interval set to 86400.
Leave Percentage set to 100.
Leave Alignment mode for DKIM set to Relaxed.
Leave Alignment mode for SPF set to Relaxed.
Step 12: Review the DMARC Value
DirectAdmin will generate the DMARC value automatically based on the options you selected.
A typical starting record will look like this:
v=DMARC1; p=none; sp=none; rua=mailto:dmarc@yourdomain.com; pct=100; adkim=r; aspf=rStep 13: Save the Record
Click the ADD button to save the DMARC record.
Step 14: Review Reports and Update the Policy Later
Start with a none policy so you can monitor reports and confirm that legitimate email is passing SPF and/or DKIM correctly.
Once valid email is authenticating properly, you can later change the policy to quarantine or reject for stronger protection.
