PrivateZone helps you manage your ECS hostnames by making machine information more human readable.
For example, an enterprise (example.com) has 50 ECS instances in the VPC placed in Zone E of China (Beijing). Among the 50 instances, 20 are used for the official website, 20 are used for mobile application, and the other 10 are used for internal testing. For this example scenario, we recommend that you configure the hostnames as follows.
- Set the 20 hostnames for the official website in the format of web01.huabei2-e.example.com.
- Set the 20 hostnames for mobile apps in the format of m01.huabei2-e.example.com.
- Set the 10 hostnames for internal testing in the format of test01.huabei2-e.example.com.
Hostnames in this format indicate the use of the corresponding instances. This makes it easier to manage your ECS instances compared to the ssh, ping, and scp protocols.
Internal API calls save you from modifying system codes when the corresponding IP addresses change.
For example, an enterprise (example.com) wants to obtain account authentication information by calling an internal API operation. The API cannot be exposed to the Internet due to privacy concerns.
In this example, the enterprise can assign
account.inner.example.com to the API and point the domain name to a reserved IP address
10.23.45.67. When the API IP address changes to
10.45.67.89, you only need to point
account.inner.example.com to the new IP address in the PrivateZone console, without modifying the code that calls the API.
You can protect the privacy of your system using PrivateZone because internal domain names will not be exposed to the Internet.
Your information can only be accessed in specified VPCs.
PrivateZone supports reverse lookup that maps IP addresses to domain names. This makes it easier for you to troubleshoot network issues.
For example, an enterprise (example.com) performs a reverse lookup in PrivateZone so that it can identify the host associated with a specified private IP address using traceroute, host, or other commands.