Engagement - Marketing Cloud Engagement SAP DNS Requests

Requesting Changes

To request changes to your delegated SAP domain's DNS, create a support case with:

• Product: Marketing
• Topic: Email Deliverability
• Subject: Prefix with SAP DNS Request, the domain, and a short summary of the change. 
• Description: Provide the fully-qualified domain name, record type, and value. For example, a request to insert a Google Postmaster Tools verification code might look like:

A list of pre-approved requests is below. Contact support to inquire about the feasibility of other request types. 

Supported Requests

DMARC Policies

A simple DMARC policy is set on all newly-provisioned SAP domains, but can be customized to meet specific needs.

BIMI Records

Brand Indicators for Message Identification (BIMI) records are TXT entries containing a brand image URL. 

Verification Codes

Platforms that use or provide data on a domain may require verification codes - typically a TXT or CNAME record - to be set to demonstrate ownership. These include services like Google Postmaster Tools and Facebook Domain Verification.

SPF Policies

SPF policies exist as TXT records on sending domains. A global SPF policy is set on SAP domains by default, but the policy may be altered to limit it to specific sending IPs, or insert additional include clauses. 

CloudPages Domains

All SAP domains are configured with CloudPages service on the 'cloud' subdomain (e.g., cloud.email.company.com). If SAP DNS is delegated to Marketing Cloud Engagement, records for other CloudPages domains in the same subtree (e.g., red.email.company.com) can also be hosted at Marketing Cloud Engagement Engagement. Records at other CloudPages domains must be managed by the customer (e.g., blue.company.com).

Unsupported Requests

Most other records are not supported. Examples are below; this list is not exhaustive.

MX Records

Standard SAP configurations contain MX records targeting Marketing Cloud Engagement mail servers to support Reply Mail Management (RMM). These may need to be replaced if inbound mail should be directed to a third-party mail service. If so, DNS should be self-hosted. 

DKIM Keys (external)

We are unable to support DKIM keys associated with non-Salesforce sending platforms.