How to add a DMARC record on LWS

📅 Last updated: June 2026

⏱ 3 min read

✅ All plans

Adding a Domain-based Message Authentication, Reporting, and Conformance (DMARC) rule entry is a mandatory protocol requirement to finalize your custom domain authentication loop. By deploying a DMARC policy framework with a monitoring policy set to none, you authorize receiving mailbox servers to properly audit your inbound campaign headers, dramatically stabilizing your long-term deliverability metrics.

Step-by-Step LWS DNS Zone Configuration Loop

To establish a clean monitoring policy, copy the security parameters displayed within your SystemeScale DNS records modal popup window and deploy them inside LWS using this progression sequence:

Access LWS DNS Zone Manager

Log directly into your central LWS customer account portal interface. Navigate to your domain asset directory, select the custom domain you are authenticating, and click to open its specific DNS zone dashboard.

Create a New Record Row

Locate the main record configuration table area to initiate a new entry. From the available Type column selector dropdown menu, choose strictly TXT.

Populate the Name and Value Parameters

Fill out the open record input cells carefully using this structured formatting rule:

Name field: Enter exactly _dmarc (matching the default string provided under the Name column in your workspace instructions popup).
Value field: Paste your custom DMARC string framework incorporating your active postmaster reporting address tag (e.g., v=DMARC1; p=none; rua=mailto:example@example.fr).

Save the Configuration Node

Verify the layout spacing across your raw text parameters, then click the Add button to commit and launch the rule node on the live nameserver network.

🛑

Strict Single-Record Architecture Rule

Your custom domain's active DNS zone must contain only one single DMARC record row entry. If you spot any pre-existing or legacy _dmarc rows within your LWS records index list table, permanently delete the old row blocks before saving the new rule node to prevent operational alignment conflicts.

Operational Insights: Data Reports & Monitoring Loops

Once your DMARC verification asset is visible across the public network layer, receiving email provider servers will compile and transmit automated telemetry logs summarizing your domain's outgoing email actions. These XML diagnostic reports route straight to the email address specified within your rua=mailto: variable definition.

💡

Dedicated Reporting Recommendations

Because ISPs submit reporting telemetry matrices on a daily cycle, these raw files can clutter your primary personal inbox folder. We strongly recommend setting up a dedicated management address (such as dmarc-reports@yourdomain.com) exclusively to capture these tracking files without filling up your primary commercial mail storage limits.

Please note that raw DMARC XML reports utilize a dense code format designed for specialized log analyzers. To learn how to parse and evaluate these files, review our technical interpretation guide: DMARC Reports: How to read and use them.

Network Propagation Tracking

To verify that your newly deployed LWS text records are fully functional across international tracking channels, run a public scan using MXToolbox DMARC Analyzer. Input your root domain into the query search field; a green success confirmation layout indicates that your authentication loop is active and successfully established.

Was this article helpful?

📄Why aren't my emails being sent?→ 📄How to confirm your email sender address→ 📄How to improve the deliverability of my emails (advanced tips)→ 📄Why do my emails arrive in the Gmail 'promotions' tab?→ 📄How to authenticate your domain name on LWS→