How to set up spf dkim dmarc correctly is one of the first things to fix when messages from your business email keep going to spam. This guide shows the DirectAdmin workflow, the DNS records to check, and the tests that confirm Gmail can authenticate mail from your domain.
You can use the steps with any domain email that sends from your DirectAdmin hosting account. Replace example.com and the sample selector with your own domain and the values shown in your panel.
Have these ready before changing DNS:
example.com.hello@example.com.If your domain uses HostKarle nameservers (ns1.fastnsdns.com and ns2.fastnsdns.com), start with User Level → DNS Management in DirectAdmin. If DNS is hosted somewhere else, you must publish the records at that provider. DirectAdmin can sign the message with DKIM, but the receiving server can only verify it when the public DNS record is available.
Do not delete a working SPF record before checking it. SPF allows only one SPF policy at the root of a domain. If two TXT records both start with v=spf1, receiving servers can return a permanent SPF error.
SPF, DKIM and DMARC solve different parts of the same trust problem:
| Record | What it proves | DNS name to check |
|---|---|---|
| SPF | Which servers are allowed to send for your domain | @ or the root domain |
| DKIM | That the sending server signed the message and the signed content was not changed | your-selector._domainkey |
| DMARC | What a receiver should do when SPF or DKIM fails, and whether the result aligns with your From: domain | _dmarc |
Google recommends email authentication for all sending domains. For bulk senders—around 5,000 or more messages to personal Gmail accounts in a 24-hour period—Google requires SPF and DKIM authentication plus a DMARC policy, and it has been increasing enforcement on non-compliant traffic. Yahoo also publishes sender guidance built around SPF, DKIM and DMARC. Read the current Gmail email sender guidelines if you send newsletters or other high-volume mail.
Authentication cannot make an unwanted message welcome. Keep your mailing list permission-based, send from a real mailbox, avoid sudden volume spikes, and use a clear unsubscribe process for promotional mail. If messages still go to spam after authentication, see how to fix emails going to the Gmail spam folder.
Why: Your records must authorise every legitimate sender, while your test must query the DNS provider that recipients actually use.
hello@example.com.@example.com. A service that sends from its own domain does not need to be added to your domain’s SPF just because you use it.Success looks like: you know the complete list of senders and the one DNS dashboard where the public records must be published.
Why: SPF lets a receiving server compare the message’s sending server with the list authorised by your domain.
@, your full domain, or a blank host field. A DirectAdmin-generated SPF value commonly resembles this: v=spf1 a mx ip4:YOUR_MAIL_SERVER_IP ~all YOUR_MAIL_SERVER_IP with a guessed address. The authorised value must match the server that actually sends your mail.include: or IP mechanism to the same SPF value. Keep all senders in one record. Never create a second v=spf1 TXT record.Success looks like: one root TXT record begins with v=spf1, includes every real sender, and ends with the policy shown by your host or mail provider, such as ~all. Do not change the ending to -all until you have confirmed that every sender is included.
Why: DKIM adds a cryptographic signature to outgoing mail so the receiver can check that the domain’s mail system signed it.
x._domainkey. The selector is the part before ._domainkey; use the selector shown in your panel rather than assuming it is x.The DirectAdmin documentation explains that enabling DKIM signs outgoing mail and that an external DNS zone must contain the copied public key. See its DKIM and Exim instructions if you administer a DirectAdmin server rather than only a hosting account.
Success looks like: DirectAdmin reports DKIM as enabled, a public your-selector._domainkey.example.com TXT record exists, and the selector in that record matches the selector used by your sent message.
Why: DMARC connects SPF or DKIM authentication to the visible From: domain and gives receivers a policy for mail that fails.
_dmarc. Your DNS provider usually appends example.com, creating _dmarc.example.com. v=DMARC1; p=none p=none while you observe legitimate mail. It requests monitoring without telling the receiver to quarantine or reject failed messages._dmarc. If you later add aggregate reporting, first create or confirm the reporting mailbox and then add a valid rua=mailto:... value supplied by your mail administrator or reporting service.DMARC passes when SPF or DKIM passes and the authenticated domain aligns with the domain in the visible From: header. For example, mail sent as hello@example.com should authenticate for example.com or an aligned subdomain. A pass for an unrelated provider domain is not enough.
Success looks like: a public _dmarc.example.com TXT record returns v=DMARC1 and contains a policy such as p=none. Google lists p=none as the minimum DMARC policy for bulk senders; you can tighten the policy after reviewing reports and fixing legitimate senders.
Why: A record saved in a panel is not proof that the public DNS answer and the message headers are correct.
Run these commands from a computer with dig, replacing the domain and selector:
dig +short TXT example.com
dig +short TXT x._domainkey.example.com
dig +short TXT _dmarc.example.com You can also use Google Admin Toolbox Dig in a browser. Confirm that:
v=DMARC1.DNS changes can take time to appear at different resolvers. Test again later if the authoritative panel shows the record but a public query is still empty.
SPF: PASS, DKIM: PASS, and DMARC: PASS.From: address. If DKIM passes for a different domain, DMARC may still fail alignment.Success looks like: the public DNS checks return the expected records and Gmail shows all three authentication results as PASS for a fresh message.
permerrorSearch the root TXT results for every string beginning with v=spf1. Delete the duplicate policy only after checking that its sender mechanisms are included in the one record you keep. Also check that you have not exceeded SPF’s DNS lookup limit by adding too many nested include: mechanisms.
SPF can pass for the envelope sender while the visible From: domain is different. Check the Return-Path and From: values in Gmail’s original message. Configure your sending service to align them, or rely on a DKIM signature whose d= domain aligns with the From: domain.
none or failConfirm that DKIM is enabled in DirectAdmin and that the selector in the message matches the public DNS name you queried. If your DNS is external, copy the key there exactly. Remove old keys only when you know they are no longer used by any sender.
noneDMARC: none usually means the receiver could not find a valid _dmarc record. Query _dmarc.example.com, check for a spelling error, and remove duplicate DMARC records. A policy value of p=none is valid; it is not the same as a missing DMARC record.
Authentication is one part of delivery. Review recipient consent, message content, sending volume, bounce rates, and the domain or IP reputation shown in Gmail Postmaster Tools. Google says it cannot guarantee inbox placement for any provider, even when authentication passes.
Yes, publish all three when you send from your own domain. Gmail’s stricter bulk-sender requirements apply at around 5,000 messages per day to personal Gmail accounts, but authentication also helps ordinary business mail prove that it came from an authorised system.
Use the SPF value already generated for your DirectAdmin domain, because it contains the server details for your account. A common DirectAdmin pattern includes a, mx, the sending server IP and ~all, but do not copy a sample over a working record or guess the IP.
p=none enough for DMARC?It is a valid monitoring policy and the safest starting point while you identify all legitimate senders. It does not quarantine or reject failed messages. Review reports and message headers first, then ask your mail administrator whether quarantine or reject is appropriate.
No. Keep one SPF policy at the root and one DMARC policy at _dmarc. DKIM can have multiple selectors when different systems send mail, but each selector must have its own public key record.
The update time depends on the record’s TTL and cached answers at different DNS resolvers. Check the public record with dig and then send a fresh test message; do not judge a new record from an old message already sitting in an inbox.
Compare zoho mail alternatives for Indian businesses by rupee cost, IMAP access and mailbox limits,…
Compare Wix alternatives for Indian small businesses: see 3-year rupee costs, WordPress hosting, migration limits,…
Titan email price in India explained with mailbox costs, features, team totals and a comparison…
HostKarle vs Bluehost compares Indian shared hosting prices, renewal bills, email, SSL, backups, panels and…
Learn how to write blog in hindi with WordPress, Hindi typing tools, domain and hosting…
Compare Google Workspace alternatives in India by yearly rupee cost, email features and migration effort…
This website uses cookies.