Understanding the Process

To install the Sender Authentication package on a third-party domain, teams need to follow a series of steps. First, they need to fill out the SAP form, asking for the dedicated IP and filling out the domain they want. They should also select that they will “not” self-host the DNS.

Next, they need to finish buying the domain, if they haven’t already, and then configure the DNS records on the domain. This is the part that may take longer, as the DNS needs to propagate properly. Teams can use a tool like https://dnschecker.org/ to track the progress, which can take a day or two.

After the DNS records are configured, teams need to configure the nameserver entries on the domain’s DNS. The nameservers should be set to ns1.exacttarget.com, ns2.exacttarget.com, ns3.exacttarget.com, and ns4.exacttarget.com. For more information, teams can refer to the Subdomain Delegation Guide.

Root Cause of Delays

The root cause of delays in installing the Sender Authentication package on a third-party domain is often the DNS propagation time. Teams need to ensure that they allow enough time for the DNS to propagate properly before configuring the nameserver entries.

Step-by-Step Fix

To install the Sender Authentication package on a third-party domain, teams can follow these steps:

SAP Form Configuration

Fill out the SAP form, asking for the dedicated IP and filling out the domain you want
Select that you will "not" self-host the DNS
Finish buying the domain, if you haven’t already
Configure the DNS records on the domain
Configure the nameserver entries on the domain’s DNS

Heads up: Teams should ensure that they have the necessary permissions and access to configure the DNS records and nameserver entries.

Checklist

• Ensure that the domain owner can take care of the setup
• Check the expected message volume to determine if a dedicated IP is required
• Fill out the SAP form and select that you will “not” self-host the DNS
• Finish buying the domain, if you haven’t already
• Configure the DNS records on the domain
• Configure the nameserver entries on the domain’s DNS
• Allow enough time for DNS propagation

Frequently Asked Questions

What is the Sender Authentication package?

The Sender Authentication package is a feature in Marketing Cloud that helps to authenticate the sender of an email and prevent spam filters from blocking emails.

Can I install the Sender Authentication package on a third-party domain?

Yes, you can install the Sender Authentication package on a third-party domain, but you need to ensure that the domain owner can take care of the setup and that the expected message volume does not require a dedicated IP address.

How long does DNS propagation take?

DNS propagation can take anywhere from a few hours to a few days, depending on the domain and the DNS provider.

What are the benefits of installing the Sender Authentication package?

The benefits of installing the Sender Authentication package include improved email deliverability, reduced spam filters, and increased trust with email recipients.

What are the requirements for installing the Sender Authentication package?

The requirements for installing the Sender Authentication package include filling out the SAP form, configuring the DNS records on the domain, and configuring the nameserver entries on the domain’s DNS.

Can I self-host the DNS for the Sender Authentication package?

No, you cannot self-host the DNS for the Sender Authentication package. You need to use the nameservers provided by Salesforce.