Automated Domain Management in MEO lets you manage domains for multiple sites from one central location. As a platform administrator, you can set standard domain patterns at the Codebase or Environment level. You do not have to configure domain aliases manually for each site. When you save these settings, MEO creates secure domain URLs for your applications. You can use these URLs for tests, QA, content edits, and staging.

Automated Domain Management supports subdomain patterns. Path-based routing, such as [domain.com/site-id](https://domain.com/site-id), is governed separately under path-based domain management.

Key benefits

• Automation for all sites: The system creates standard URLs for new sites. It also applies updates to all current sites.
• Stable configurations: The system keeps URL structures the same across all environments. This gives you predictable URLs for QA, automatic tests, and CI/CD pipelines.
• Central control: You can set domain rules in one location. You do not have to change configurations for each site separately.
• Access control and audit logs: The system uses permissions to limit who can change patterns. It records all pattern changes in the audit logs.

How domain patterns work

A domain pattern uses regular text and dynamic tokens to create URLs. The system makes these URLs when it creates or updates a site.

The following table lists the supported dynamic tokens:

Example pattern

• Configured pattern: [site-id].[environment-id].domains.acme.com

• Generated URL: mysite.stage.domains.acme.com

Configuration hierarchy and override rules

Apply domain patterns at two administrative levels:

• Codebase level: Sets a baseline domain pattern across all environments associated with a specific codebase.

• Environment level: Sets a domain pattern for a specific environment, such as staging or dev.

Hierarchy rule: An Environment-level pattern overrides a Codebase-level pattern for all sites running in that environment.

Domain pattern management

Create or update a custom domain pattern at the codebase level

To create or update a custom domain pattern at the codebase level:

1. Sign in to the Cloud Platform user interface.

2. Click Codebases, and then select a codebase.

3. Click Domain Settings.

4. Do one of the following steps:

   1. To create a pattern, click Create custom domain pattern.

   2. To change a pattern, click Edit next to the pattern that you want to change.

5. In the New Domain Pattern field, enter your new template with dynamic variables. For example: [site-id].[environment-id].customdomain.com.

6. Review the Live Preview section to make sure that the system resolves your variables correctly.

7. In the Scope section, select Codebase.

8. Read the warning at the bottom of the dialog box. This message shows the number of domains or sites that this change affects.

Create or update a custom domain pattern at the environment level

To create or update a custom domain pattern at the environment level:

1. Sign in to the Cloud Platform user interface.
2. Click Codebases, and then select a codebase.
3. Click Environments and select an environment.

4. Click Domain Settings.

5. Open the pattern dialog box:

   • To create a pattern, select Create custom domain pattern.

   • To update an existing pattern, select Edit next to the current domain pattern.

After you save the pattern, the system propagates the domain pattern to all existing sites in that codebase or environment and applies it to newly provisioned sites.

Validation rules

• Single pattern limit: Configure only one domain pattern per Codebase and per Environment.

• Immutable fleet URLs: Domain URLs generated from standard patterns cannot be edited or removed at the individual site level to prevent configuration drift. Site managers can attach additional custom vanity domains.

• DNS label validation: The platform ensures that individual DNS labels, which are the string segments between dots, do not exceed the standard 63-character limit.

• High scalability: Supports fleets of up to 1,000 sites per environment without platform responsiveness degradation.

User permissions and access control

Managing domain patterns requires specific platform permissions:

• Add or remove domains for codebases: Grants authority to set or update codebase-level domain patterns.

• Add or remove domains for non-production environments: Grants authority to manage domain patterns on non-production environments, such as dev, stage, or UAT.

• Add or remove domains for production environments: Grants authority to manage domain patterns on production environments.

Audit logging and compliance To maintain security and compliance, all domain pattern creations and modifications generate an entry in the Customer Audit Log. Audit records track:

• The user who created or updated the pattern

• Timestamp of the modification

• Target Codebase or Environment

• Previous pattern string and newly applied pattern string

Limitations

• Primary production vanity domains: Automated Domain Management handles pattern-based non-production and testing aliases. Manage primary public-facing vanity domains, such as [www.brand.com](https://www.brand.com), individually through custom domain settings.

• Direct pattern deletion: Direct deletion of a domain pattern is planned for a future release. Administrators can modify existing patterns to update fleet URLs.

• Per-site pattern overrides: Individual sites cannot opt out of fleet-wide patterns to ensure system-wide predictability.

Automated Domain Management

Click Create or Save.

The system displays the success message.

In Custom Domain Pattern or New Domain Pattern, enter your domain syntax with dynamic site variables, for example, [site-id].[environment-id].customdomain.com.

The system displays the success message.

In Custom Domain Pattern or New Domain Pattern, enter your domain syntax with dynamic site variables, for example, [site-id].[environment-id].customdomain.com.