Docs

Container Registry

Domain name management

Domain name overview

Container Registry provides a system domain name and a default domain name for each instance and supports binding custom domain names. This topic describes the differences between domain name types and usage scenarios, helping you choose an appropriate domain name for accessing an instance.

tip

This feature is only available for Standard Edition instances.

Domain name types

tip

Both the system domain name and the default domain name can be used for operations such as docker login, docker push, and docker pull, and the results are identical.

If the instance name is changed, the default domain name is not automatically updated. We recommend that you prioritize using the system domain name in automation scripts to avoid access interruptions caused by instance renaming.

Domain name types	Format	Description	Typical application scenarios	Modifiable
System Domain Name	[instance name]-[region].cr.volces.com	The system domain name is automatically allocated by the system when the instance is created. It is generated based on the instance name and the region and uniquely identifies the instance. Both private network access and public network access are supported.	CI/CD pipelines, automation scripts. The system domain name is fixed and suitable for long-term use in configuration files.	Cannot be modified
Custom domain name	User-defined, for example, cr.example.com	A domain name that you bind. You must configure CNAME resolution at the DNS service provider. This domain name type applies to scenarios such as unified enterprise domain name management and hiding instance IDs.	Unified enterprise domain name standards and seamless domain name migration. When you change the domain name, you only need to update the DNS resolution. Existing configurations do not require changes.	Can be added and deleted
Default domain name	[instance name]-[region].cr.volces.com or [custom domain name]	When an instance is created, the default domain name equals the system domain name. You can use the default domain name feature to switch the default domain name to another bound custom domain name. After the switch, the command displayed in the console instance setup instructions uses the new default domain name.	Unified display for console operations. After you set the default domain name as a custom domain name, team members automatically use this domain name when copying push and pull commands.	Can be configured

Examples

The following examples show how to use different types of domain names to log in to an instance and push and pull images.

Use the system domain name

Use a custom domain name

After you create a custom domain name and configure DNS resolution, you can use the custom domain name instead of the system domain name for all operations:

Effects of setting a default domain name

After you set a custom domain name as the default domain name:

The command displayed in the console instance setup instructions automatically uses the custom domain name.

When team members copy push and pull commands in the console, the image addresses they obtain all use the custom domain name, and no manual replacement is required.

Configurations in existing scripts that use the system domain name or the previous default domain name remain valid and are not affected.

Related operations

Action	Description
Creating custom domain names	Bind a custom domain name to the CR instance and configure DNS resolution.
Managing custom domain names	View, modify, or delete bound custom domain names.
Setting default domain names	Set a bound custom domain name as the default domain name of an instance.
Viewing TrafficRoute resolution records	View the DNS resolution records of the instance domain name in TrafficRoute.
Adding public network access resolution records	Add a public network resolution record for the instance domain name so that external networks can access the instance via the domain name.

Last updated: 2026.09.23 14:37:25