RD Station
How to set up SPF, DKIM and DMARC for RD Station
Authenticate RD Station Marketing email with the records generated for your account, a separate email subdomain and a policy-preserving DMARC check.
Check your current setup:
Before you start
RD Station Marketing generates the DNS records for your account. Its public FAQ describes five CNAME records for email and a separate landing-page record. This does not establish a universal breakdown into SPF, DKIM and DMARC records. Copy the names, types and values your account actually shows.
SPF authorizes servers using an SMTP sender domain. DKIM uses a private signing key and a public verification key in DNS. DMARC needs SPF or DKIM to pass with a domain aligned with the visible From address. One passing aligned mechanism is enough.
Choose a separate email subdomain, such as email.example.com. RD Station says email and landing pages cannot share the same subdomain. Identify the authoritative DNS provider before making changes; entries saved at a different provider have no effect. Keep copies of existing website, mail and campaign-link records.
Step 1: Get the account records
- Open Account > Settings > Domains and the email-domain configuration. Follow the account's setup or edit controls.
- Copy each generated record name, type and value. Do not copy another customer's targets.
- Compare the proposed names with existing DNS. A CNAME cannot share its name with TXT, MX or other data.
- If a name is occupied by an active service, ask RD Station support for a compatible configuration before replacing it. Old campaign links can depend on records that appear unused.
Publish changes at your DNS host, such as Registro.br, Locaweb or Cloudflare. Keep each account-generated record with its own name and type.
Step 2: Check SPF
If the account asks for include:_spf.rdstation.com.br, add it to the existing single SPF record at the name shown. If no SPF exists there, use the account's full value. Never create a second v=spf1 record: that causes permerror.
On 2026-11-09, _spf.rdstation.com.br published v=spf1 include:sendgrid.net ?all. Its include already reaches SendGrid, so do not add another include:sendgrid.net out of habit. A root-domain SPF change helps only when that root domain is used as SMTP MAIL FROM; a different bounce subdomain has its own authentication.
Check the complete record with the SPF checker. Nested includes count toward SPF's ten DNS-lookup terms. A neutral result inside an include is not a match, so evaluation continues in the outer record.
Step 3: Check DKIM
Publish every DKIM entry shown in your account, using the exact public key or CNAME target. On Cloudflare, set CNAME records to DNS only. Do not overwrite another sender's active selector.
Send a test campaign. Read s= and d= in its DKIM-Signature to identify the selector and signing domain, then use the DKIM checker. Check a passing result from the receiving provider. In relaxed mode, the signing domain must share its organizational domain with From; strict mode requires an exact match.
Step 4: Preserve DMARC
DMARC looks up a TXT policy at _dmarc under the actual visible From domain. For sender@example.com, check:
nslookup -type=TXT _dmarc.example.com 1.1.1.1
Replace example.com with your actual From domain. If no record appears there, ask your DNS administrator to confirm any effective inherited parent policy before creating one. Use the DMARC checker to inspect published records. Preserve the existing policy, alignment and rua destinations; do not create a duplicate or replace established enforcement.
If your account requests DMARC, inspect the existing record and any hosted CNAME target first. Preserve its policy, alignment settings and report destinations. Ask support if the account's verification cannot accept them; do not replace an established policy just to finish the wizard.
A name can have one DMARC policy record. If none exists and the account supports your own TXT policy, a first monitoring record can be:
v=DMARC1; p=none; rua=mailto:dmarc@example.com
Replace the example mailbox with your monitored reporting address. p=none states no DMARC handling preference; receivers can still filter or reject under other rules. Existing policies keep their settings and report addresses when you add a reporting destination.
Step 5: Verify before sending
Use the verification control displayed in your account. RD Station's public FAQ allows 24–72 hours for DNS changes, and its troubleshooting uses a 72-hour window. If entries remain pending, compare public DNS with the account and contact support. Do not send campaigns until the required authentication validates.
Run the DMARC checker and read reports from test campaigns. Preserve existing enforcement. For a first policy, monitor before considering quarantine; assess reject separately, including mailing-list and forwarding risks.
Common problems
- Landing pages and email share a subdomain. Use the account's edit control to assign distinct subdomains. Preserve needed links and DNS records during migration.
- Existing SendGrid records conflict. Keep records still used by another sender. Ask support for compatible alternative values and publish only those generated for your account.
- Two email configurations conflict. Ask support which configuration to retain. Do not delete active CNAMEs before checking old campaign links and validating replacement authentication.
- Two SPF records. Merge the required mechanisms into one record while preserving other legitimate senders.
- DNS values differ from the account. Compare the complete saved owner name, type and value. Some panels append the zone name automatically; strip only that suffix from the input.