Setting up a new subdomain
Subdomain delegation from the Control Panel is available in beta, and subject to frequent updates and modifications without notice.
Full subdomain delegation
Control Panel allows you to fully delegate a subdomain to Adobe Campaign. To do this, follow these steps:
- In the Subdomains & Certificates card, select the desired production instance, then click Setup new subdomain .Subdomain delegation is available for production instances only.If the selected instance has no previously configured subdomains, the first subdomain delegated to Adobe will become the primary subdomain for that instance, you will not be able to change it in the future. Reverse DNS records will be created for other subdomains using the primary subdomain. Reply-to, and bounce addresses for other subdomains will be generated from the primary subdomain.
- Click Next to confirm the full delegation method.Note that CNAME and custom methods are currently not supported by the Control Panel.
- Create the desired subdomain and nameservers in the hosting solution used by your organization. To do this, copy-paste the Adobe Nameserver information displayed in the wizard. For more on how to create a subdomain in a hosting solution, refer to the tutorial video .When configuring nameservers, make sure you never delegate your root subdomain to Adobe . Otherwise, the domain will be able to work with Adobe only. Any other use will be impossible, like for example sending internal emails to your organization's employees.Moreover, do not create a separate zone file for this new subdomain.
- Once the subdomain is created with the corresponding Adobe nameserver information, click Next .
- Select the desired use case for the subdomain:
Breaking down your subdomains according to use cases is a best practice for deliverability . By doing so, the reputation of each subdomain is isolated and protected. For example, if your subdomain for marketing communications ends up being added to the block list by Internet Service Providers, your transactional communications subdomain will not be impacted, and will keep being able to send communications.You can delegate a subdomains for both Marketing and Transactional use cases :
- Marketing communications : communications that are intended for a commercial purpose. Example: sales email campaign.
- Transactional & operational communications : transactional communications contain information aimed at completing a process that the recipient has started with you. Example: purchase confirmation, password reset email. Organizational communications relate to the exchange of information, ideas, and views within and outside the organization, with no commercial purpose.
If you are using Campaign Classic, Control Panel allows you to see what RT/MID instances are connected to the Marketing instance that you are working with. For more on this, refer to the Instance Details section.
- For Marketing use cases, subdomains will be configured on MID (Mid sourcing) instances.
- For Transactional use cases, subdomains will be configured on ALL RT (Message Center / Real-time messaging) instances to ensure connectivity. The subdomains will therefore operate with all your RT instances.
- Enter the subdomain that you created into your hosting solution, then click Submit .Make sure you fill in the full name of the subdomain to delegate. For example, to delegate the "usoffers.email.weretail.com" subdomain, type "usoffers.email.weretail.com".
- Once the subdomain is submitted, the Control Panel will check that it correctly point to Adobe NS records and that the Start of Authority (SOA) record does not exist for this subdomain.Note that while subdomain delegation runs, other requests through the Control Panel will be entered into a queue and performed only after the Subdomain Delegation completes, to prevent any performance issues.
- If the checks are successful, the Control Panel will start setting up the subdomain with DNS records, additional URLs, inboxes etc.Eventually, the Deliverability team will be notified about the new subdomain, in order to audit it. The audit process can take up to 10 business days after the subdomain has been delegated. The checks that are performed include feedback loops and spam complaint loops testing. We therefore do not recommend using the subdomain before the audit has been completed, as it could result in bad subdomain reputation.You can get more details on the configuration progress by clicking the Process details button.Troubleshooting:
- In some cases, delegation goes through, but the subdomain may not be successfully verified. The subdomain will stay into the Configured list with a job log providing information on the error. Contact Customer Care if you have trouble resolving the issue.
- If the subdomain is being shown as “Unverified” after being configured, launch a new subdomain verification ( ... / Verify subdomain ). If it still shows the same status, the reason could be that there is some customisation done on recipients schema, which cannot be verified using standard processes. Please try sending out a campaign with that subdomain.
- If the subdomain configuration is taking too long (more than 10 business days) at deliverability audit step, please reach out to Customer Care.
At the end of the process, the subdomains will be configured to work with your Adobe Campaign instance and the elements below will be created:
- The subdomain with the following DNS records : SOA, MX, CNAME(s), DKIM, SPF, TXT,
- Additional subdomains to host mirror, resource, tracking pages and domain key,
- Inboxes : Sender, Error, Reply-to.By default, the "Reply-to" inbox from the Control Panel is configured to clear emails and is not reviewable. If you want to monitor your "Reply-to" inbox for your marketing campaigns, do not use this address.
You can get more details on the subdomain by clicking the Subdomain details and Sender info buttons.