Skip to main content
Configure DNS records provided by OneSignal to authenticate your sending domain. In most cases, DNS can be auto-configured from the OneSignal dashboard as described in the Email setup guide. Use this page when you need to add records manually.

​
Requirements

To manually configure DNS records, you must:
  • Own the sending domain.
  • Have access to DNS settings via your provider.
If you don’t own a domain, we recommend purchasing one via Cloudflare. This guide uses Cloudflare as an example, but most DNS providers work the same way.
Create an account at Cloudflare.com.Go to Domain Registration > Register Domains.
Cloudflare dashboard showing the Register Domains page

Cloudflare domain registration page

Search for an available name and purchase it.
Cloudflare domain search results with purchase option

Cloudflare domain purchase page

Once purchased, your domain will appear under Domain Registration > Managed Domains.
Cloudflare managed domains list showing the active domain

Cloudflare managed domains page

​
Add DNS records

Complete the Email setup steps until you’re prompted to add DNS records, then return here or use the Auto-Configure DNS button. From the OneSignal dashboard:
  • ⚠️ means the current DNS record does not match
  • ✅ means the current DNS record matches
Each DNS record needs to be added to your DNS provider. The exception is the MX record. You must have MX records configured, but they may point to a different mail server (e.g., Gmail).
OneSignal dashboard showing DNS records to copy into your provider

Copy DNS records from OneSignal into your DNS provider

In your DNS provider’s interface (e.g., Cloudflare), go to DNS > Records and add each record.

​
TXT records

  • Type: TXT
  • Name: OneSignal “Hostname”
  • Content: OneSignal “Value”
  • TTL: Auto or lowest
If you already have an SPF TXT record, do not create a second one. Append additional include: directives to the existing record:v=spf1 include:spf.onesignal.email include:mailgun.org include:your-other-spf-records ~all
Cloudflare interface for adding a TXT DNS record with hostname and value fields

TXT DNS record interface in Cloudflare

​
SPF (Sender Policy Framework)

Verifies the sending IP is authorized to send emails on your domain’s behalf.

​
DMARC

Adds policy enforcement for SPF and DKIM failures. DMARC is required for any domain that sends 5,000 or more emails per day to Gmail or Yahoo (the bulk sender threshold), and is strongly recommended for all senders. See Google’s Email Sender Guidelines and Google and Yahoo email sender requirements for the OneSignal-specific setup.
OneSignal uses the value v=DMARC1; p=none; for the DMARC record. If you already have a DMARC record, do not add a duplicate. Verify the existing record includes this policy or a stricter one (e.g., p=quarantine or p=reject).

​
CNAME records

Used for open, click, and unsubscribe tracking.
  • Type: CNAME
  • Name: OneSignal “Hostname”
  • Target: OneSignal “Value”
  • TTL: Auto or lowest
If using Cloudflare, set Proxy to “DNS only” and Flattening to “Off” for CNAME records. Other DNS providers typically do not require these settings.
Cloudflare interface for adding a CNAME record with hostname and target fields

CNAME DNS record interface in Cloudflare

​
DKIM (DomainKeys Identified Mail)

Verifies the message content was not altered and was sent by you. The public key is included in the CNAME DNS record provided by OneSignal.

​
MX records

Receives email responses and bounces. Even if you’re only sending, MX records help avoid domain verification errors.
If you already use another email provider (e.g., Gmail), do not overwrite existing MX records.
  • Type: MX
  • Name: OneSignal “Hostname”
  • Mail server: OneSignal “Value”
  • TTL: Auto or lowest
  • Priority: 10
Cloudflare interface for adding an MX record with mail server and priority fields

MX DNS record interface in Cloudflare

​
DNS verification & troubleshooting

After adding records:
  1. Return to your OneSignal dashboard.
  2. Click Check Records or the refresh button.
Verified records show ✅. All records should be verified except MX, which may show ⚠️ if it points to a different mail server (e.g., Google Workspace). This is expected and acceptable.
OneSignal dashboard showing DNS records with green checkmarks for verified status

Verified DNS records in the OneSignal dashboard

Verification typically takes a few minutes but can take up to 48 hours.

​
Troubleshoot DNS propagation

  1. Use whatsmydns.net to check propagation if any records are pending.
  2. For records that show ⚠️, copy the hostname from the OneSignal dashboard into the search bar and set the DNS type.
  3. Check the results: ✅ means the record is verified globally, ❌ means it has not propagated to that server yet.
If the value shown on whatsmydns.net differs from what OneSignal provides, check your DNS provider and update the record to match.
whatsmydns.net results showing global DNS propagation status with green and red indicators

Check DNS propagation with whatsmydns.net

​
Common errors & solutions

  • TXT SPF record isn’t verified
    • You likely have an existing SPF record. You should only have one SPF TXT record. Append additional include: directives to its value. See the TXT records section above.
  • DNS not fully propagated
    • If whatsmydns.net shows a mix of ✅ and ❌, the records have not fully propagated. This can take up to 48 hours. Wait and check again, or contact your DNS provider.
  • DNS value not matching OneSignal
    • If the values on whatsmydns.net don’t match what OneSignal provides:
      • MX records pointing elsewhere (e.g., Google Mail) are expected. This is fine as long as they show ✅ on whatsmydns.net.
      • Verify the hostname is correct. mail.yourdomain.com is not the same as yourdomain.com.
      • Contact your DNS provider for help.

​
FAQ

​
How long does DNS verification take?

Verification typically completes within minutes, but DNS propagation can take up to 48 hours depending on your provider and TTL settings. Use whatsmydns.net to check progress.

​
What if I already have SPF or DMARC records?

Do not create duplicate records. For SPF, append OneSignal’s include:spf.onesignal.email to your existing SPF TXT record. For DMARC, verify your existing record includes v=DMARC1; p=none; or a stricter policy.

​
Do I need MX records if I’m only sending emails?

MX records help avoid domain verification errors even for send-only configurations. If you already use a mail provider like Gmail or Google Workspace, keep your existing MX records. You do not need to overwrite them with OneSignal’s values.

​
My SPF record looks correct on external DNS checkers, but OneSignal still shows a warning. What should I check?

External DNS checkers confirm that a TXT record exists for your domain, but they do not verify that its value matches what OneSignal expects. A record can exist and still fail OneSignal’s check if the value is wrong or incomplete. To diagnose the mismatch:
  1. In the OneSignal dashboard, find the SPF record showing a warning and note the exact Hostname and Value shown.
  2. Open your DNS provider and locate the TXT record for that hostname.
  3. Compare the record value character-for-character against what OneSignal shows.
If you send email exclusively through OneSignal with no other email providers, the minimal valid SPF value is: v=spf1 include:spf.onesignal.email ~all If you use other senders, append their include: directives to the same record rather than creating a second SPF record. See What if I already have SPF or DMARC records? above.
Return to Email setup to complete configuration and begin sending emails.

Email setup

Complete email channel setup including provider selection and auto-DNS configuration.

Senders

Manage sending domains, reply-to addresses, and sender identities.

Email warm-up

Gradually increase email volume to build sender reputation and improve deliverability.

Email messaging

Compose and send email campaigns with templates, personalization, and scheduling.