How to set up DMARC/DKIM/SPF for LocalNet
Published 22 Nov 2026
Updated 22 Nov 2026
11 min read
Summarize with

For a domain you own, set up LocalNet email authentication by publishing the SPF record supplied for your sending account, enabling DKIM signing with your domain, and adding a DMARC TXT record at _dmarc. Then send a real message through LocalNet and check the receiving server's results. DMARC passes when either SPF or DKIM passes with domain alignment to the visible From address.
I first check who owns the sending domain. If your address ends in @localnet.com, LocalNet controls its authentication records. Mailbox access does not grant DNS control. Custom-domain configuration requires your own domain; cPanel instructions apply only to hosting accounts that provide it.
Add your domain
I use the hosting account's control panel for custom-domain setup. LocalNet's public 'Checking Your E-mail Settings' article covers dial-up subscribers; LocalNet Hosting's 'Linux Web Hosting' page lists cPanel. Those are different account workflows.
- Open hosting access: Use the control-panel address and credentials supplied with your LocalNet Hosting account.
- Check the domain: Open cPanel > Domains. Keep an existing entry. Otherwise use Create a New Domain when available, or ask LocalNet to provision the domain.
- Locate public DNS: Check the domain's NS records. Edit authentication records at the authoritative DNS host, which is not necessarily your LocalNet control panel.
- Verify provisioning: Open Email > Email Accounts and confirm the domain is available. Create the required mailbox, then use Connect Devices for its account-specific outgoing server settings.
The public LocalNet documentation does not establish a universal domain-verification TXT value. Complete the ownership check supplied for your account. Keep working nameservers unless your hosting setup specifically requires a change.
cPanel menus depend on the account's version and enabled controls. Without cPanel, request your SPF value, DKIM public record and custom Return-Path configuration through LocalNet support.

Illustrative LocalNet Hosting cPanel screen for checking or adding a domain.
Set up SPF
I check the delivered Return-Path before choosing where to publish SPF. SPF authenticates the SMTP envelope sender, not the visible From address. For LocalNet custom-domain sending, verify that the envelope sender uses your domain or an appropriate subdomain.
- Get the account value: Open cPanel > Email > Email Deliverability > Manage for your domain. Copy the suggested SPF Name and Value, or request the approved record from LocalNet support.
- Merge existing senders: Edit the envelope-sender domain's existing SPF TXT record. Preserve authorized senders and one final all mechanism. Never add a second v=spf1 record at that name.
- Publish publicly: Use cPanel's installation or repair control when it manages authoritative DNS. Otherwise publish at your external DNS host.
- Confirm the Return-Path: Send a message and inspect Return-Path. If it still uses a provider-owned domain, ask LocalNet to provision a custom envelope sender for the account. Changing the visible From address is insufficient.
Keep SPF within 10 DNS-lookup-causing terms, including nested includes. Authorize LocalNet's approved outbound pool. One message's IP or smtp.localnet.com's current address does not establish that pool.
If Return-Path cannot use your domain, changing your From-domain SPF will not fix SPF alignment. Expect that error and require passing DKIM with your domain. DMARC can pass through DKIM.
SPF checker
Find SPF syntax issues, lookup limits, and weak records.
?/16tests passed
Check the exact envelope-sender domain with the SPF checker. Confirm that one valid record exists and that its evaluated mechanisms authorize LocalNet's actual outbound server.
Do not assume include:localnet.com is an approved SPF mechanism. Use the value supplied for your account, then test a new delivered message after DNS caches expire.

