Creating a Private Zone

Scenarios

Create a private zone to map a private domain name to a private IP address within a VPC.

Constraints

The domain name of the private zone you want to create and the VPCs associated with the private zone cannot conflict with the domain names configured in and VPCs associated with the DNS Resolver endpoint rules.

For example, if the example.com domain name is configured in an endpoint rule and VPC A is associated with the endpoint rule, you cannot create a private zone for example.com and associate VPC A with the private zone.

Procedure

1. Go to the Private Zones page.
2. In the upper right corner of the page, click Create Private Zone.
3. Configure the parameters.
   Figure 1 Creating a private zone
   
   Table 1 describes the parameters.

   Table 1 Parameters for creating a private zone

   Parameter	Description	Example Value
   Domain Name	Domain name you have planned for the ECS. You can enter a top-level domain that complies with the domain naming rules. For details about the domain name format, see Domain Name Format and DNS Hierarchy.	example.com
   Recursive resolution proxy for subdomains	If you select this option, when you query subdomains that are not configured in the zone namespace, DNS will recursively resolve the subdomains on the Internet and use the result from authoritative DNS servers.	-
   VPC	VPC to be associated with the private zone. NOTE: This VPC must be the same as the VPC where your other cloud resources are deployed. If the VPC is different, the domain name cannot be resolved.	-
   Email	(Optional) Email address of the administrator managing the private zone. Recommended email address: HOSTMASTER@Domain name For more information about the email address, see Why Was the Email Address Format Changed in the SOA Record?	HOSTMASTER@example.com
   Tag	(Optional) Identifier of the zone. Each tag contains a key and a value. You can add up to 20 tags to a zone. For details about tag key and value requirements, see Table 2. NOTE: If you have configured tag policies for DNS, you need to add tags to your private zones based on the tag policies. If you add a tag that does not comply with the tag policies, private zones may fail to be created. Contact the administrator to learn more about tag policies.	example_key1 example_value1
   Description	(Optional) Supplementary information about the zone. The description can contain no more than 255 characters.	This is a zone example.

   Table 2 Tag key and value requirements

   Parameter	Requirements	Example Value
   Key	Cannot be left blank. Must be unique for each resource. Can contain no more than 36 characters. Cannot start or end with a space nor contain special characters =*<>\,|/	example_key1
   Value	Cannot be left blank. Can contain no more than 43 characters. Cannot start or end with a space nor contain special characters =*<>\,|/	example_value1

4. Click OK.
5. Switch back to the Private Zones page.

   You can view the created private zone in the zone list.

6. Click the domain name to add record sets.

   On the Record Sets tab, click Add Record Set. For details about the parameters, see Record Set Overview.

   

   You can click the domain name to view SOA and NS record sets automatically added to the zone.

   • The SOA record set includes administrative information about your zone, as defined by the Domain Name System (DNS).
   • The NS record set defines the authoritative DNS servers for the domain name.

Follow-up Operations

After a private zone is created, you can perform the following operations:

• Add record sets for it. For details, see Record Set Overview.
• Modify or delete it, or view its details. For details, see Managing Private Zones.