All Products
Search
Document Center

PolarDB:Private domain name

Last Updated:Mar 30, 2026

Bind a custom private domain name to a Virtual Private Cloud (VPC)-facing endpoint of your PolarDB cluster. After binding, applications in the specified VPC resolve the custom domain to the PolarDB endpoint—so you can migrate databases to PolarDB without changing connection strings.

How it works

The private domain name feature uses PrivateZone to create a CNAME record that maps your custom domain to the PolarDB VPC-facing endpoint. You can bind a private domain name to each VPC-facing endpoint of PolarDB. DNS resolution for the private domain name is scoped to the VPC you specify in the current region and takes priority over globally-effective domain names.

For example, if your original database domain is developer.aliyundoc.com and the PolarDB cluster endpoint is image.developer.aliyundoc.com, you can create a private domain name that maps developer.aliyundoc.com (CNAME) to image.developer.aliyundoc.com. Applications in the specified VPC then connect using the original domain name without any configuration changes.

Private domain name scenario

Billing

The private domain name feature relies on PrivateZone, which charges a small fee. For pricing details, see Pricing.

Prerequisites

Before you begin, ensure that you have:

  • A PolarDB cluster with at least one VPC-facing endpoint

  • Access to the PolarDB console

Bind a private domain name

  1. Log on to the PolarDB console.

  2. In the upper-left corner, select the region where the cluster is deployed.

  3. Find the cluster and click its ID.

  4. On the Basic Information page, go to the Endpoints section. In the upper-right corner of the section, click the Switch icon to switch the view.

  5. On the right side of the VPC-facing endpoint, click Bind Private Domain Name.

    PG/O: Bind the private domain name

  6. In the Bind Private Domain Name dialog box, enter the prefix and suffix of the private domain name. The private domain name format is <prefix>.<suffix> (for example, mydb-prod.example.com). The following table describes each part.

    If the VPC where your PolarDB cluster resides is not associated with the selected zone, the system automatically binds the VPC to the zone.
    Binding a private domain name automatically creates the AliyunServiceRoleForPolarDB service-linked role. For details, see Service-linked roles for PolarDB.
    Field Description
    Prefix of a private domain name 6–40 characters. Allowed characters: lowercase letters, digits, and hyphens (-). Must start with a letter and end with a letter or digit.
    Suffix of the private domain name (zone) Select an existing zone from the drop-down list, or enter a new zone name. To view and manage zones, go to the PrivateZone console.

    Prefix and zone fields

  7. Click OK.

  8. In the Bind Private Domain Name dialog box, confirm the information about the domain name again and click OK.

API reference

API operation Description
ModifyDBEndpointAddress Modifies the endpoints of a PolarDB cluster, including the primary endpoint, default cluster endpoint, custom cluster endpoint, and private domain name.