Region Domain Name Change

The domain name is a critical part of the platform infrastructure, as it is used for environment access, internal communication between components, and various services operation. However, over time, there may be a need to change the domain name associated with a specific region due to rebranding, organizational changes, or other reasons. To facilitate this process and avoid extensive manual reconfiguration that is prone to errors, the platform provides built-in tools to automate the domain names management.

As a platform administrator, log in to the admin panel and navigate to the Regions section. Select the desired region and switch to the Domains tab, where you can perform the following actions:

• add domain - attach a new domain name to the region. All existing and newly created environments will be able to operate using this domain as well as all the previously existing domains.
• deactivate domain - disable a non-primary domain name (cannot be reactivated). New DNS records will not be generated for this domain. However, all the already existing records for the domain will remain indefinitely to ensure that internal communication within and between environments won’t be interrupted.
• change primary domain - switch the primary domain to another domain. The new primary domain will be used for internal communication between infrastructure components, reverse DNS zone, endpoint for internal infrastructure API calls, monitoring checks, infrastructure containers hostnames, and newly created user environment hostnames.
• manage domain SSL - handle SSL certificates for the domain. The process is the same as SSL for regions.

let’s review each of these actions in detail.

1. Click the Add button to attach a new domain name to the region. In the opened dialog, you need to specify:

• Region – automatically set as the currently selected region.
• Domain – provide a new domain name for the region. This domain should be delegated in advance, as described in the DNS Zones Delegation guide.
• Use as Primary – tick to change the primary domain to the current one immediately after addition (not recommended).

Be aware of the specifics when adding a new domain:

• Be patient, the process can take several minutes.
• Once added, domains cannot be removed (only disabled).
• Changes to the infrastructure region, usually the Default one, will also affect the user dashboard and admin panel URLs (app.{your-domain} and jca.{your-domain} respectively).
• Check the result window for errors and resolve them (if any).

Once a domain is added to the platform, all the existing environments in the region will be able to operate using this new domain (as well as all the previously existing domains). Also, all newly created environments and nodes will be provided with DNS records for all the active domains. Any infrastructure applications in the region will also be accessible via the new domain.

2. You can Deactivate any non-primary domain with the appropriate button in the tools panel. After deactivation, the domain cannot be re-activated, so you need to confirm the action.

Once deactivated, new DNS records will not be generated for that domain. However, due to possible domain records in configurations and scripts, all the already existing records will remain indefinitely to ensure that internal communication within and between environments won’t be interrupted.

3. In order to change the primary domain of the region, select any active domain and click the Use as Primary button in the tools panel.

After switching the primary, all the active domains will continue to work. However, the new primary domain will be used for:

• internal communication between infrastructure components
• reverse DNS zone
• endpoint for internal infrastructure API calls
• monitoring checks
• infrastructure containers hostnames
• newly created user environment hostnames

4. You can manage SSL certificates for each active domain in the panel.

The process is the same as described for the region’s primary domain (follow the linked guide above).

What’s next?

• Admin Panel Regions
• DNS Zones Delegation
• Network Isolation Settings
• Storing Failed Containers
• Distribution Optimization