Assume that you use domain names to connect to databases and you want to retain the original domain names of the databases after the databases are migrated to the cloud. In this case, you can bind the private domain names by using the private domain name feature.
Scenarios
You can bind a private domain name to each VPC-facing endpoint of PolarDB. Private domain names take effect in only the VPC that you specify in the current region. Private domain names have a higher priority for resolution than the domain names that take effect in the globe.
For example, the original domain name of a database is developer.aliyundoc.com, and the database is migrated to the PolarDB cluster. The endpoint of the PolarDB cluster is image.developer.aliyundoc.com. To allow the original domain name to remain unchanged, you can create a private domain name to bind developer.aliyundoc.com that is a CNAME record to image.developer.aliyundoc.com. After the domain name is bound to the endpoint, you can access the PolarDB cluster by visiting developer.aliyundoc.com in the specified VPC, as shown in the following figure.

Billing description
The private domain name feature of PolarDB is realized by mapping the private domain names that are managed by PrivateZone to the VPC-facing endpoints of PolarDB. PrivateZone charges a small amount of fee. For more information about pricing, see Pricing.
Bind a private domain name
Related API operations
API | Description |
---|---|
ModifyDBEndpointAddress | Modifies the endpoints of a PolarDB cluster, including the primary endpoint, default cluster endpoint, custom cluster endpoint, and private domain name. |