Below are several common scenarios for VPCDNS:
Domain Privacy Protection Scenario
Core system privacy protection ensures that the domain of internal core systems is not exposed to the Internet, which is safer.
Reverse Resolution Scenario
Private IP address reverse resolution allows IP addresses to be reverse-mapped to a domain, making network troubleshooting more intuitive.
Private Network Access Hijacking
You can use VPCDNS to create a private domain and associate it with a VPC, add resolution records to the private domain, and set resource mapping to implement private network hijacking capabilities. When you access the private domain within the VPC, the returned data will be the mapped resource you have previously set.
Cloud Service Resource Management
You can use private domain records to manage CVM hostnames in the VPC. For example, you can plan CVM hostnames based on the cloud servers' region, business scenario, server information, etc., and use the hostname information to add private domain and resolution records for those servers. These private domains will be inaccessible outside the VPC, facilitating an intuitive management of cloud service resources.
Cloud Service Resource Switching
Generally, to ensure the stable operation of a high-concurrency business, the business is distributed on multiple CVMs so they can share the pressure, and the same VPC can be established to enable mutual access between CVMs via private IPs. However, when a CVM is switched, its private IP will also change accordingly. Therefore, it is necessary to modify the business code and release the change, which is extremely inconvenient for the ops. In this case, you can create a private domain for each CVM in your VPC through private domain services and add resolution records pointing to the corresponding private IPs. The CVMs can access each other through the private network domain, and when a CVM is switched, you do not need to modify the CVM code. Instead, you only need to modify the resolution record of its domain.