Skip to main content

​
Overview

If your location sends email notifications from a custom domain, inbox providers may treat those messages as spam unless you authenticate the sending domain.
For example, you use [email protected] as the sender for email notifications from Nexudus instead of [email protected].
This usually means updating your domain’s SPF record and adding DKIM CNAME records. Nexudus can then be included in your sending domain’s authorised mail sources without changing the way your team sends notifications in the dashboard. You’ll need to configure these settings from the domain provider that sends your notifications.

​
1. Add Nexudus to your SPF record

Add this fragment to your SPF record: include:_spf.nexudus.com For example, if your current SPF record is: v=spf1 include:spf.protection.outlook.com -all update it to: v=spf1 **include:_spf.nexudus.com** include:spf.protection.outlook.com -all The way you access and edit your SPF record in your DNS is different for each domain provider. You can find links to tutorials for some common providers below.

​
Common domain provider guides

​
2. Add the DKIM CNAME records

Add these two CNAME records to your DNS: For example, if your domain is coworking.com, the Name fields should be:
  • s1._domainkey.coworking.com
  • s2._domainkey.coworking.com

​
Common DNS provider guides

DNS changes can take up to 72 hours to fully propagate.