Illustrative LocalNet Hosting cPanel location for account-specific SPF and DKIM records.
Set up DKIM
DKIM needs an outgoing signature and its matching public DNS key. I verify both; a DNS key alone does not enable LocalNet signing.
- Open DKIM settings: Open Email Deliverability > Manage > DKIM. If no key exists, use Generate Local DKIM Key when available, or ask LocalNet to enable signing.
- Copy the public record: Copy the supplied DNS name and full public TXT value to authoritative DNS. Use the displayed selector. Do not assume it is default, and never publish the private key.
- Check the signature: Send through your production LocalNet route. Inspect DKIM-Signature for signing domain d= and selector s=. The d= domain must satisfy DMARC alignment.
- Require verification: Require the receiver's dkim=pass for that signature. A passing provider-domain signature alone does not authenticate your From domain.
Use 2048-bit RSA when supported. Preserve the full public key, including when the DNS host splits TXT data into strings within one record.
Default relaxed DMARC alignment accepts signing and From domains under the same organizational domain. Strict alignment requires an exact match.
Provider SPF alone
SPF passes for a provider-owned Return-Path. From is sender@example.com, with no passing DKIM for your domain. DMARC fails.
Your domain's DKIM
A verified DKIM signature has d=example.com. DMARC passes through DKIM despite the provider-owned Return-Path failing SPF alignment.
For unsigned website messages, configure the application to use your account's supported SMTP submission path and retest.
Without domain DKIM, SPF with domain alignment can still pass DMARC on direct delivery. Forwarding often breaks SPF, so test forwarded mail before enforcement.
Set up DMARC
For a domain without an enforcement policy, I start with p=none to collect reports. If you already use p=quarantine or p=reject, keep that policy while adding or correcting LocalNet authentication.
- Inspect the existing record: Query TXT records at _dmarc.example.com before making changes. Edit the existing DMARC record if present; do not create a competing record.
- Create the TXT entry: At authoritative DNS, add a TXT record at _dmarc.example.com. In cPanel Zone Editor, select Manage for the domain, then Add Record > TXT, enter the value and choose Save Record.
- Set the report destination: Replace the example reporting address with a working address that accepts aggregate DMARC reports. Keep any existing reporting destinations you still need.
- Keep matching relaxed: Leave adkim and aspf at their default relaxed settings unless you have tested every sender with strict settings. Save one valid DMARC record.
Use the DMARC record generator to build the TXT value. A p=none policy requests monitoring without DMARC enforcement.
For a newly monitored domain, use this value with your real reporting mailbox replacing dmarc@example.com. Preserve any existing quarantine or reject policy.
Initial TXT value at _dmarc.example.comtext
v=DMARC1; p=none; rua=mailto:dmarc@example.com
If the reporting mailbox is on another domain, its operator must provide external reporting authorization in DNS.
Check after existing DNS caches expire. A DMARC lookup validates publication and syntax; a delivery test validates the actual message.
DMARC checker
Look up a domain's DMARC record and catch policy issues.
?/7tests passed
Enter your visible From domain in the DMARC checker. Confirm the expected policy and reporting address, and resolve duplicate-record or malformed-value errors before continuing.
Use the fully qualified name where your DNS panel requires it. If the panel automatically appends your domain, enter only _dmarc. Verify that the result is _dmarc.example.com, without a duplicated domain suffix.

