This article explains how hostnames work in multitenant environments and how to use them correctly when sending campaigns from child instances.
Scope of Hostnames
When creating a hostname from a parent instance, it becomes available only for that instance and is not inherited by the child instances.
Additionally, it is important to note that the same custom hostname cannot be used in more than one instance. Each custom host is unique and associated with a single instance.
For this reason, if you want to use a specific hostname in a child instance, it will be necessary to configure it directly in that child instance and send the campaign from that same child instance.
Sending Campaigns with Custom Host
To send a campaign using a custom host, it is important to keep the following in mind:
The campaign must be created and managed from the child instance where you want to use the host.
The hostname must be previously configured in that same child instance.
| Note: It is not possible to create the campaign with custom hosts in the parent instance and expect the host to apply in the child instances. |
Use of Custom Domains
Unlike hostnames, custom domains can be used in child instances.
It is possible to select a custom domain when configuring campaigns in the parent instance/portal.
This domain is available to child instances, as they are owned by SMARTFENSE, and is properly recognized.
This allows maintaining consistency in sends without needing to replicate configurations in each instance.
Usage Recommendation
For proper implementation in multitenant environments:
Configure custom hosts directly in each child instance.
Create and manage campaigns from the instance where they will be sent if you want to use custom hosts.
Use custom domains when seeking a reusable configuration across instances.
Best Practices
Avoid configuring hosts only in the parent instance if they will be used by child instances.
Always validate in which instance the campaign is being created before sending it.