You can connect to and access the database cluster through the private network address of the cluster. After a cluster is created, the system automatically provides an IPv4 private network address for the cluster by default. You can also customize a private network domain name for the cluster through the console to better distinguish the database clusters connected by applications while also meeting enterprise compliance requirements. This document provides descriptions and operations related to the private network addresses and domain names of TDSQL-C for MySQL clusters.
Private Network Address Type
After the TDSQL-C for MySQL cluster is created, it can have private network addresses for read/write and read only, and private network access addresses for the database proxy. Certain private network addresses support custom private network domain names. For details of the types of private network addresses supported for mounting under the cluster and the corresponding supported custom private network domain names, see the table below.
|
Provisioned resource cluster Serverless cluster | Read-write instance | Private network address for read/write | The private network address for read/write points to the unique read-write instance under the cluster, and connecting to the database using this address can handle all write operations and read requests. | Supported |
Provisioned resource cluster Serverless cluster | Read-only instance | Private network address for read only | The private network address for read only points to the read-only instance under the cluster, and connecting to the database using this address can handle only read-only queries on this instance. | Supported |
Provisioned resource cluster | Analysis engine | Private network address for read only | The private network address for read only points to the analysis engine under the cluster, and connecting to the analysis engine nodes of the columnar storage using this address can handle complex analysis queries and real-time big data aggregation scenarios. | Not supported |
Provisioned resource cluster Serverless cluster | Database proxy | Private network access address | After the database proxy feature is enabled, the private network access address points to the database proxy under the cluster. This address provides a unified entry for the cluster, which automatically balances the load of read requests across multiple read-only instances, thereby reducing the load on the read-write instance under the cluster. | Supported |
Analysis cluster | Analysis engine | Private network address for read only | The private network address for read only points to the analysis engine under the analysis cluster, and connecting to the analysis engine nodes of the columnar storage using this address can handle complex analysis queries and real-time big data aggregation scenarios. | Not supported |
Viewing the Private Network Address and Port
Viewing the Private Network Address and Port for the Provisioned Resource Cluster/Serverless Cluster by Using the Following Method
2. Click the target cluster in the cluster list on the left to go to the cluster management page.
3. View the corresponding private network address and port on the cluster details page.
View the private network address and port of the read-write/read-only instance.
View the private network address and port of the analysis engine.
View the private network access address and port of the database proxy.
Viewing the Private Network Address and Port for the Analysis Cluster by Using the Following Method
2. Select MySQL (Analytic Cluster) at the top.
3. Click the target cluster in the cluster list on the left to go to the cluster management page.
4. View the corresponding private network address and port on the cluster details page.
Modifying the Private Network Address or Port
Note:
Modifying the private network address will impact the business of the database being accessed.
2. After the mouse pointer is moved to the private network address, click the edit icon.
3. In the pop-up dialog box, modify the private network address or port, and then click OK.
Private network address: You can customize the private network address within the optional range of the private network address.
Custom port: You can customize the port value, with a value range of 1024–65535.
Valid Hours of Old IPs: The default reclaim time for the system is set to 0 hours, indicating that the old IP address is reclaimed immediately, and the instance can no longer be accessed through the old IP address. Customization is supported, with a range of 0 to 168 hours.
Note:
If you modify the private network address after the private network domain name is enabled for an instance, the reclaim time for the old IP address is 24 hours by default and supports customization, with a range of 24–168.
Enabling the Private Network Domain Name
Enabling the Private Network Domain Name for the Read-Write Instance or Read-Only Instance in the Provisioned Resource Cluster/Serverless Cluster
2. Click the target cluster in the cluster list on the left to go to the cluster management page.
3. Under the cluster details page, find the target instance, and click Details to go to the instance details page.
4. Click Enable next to the Read-Write Intranet Domain Name or Read-Only Intranet Domain Name in the Connection Information section.
5. Edit the private network domain name of an instance in the pop-up window, and click Next.
Note:
The complete domain name format is <custom part>.<instance ID>.internal.tencentdb.com. For example, andy125.cynosdbmysql-ins-pajhe***.internal.tencentdb.com. You can edit the custom part, which should start with a letter, end with a digit or letter, and consist of lowercase letters, digits, and hyphens (-). Entering 6–40 characters is supported. If the custom part is left unspecified, the domain name is generated by the system automatically.
6. Confirm the domain name in the pop-up window and click OK.
Before clicking OK, you can click Back to return for modification, if you need to modify the private network domain name.
Before clicking OK, you can click Cancel if you do not want to enable the private network domain name.
Enabling the Private Network Domain Name for the Database Proxy in the Provisioned Resource Cluster/Serverless Cluster
2. Click the target cluster in the cluster list on the left to go to the cluster management page.
3. Select the Database Proxy tab, and click Enable under Connection Address > Intranet Domain Name.
4. Edit the private network domain name of a database proxy in the pop-up window, and click Next.
Note:
The complete domain name format is <custom part>.<database proxy resource ID>.internal.tencentdb.com. For example, testproxy.cynosdbmysql-proxy-7eje***.internal.tencentdb.com. You can edit the custom part, which should start with a letter, end with a digit or letter, and consist of lowercase letters, digits, and hyphens (-). Entering 6–40 characters is supported. If the custom part is left unspecified, the domain name is generated by the system automatically.
5. Confirm the domain name in the pop-up window and click OK.
Before clicking OK, you can click Back to return for modification, if you need to modify the private network domain name.
Before clicking OK, you can click Cancel if you do not want to enable the private network domain name.
Modifying or Disabling the Private Network Domain Name
Note:
After modifying the private network domain name, you need to manually update the private network domain name used for access in the application to maintain database connection.
If you enable the private network domain name, modifying the private network address will not affect the connection between the application and the database through the private network domain name.
After the private network domain name is disabled, the domain name connection becomes unavailable. Please ensure that your applications do not require connecting through the private network domain name before you disable the private network domain name.
Modifying or Disabling the Private Network Domain Name for the Read-Write Instance or Read-Only Instance in the Provisioned Resource Cluster/Serverless Cluster
2. Click the target cluster in the cluster list on the left to go to the cluster management page.
3. Under the cluster details page, find the target instance, and click Details to go to the instance details page.
4. If you need to modify the private network domain name, you can click the edit icon next to the Read-Write Private Domain Name or Read-Only Private Domain in the Connection Information section. Modify the private network domain name in the pop-up window, click Next, and then click Confirm.
5. If you need to disable the private network domain name, you can click Disable next to the Read-Write Private Domain or Read-Only Private Domain in the Connection Information section, and then click OK in the pop-up window.
Modifying or Disabling the Private Network Domain Name for the Database Proxy in the Provisioned Resource Cluster/Serverless Cluster
2. Click the target cluster in the cluster list on the left to go to the cluster management page.
3. Select the Database Proxy tab.
4. If you need to modify the private network domain name, you can click the edit icon next to the target private network domain name under Connection Address. After the private network domain name is modified in the pop-up window, click Next, and then click OK.
5. If you need to disable the private network domain name, you can click Disable next to the target private network domain name under Connection Address, and then click OK in the pop-up window.