Illustrative LocalNet Hosting cPanel entry for a monitoring DMARC TXT record.
Verify and troubleshoot
I test actual outgoing mail, including website messages and forwarding paths. A green DNS status does not prove that every LocalNet sending route uses the expected identity or signing key.
- Send a fresh message: Send to the email tester's generated address through your normal LocalNet account. Repeat for each sending application.
- Read receiver results: Inspect the receiving service's Authentication-Results header. Check spf=pass, dkim=pass and dmarc=pass alongside their evaluated domains, not just the pass labels.
- Check SPF failures: Confirm the actual Return-Path and sending IP. Duplicate SPF records, missing outbound servers and excess DNS lookups need different fixes.
- Check DKIM failures: Compare the signature's d= and s= values with its public DNS key. For missing signatures or an incorrect signing domain, ask LocalNet to fix the sending configuration.
The email tester prompts you to send a message and returns a full diagnosis. This is the quickest check of DNS and actual sending behavior together.
Use a new message for each retest. An older message retains the signature and authentication results recorded when it was processed.
Email tester
Send a real email to this address. Suped shows a results button when the test is ready.
?/43tests passed
For an SPF pass with DMARC failure, compare the envelope-sender domain with the visible From domain. For a DKIM pass with DMARC failure, compare the signing domain instead. Both passes can authenticate a provider's domain without authenticating yours.
Check public DNS after the prior TTL expires. If cPanel shows a repaired value but public DNS still has another value, confirm that you edited the authoritative zone.
|
|
|
|---|---|---|
SPF permerror | Duplicates or lookups | Merge or simplify |
DKIM missing | Outgoing signature | Enable domain signing |
DKIM fail | Selector and key | Correct public key |
DMARC fail | Identity domains | Fix domain matching |
PTR warning | Outbound IP owner | Contact LocalNet |
Use message results to choose the next check.
Get alerted when it breaks
Suped is our DMARC reporting and email authentication platform. Its DMARC monitoring combines source-level analysis with issue notifications for ongoing LocalNet checks.
- Keep reports flowing: Use Suped's assigned reporting destination in your existing rua value. Preserve the policy and other required destinations.
- Enable issue notifications: Enable Issues detected and Sending sources need verification notifications for your DNS administrators. Use summary emails for routine review.
- Verify sending sources: Confirm LocalNet's IPs and authentication domains match your account traffic before marking the source verified.
- Resolve regressions: Use Suped's record diagnostics and DNS history to investigate changes. Follow the fix steps, then retest through LocalNet.
I review failures per source. An overall pass rate can hide a broken low-volume sender; unfamiliar traffic using your From domain needs separate investigation.
Use the receiving error and the authentication results together. A message can pass DMARC and still be filtered for reputation or content reasons.
Report-based alerts have a delay
DMARC aggregate reports follow the receiver's schedule, commonly daily. Suped notifications depend on available data. Use a fresh email test for immediate feedback on a configuration change.
Secure your domain with p=reject
Move to p=reject after every legitimate sending path consistently passes DMARC. I base that decision on source-level results across a complete sending cycle, including infrequent billing or application messages.
- Inventory all senders: Review LocalNet mailboxes, website submissions, forwarding and every other service using your From domain. Require a passing SPF or DKIM result with domain alignment for each direct sending path.
- Fix legitimate failures: Use Suped's source view and detailed authentication results to identify the failed identity. Correct LocalNet's DNS or signing setup and retest before changing the policy.
- Stage enforcement: For a domain starting at p=none, move to p=quarantine, review real delivery and report results, then use p=reject when legitimate traffic remains healthy. Keep existing stricter policies during LocalNet onboarding.
- Retain operational control: Use Suped's hosted policy controls when Hosted DMARC is configured, or edit the existing authoritative TXT record. Retain reporting destinations and review subdomain coverage before applying the policy broadly.
Suped's Hosted DMARC manages policy changes through the dashboard after its DNS setup. Source diagnostics identify legitimate senders needing fixes before enforcement.
For direct TXT publication, update the existing record with p=reject. Replace the reporting address, retain required tags and keep one DMARC record.
Final TXT value at _dmarc.example.comtext
v=DMARC1; p=reject; rua=mailto:dmarc@example.com
With no explicit subdomain policy, the parent policy also applies to applicable subdomains that lack their own DMARC record. Check those sending identities before tightening the parent domain.
A reject policy asks receivers to reject mail that fails DMARC, subject to receiver policy. Keep report review and alerts active after enforcement, especially when LocalNet changes outbound infrastructure or you add another sender.
Frequency asked questions
LocalNet controls the DNS and signing configuration for localnet.com. A mailbox customer cannot publish its SPF, DKIM or DMARC records. Ask LocalNet to investigate failed authentication on that address. Custom-domain DNS changes require a domain you control.
Public LocalNet documentation does not establish a universal SPF include. Use your account's suggested SPF value in cPanel or obtain the approved record from support. Do not guess include:localnet.com.
Use the selector shown in your account's DKIM DNS name or the s= value on a delivered DKIM-Signature header. Do not assume default. The public key must match the private key used by that sending account, and the receiver must verify the signature.
SPF can pass for a provider-owned Return-Path that does not have domain alignment with your visible From address. Configure the custom Return-Path through LocalNet where supported, or require passing DKIM with your domain. DMARC needs at least one passing authentication method with domain alignment.
I treat a PTR hostname ending in .localnet.com as a clue pointing toward LocalNet infrastructure, including customer connections. That inference does not prove hosted-mail use or authorization for your domain. Check the source IP against your account's approved servers and inspect SPF and DKIM identities before authorizing it.
Use authentication evidence rather than a fixed waiting period. Include normal and infrequent sending jobs in the observation period, fix legitimate failures, and check forwarding behavior before enforcement. If your domain is already at quarantine or reject, keep that policy while configuring LocalNet.

