Provider documentation checked on 8 November 2026. Account-generated values, entitlements and current support remain deployment prerequisites.
Adobe Campaign domain setup is not interchangeable with Adobe Marketo Engage or Journey Optimizer. Identify the Campaign version, production instance and marketing or transactional use case before delegating a subdomain. This guide covers the documented Control Panel workflow; it does not assume that every self-hosted deployment has the same managed-service features.
Decide who will manage the subdomain
References: RFC 1034 §4.2.
Adobe documents full subdomain delegation and a CNAME-based alternative. Full delegation gives Adobe management of the required subdomain DNS. With CNAME setup, the customer retains responsibility for publishing and maintaining the supplied aliases. Choose a dedicated, unused subdomain, not the organization's main domain or an active name belonging to another service. Subdomain branding
Before starting, inventory the name's existing DNS, mail, tracking and web dependencies. A delegation is a change of authority for that subtree, not simply an extra authentication TXT record. Preserve the previous zone and name the owner of rollback and certificate responsibilities.
Use the selected instance’s wizard values
In Control Panel, open Subdomains & Certificates, select the production instance and start Setup new subdomain. For full delegation, Adobe directs the administrator to copy the nameserver information displayed by the wizard into the DNS hosting configuration, then submit the complete subdomain name and relevant use case. Adobe notes that the first configured subdomain becomes the primary subdomain for the instance and cannot later be changed in that workflow. New-subdomain setup
Adobe’s Nameservers configuration section also says not to create a separate zone file for the new subdomain; its preflight checks for conflicting existing authority. Have the DNS owner follow that specific delegation workflow, rather than treating this as a general prohibition on SOA records in DNS.
Use the exact nameserver record set displayed by the selected instance’s wizard. Retain that set with the change request and resolve any discrepancy with Adobe before changing authority; do not substitute a generic tutorial’s values.
Keep authentication, certificates and replies distinct
References: RFC 9989 §4.4, RFC 9989 §4.10.
After delegation or CNAME publication, verify the provider's configuration status, then inspect the DNS and mail identities produced for the route. Certificates protect web endpoints such as tracking pages; they are not DKIM verification keys. Reply-To handling is also separate from SPF and DKIM alignment. Adobe warns that the default Control Panel Reply-to inbox clears messages and cannot be reviewed. For replies that staff need to read, configure an approved monitored address instead and test receipt there. Do not use the default disposable inbox for customer support. Reply-to warning
Adobe's Control Panel DMARC record feature applies to fully delegated subdomains. For other arrangements, determine the appropriate DNS owner and workflow rather than assuming the same button controls the policy. Preserve a valid existing policy unless its owner approves a change. Campaign DMARC records
Validate the precise Campaign route
References: RFC 6376 §6, RFC 9989 §5.3.5.
Before using the new subdomain, wait for Adobe’s Deliverability audit to complete. Adobe says that audit can take up to ten business days after configuration and advises against using the subdomain before completion. DNS configuration alone is not the launch gate. Escalate a delayed audit to Customer Care rather than treating elapsed time as approval. Audit gate
Original test plan, after audit completion: send a harmless message from the intended production route to a controlled mailbox. Record visible From, envelope identity/SPF result, DKIM d=/s=/result and DMARC outcome from the trusted receiver. Also test the expected reply destination and tracking URL separately. A successful tracking redirect does not prove aligned email authentication.
Illustrative failure: a team delegates email.example.com successfully but selects a From address on another brand's domain. DNS completion for the delegated name alone does not establish alignment for that other brand. Resolve sender selection or the supported domain setup before launch.
Pause the affected campaign when evidence is missing. Do not undo an active delegation abruptly: queued mail, landing pages and links in messages already sent can depend on it. Plan any rollback with the DNS and Campaign owners. No customer tenant, production delegation or real message was tested here.