Skip to content
English
  • There are no suggestions because the search field is empty.

DNS Updates

Learn how to update your DNS Configuration for email deliverability

DNS updates
To ensure your emails sent from commonsku are delivered successfully and avoid landing in spam folders, you’ll need to update your domain’s DNS records.

The person who manages your domain (usually, someone from your IT team or whoever set up your email) will need to log in to your provider and make the following DNS updates:

  1. Set up your SPF TXT Record:

There are two scenarios for SPF setup:

If you already have an SPF TXT record:

  • Find the existing record that starts with "v=spf1."

  • Add the following components:

    • ip4:107.23.94.186

    • ip4:54.240.34.60

    • ip4:54.240.34.61

    • include:amazonses.com

  • Your updated SPF should look like this:

    • v=spf1 YOUR PRE-EXISTING COMPONENTS ip4:107.23.94.186 ip4:54.240.34.60 ip4:54.240.34.61 include:amazonses.com ~all

 

All parts of the SPF record that start with include: (e.g., include:spf.protection.outlook.com) should be grouped together near the end of the record, just before the final directive (~all).

 

If you don’t have an existing SPF TXT record:

  • Create a new TXT record:

    • Type: TXT

    • Name: @

    • Data: v=spf1 ip4:107.23.94.186 ip4:54.240.34.60 ip4:54.240.34.61 include:amazonses.com ~all

    • TTL: 1 hr (or equivalent)

Only one SPF record should exist per domain.

Avoid duplicating v=spf1 or adding multiple ~all/-all endings.

2. Set up Your CNAME Records:

Once your SPF record is set up, the next step is to add your CNAME records.

Reach out to us at support@commonsku.com for your company's cname records. 


You will see a set of 3 unique records that you would need to add one by one:

Create a new CNAME record:

    • Type: CNAME

    • Name: Value under the Name column

    • Data: Corresponding Value 

    • TTL: 1 hr (or equivalent)

 

Important: Check your CNAME Host/Name format

Some DNS providers automatically add your domain name to the Host/Name field.

If your DNS verification remains Pending, check that your domain name has not been added twice to your CNAME records.

For example, if the CNAME provided by commonsku is:

abc123._domainkey.yourdomain.com

and your DNS provider automatically appends yourdomain.com, you may need to enter only:

abc123._domainkey

Otherwise, the record could be created as:

abc123._domainkey.yourdomain.com.yourdomain.com

which will prevent the CNAME from being verified.

If you're unsure, check how your DNS provider handles the Host/Name field or contact your IT/domain administrator before making changes.

3. Final Steps:

  • After updating your DNS, it may take 15 minutes to 72 hours for changes to fully propagate across the internet.

  • Once your records are verified, your email setup will be complete.

commonsku Tip: The updates mentioned above vary depending on which company is hosting your domain (GoDaddy vs. Google, etc.).  We suggest consulting with your company's IT support team for additional guidance on how to update your DNS effectively.

 

 

 

For any further information about this article or  DNS updates please reach out to support@commonsku.com 

 

Microsoft 365 email delivery issues

If your organization uses Microsoft 365 Defender, emails sent from commonsku may occasionally be flagged as spoofing or phishing.

This can happen because the email appears to come from your company email address (for example, yourname@yourdomain.com), while the message is sent through commonsku's email provider, Amazon SES. Microsoft 365 may detect that the sending service does not fully align with your domain's email authentication settings and block or quarantine the message.

Allow commonsku emails in Microsoft 365 Defender

Your Microsoft 365 administrator can allow these messages through the Tenant Allow/Block List.

In Microsoft 365 Defender:

  1. Go to Tenant Allow/Block List.
  2. Open Spoofed senders.
  3. Create an allow entry for the user whose email address is being used to send emails through commonsku.
  4. Configure the entry using:
    • Spoofed user: The user's company email address, such as yourname@yourdomain.com
    • Sending infrastructure: amazonses.com
    • Spoof type: Internal
  5. Save the allow entry.

An individual allow entry is required for each internal email address that sends emails through commonsku. For example, if 10 users send emails from commonsku using their company email addresses, you will need to create 10 allow entries.

SPF configuration

If your organization uses Microsoft 365 security features and manages its own DNS records, make sure your domain's SPF record also allows the services used to send email.

The SPF record should include:

v=spf1 include:spf.protection.outlook.com include:amazonses.com ip4:107.23.94.186 ip4:54.240.34.60 ip4:54.240.34.61 ~all

Important: A domain should have only one SPF record. If your domain already has an SPF record, do not create a second one. Instead, your IT administrator or DNS provider should update the existing SPF record to include the required values.