Custom Domains for Tenants

Overview

By default, tenants access their archive via a subdomain of your reseller base domain (e.g., acme.archive.yourcompany.com). For a more professional experience, tenants can configure their own custom domain (e.g., archive.acme.com) so the archive feels like a fully integrated part of their infrastructure.

How Custom Domains Work

When a tenant configures a custom domain, the system adds an entry to the tenant_custom_domains table. The platform then recognizes requests coming in on that domain and routes them to the correct tenant. The original subdomain continues to work alongside the custom domain.

The resolution order when a request arrives is:

1. Check if the hostname matches any custom domain in the tenant_custom_domains table
2. If no match, split the hostname into subdomain + base domain and look up the reseller and tenant
3. If no match is found, the request is rejected

DNS Setup

To use a custom domain, the tenant needs to create a DNS record pointing to the Easy Mail Archive infrastructure:

CNAME Record

Create a CNAME record for the desired subdomain:

archive.acme.com  CNAME  ingress.easymailarchive.com

The CNAME target will be provided by your reseller dashboard or our support team. DNS propagation usually takes a few minutes but can take up to 48 hours.

TLS Certificate

Once the DNS record is in place and propagated, Easy Mail Archive automatically provisions a TLS certificate for the custom domain. No manual certificate management is required. The certificate is renewed automatically before expiration.

Configuring a Custom Domain

Custom domains are configured on a per-tenant basis. As a reseller, you can set up custom domains for your tenants through our support team. Provide:

1. The tenant slug
2. The custom domain the tenant wants to use (e.g., archive.acme.com)
3. Confirmation that the DNS CNAME record has been created

After configuration, the custom domain typically becomes active within a few minutes.

Multiple Custom Domains

A tenant can have multiple custom domains configured simultaneously. This is useful for organizations that operate under different brand names or have regional domains. All custom domains route to the same tenant instance.

Removing a Custom Domain

To remove a custom domain from a tenant, contact our support team. After removal, the domain will no longer resolve to the tenant's archive. The tenant can still be accessed via its original subdomain.

Considerations

• DNS propagation - Allow time for DNS changes to propagate before testing the custom domain
• Email links - System emails (login codes, notifications) will use the tenant's primary access URL. If you want emails to use the custom domain, ensure it is set as the primary domain for the tenant.
• Bookmarks and links - After adding a custom domain, remind users to update their bookmarks if they were previously using the subdomain URL
• SSL/TLS - Certificates are provisioned and managed automatically. There is nothing you or the tenant need to do.