By default, you can use an account to create up to 50 public zones, 50 private zones, 50 PTR records, and 500 record sets.
-If the quotas do not meet your service requirements, contact customer service to request an increased quota.
+The default quotas for an account are 50 public zones, 50 private zones, 50 PTR records, and 500 record sets.
+If the quotas do not meet your service requirements, contact customer service for higher quotas.
What Can I Do If the System Prompts that the Domain Name Already Exists When I Create a Public Zone?
-If the system prompts that the domain name has been created by another user when you create a public zone, send an email to cloud-products@telekom.de for identity authentication. After the authentication is approved, the system sends an email to notify you that you can re-create the zone.
-- Involved domain name
- Evidence that proves you have registered the domain name, for example, the proof of purchase or the email notifying that the domain name is valid for you
What Can I Do If There Is Message Indicating that the Public Zone Already Exists?
+If there is a message indicating that the public zone you are creating has been created by another user, send an email to cloud-products@telekom.de for identity authentication. After your identity is authenticated, you will receive an email to notify you that you can re-create the zone.
+- Your domain name
- Evidence that proves you have registered the domain name, for example, the proof of purchase or the email notifying that the domain name is valid for you
Why Was the Email Address Format Changed in the SOA Record?
When you add a record set, you can enter an email address to receive error information and problem reports of the domain name. However, based on RFC 2142, we strongly recommend that you use HOSTMASTER@Domain name as the email address.
-Because the at sign (@) has a special meaning in the SOA record set, the system replaces it with a period (.) and includes a backslash (\) before the period in the label before the at sign, but emails are still sent to the email address you specify. For more information, see RFC 1035.
+Because the at sign (@) has a special meaning in the SOA record set, the system replaces it with a dot (.) and includes a backslash (\) before the dot in the label before the at sign, but emails are still sent to the email address you have specified. For more information, see RFC 1035.
For example, if you enter test.hostmaster@example.com when you create the zone, the email address displayed in the SOA record set is test\.hostmaster.example.com.
Does DNS Support Wildcard Entries?
-DNS allows you to configure wildcard entries.
+Yes. DNS allows you to configure wildcard entries.
A wildcard entry is a record set that uses an asterisk (*) as the name and matches requests for any domain name based on the configuration you set. For more information, see RFC 4592.
-DNS supports wildcard entries for the following record set types: A, AAAA, MX, CNAME, TXT, CAA, and SRV.
+DNS supports wildcard entries for the following record set types: A, AAAA, MX, CNAME, TXT, PTR, CAA, and SRV.
How Are Zones Queried to Resolve a Domain Name?
When a domain name resolution request is initiated, a matched subdomain is first queried.
- If a zone is created for the subdomain, the system returns the result based on the zone configuration.
- If a zone is not created for the subdomain, the system queries the domain name in the zone created for the domain name.
For example, suppose you have created one zone named example.com and added an A record set to it, with the Name field set to www, and you have also created another zone named www.example.com but have not added an A record set to this zone.
-If a visitor accesses www.example.com, the domain name is first queried in the zone named www.example.com. However, no result will be returned because no record sets have been added to the zone.
+For example, suppose you have created one zone for example.com and added an A record set with the Name field set to www. You have also created another zone for www.example.com without an A record set.
+If an end user accesses www.example.com, the domain name www.example.com is first queried. However, no result will be returned because no record sets have been added to the zone.
How Can I Configure a PTR Record to Map the IP Address of an ECS to a Domain Name?
-PTR records enable users to query domain names based on IP addresses.
-To map the private IP address of an ECS to a domain name, you must create a private zone and create a PTR record in the zone.
-To map the EIP of the ECS to a domain name, refer to Creating a PTR Record.
-
The domain name in a PTR record must be in the x.x.x.x.in-addr.arpa format. in-addr.arpa is the domain name suffix used for reverse resolution.
-For example, if the private IP address is 192.168.1.10, the domain name in the PTR record must be 10.1.168.192.in-addr.arpa.
-In this case, you must create a private zone named 192.in-addr.arpa and add a PTR record with its value set to 10.1.168.192.in-addr.arpa.
+How Can I Map the Private IP Address of an ECS to a Domain Name?
+You can configure PTR records to allow end users to query domain names based on IP addresses.
+To map the private IP address of an ECS to a domain name, you must create a private zone and add a PTR record to the zone.
+To add a PTR record, you may refer to Creating a PTR Record.
+ The domain name for the PTR record must be in the x.x.x.x.in-addr.arpa format. in-addr.arpa is the domain name suffix used for reverse resolution.
+For example, if the private IP address is 192.168.1.10, the domain name is 10.1.168.192.in-addr.arpa.
+You need to create a private zone with the domain name set to 192.in-addr.arpa and add a PTR record with the Name field set to 10.1.168.
Creating a Private Zone
- Log in to the management console.
- In the service list, choose Network > Domain Name Service.
The DNS console is displayed.
- - In the navigation pane, choose Private Zones.
The Private Zones page is displayed.
- - Click
in the upper left corner and select the desired region and project. - Click Create Private Zone.Figure 1 Create Private Zone-
- Set the parameters based on Table 1.
+
Creating a Private Zone
- Log in to the management console.
- In the service list, choose Network > Domain Name Service.
The DNS console is displayed.
+ - In the navigation pane on the left, choose Private Zones.
The Private Zones page is displayed.
+ - Click
in the upper left corner and select the desired region and project. - Click Create Private Zone.Figure 1 Create Private Zone+
- Configure the parameters based on Table 1.
-
Table 1 Parameters for creating a private zone Parameter
Description
+Description
Example Value
+Example Value
Name
+Domain Name
Domain name
-Set the domain name suffix to in-addr.arpa.
+Domain name you use to access the cloud servers or cloud services.
+Ensure that the domain name suffix is in-addr.arpa.
192.in-addr.arpa
+192.in-addr.arpa
VPC
VPC to be associated with the private zone
+VPC to be associated with the private zone.
Select the VPC you want to associate with the private zone.
N/A
+N/A
Email
(Optional) Email address of the administrator managing the private zone
-It is recommended that you set the email address to HOSTMASTER@Domain name.
+(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
+HOSTMASTER@example.com
Tags
+Tag
(Optional) Identifier of a resource
+(Optional) Identifier of a resource
Each tag contains a key and a value. You can add a maximum of 20 tags to a zone.
For details about tag key and value requirements, see Table 2.
example_key1
+example_key1
example_value1
Description
(Optional)
+(Optional)
Supplementary information about the zone
You can enter a maximum of 255 characters.
This is a private zone.
+This is a private zone.
Table 2 Tag key and value requirements Parameter
+-Table 2 Tag key and value requirements Parameter
Requirements
Key
- Cannot be left blank.
- Must be unique for each resource.
- Can contain a maximum of 36 characters.
- Cannot be left blank.
- Must be unique for each resource.
- Can contain a maximum of 36 characters.
- Can contain only letters, digits, hyphens (-), at signs (@), and underscores (_).
example_key1
Value
- Cannot be left blank.
- Can contain a maximum of 43 characters.
- Cannot be left blank.
- Can contain a maximum of 43 characters.
- Can contain only letters, digits, hyphens (-), at signs (@), and underscores (_).
example_value1
- Click OK.
- Switch back to the Private Zones page.
View the created private zone. -Click the zone name to view zone details. You can view SOA and NS record sets automatically generated by the system.
-- The SOA record set defines the DNS server that is the authoritative information source for a particular domain name.
- The NS record set defines authoritative DNS servers for a zone.
- Click OK.
- Switch back to the Private Zones page.
You can view the created private zone in the private zone list. Click the domain name to view SOA and NS record sets automatically generated for the zone.
+- The start of authority (SOA) record 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.
Adding a PTR Record
- On the Private Zones page, click the name of the private zone that you have created.
The Record Sets page is displayed.
+Adding a PTR Record
- On the Private Zones page, click the domain name of the private zone you created.
The Record Sets page is displayed.
- Click Add Record Set.
The Add Record Set dialog box is displayed.
-Figure 2 Add Record Set-
- Set the parameters based on Table 3.
-
Table 3 Parameters for adding a PTR record Parameter
+Figure 2 Add Record Set+
- Configure the parameters based on Table 3. +
-Table 3 Parameters for adding a PTR record Parameter
Description
+Description
Example Value
+Example Value
Name
+Name
IP address in the PTR record (typed in reverse order)
+Part of the private IP address in reverse order.
10.1.168
-For example, if the IP address is 192.168.1.10, the domain name in the PTR record is 10.1.168.192.in-addr.arpa.
-- If the private zone name is 192.in-addr.arpa, enter 10.1.168 in the box.
- If the private zone name is 1.168.192.in-addr.arpa, enter 10 in the box.
10.1.168
+For example, if the IP address is 192.168.1.10, the domain name in the PTR record must be 10.1.168.192.in-addr.arpa.
+- If the domain name is 192.in-addr.arpa, enter 10.1.168.
- If the domain name is 1.168.192.in-addr.arpa, enter 10.
Type
+Type
Type of the record set
+Type of the record set.
PTR – Map IP addresses to domains
+PTR – Map IP addresses to domains
TTL (s)
+TTL (s)
Cache duration of the record set, in seconds
+Cache duration of the record set, in seconds.
The default value is 300, which is, 5 minutes.
+Default value: 300
Value
+Value
Domain name mapped to the IP address
+Domain name mapped to the IP address.
You can enter only one name.
mail.example.com
+mail.example.com
Tags
+Tag
(Optional) Identifier of a resource
+(Optional) Identifier of a resource
Each tag contains a key and a value. You can add a maximum of 20 tags to a record set.
For details about tag key and value requirements, see Table 2.
example_key1
+example_key1
example_value1
Description
+Description
(Optional) Supplementary information about the PTR record
+(Optional) Supplementary information about the PTR record.
The PTR record is for reverse resolution.
+The PTR record is for reverse resolution.
- Click OK.
- Switch back to the Record Sets page.
View the added record set in the record set list of the zone and ensure that the status of the record set is Normal.
+- Click OK.
- Switch back to the Record Sets tab.
@@ -172,10 +172,3 @@ - - \ No newline at end of file diff --git a/docs/dns/umn/dns_faq_032.html b/docs/dns/umn/dns_faq_032.html index 0291267b..960168ea 100644 --- a/docs/dns/umn/dns_faq_032.html +++ b/docs/dns/umn/dns_faq_032.html @@ -1,24 +1,24 @@The added record set is in the Normal state.
What Is CAA?
-Certification Authority Authorization (CAA) is a way to ensure that SSL certificates are issued by authorized certificate authorities (CAs). CAA complies with all RFC 6844 requirements. As of September 8, 2017, all CAs are required to check CAA records before they can issue certificates.
-CAA Specifications
Domain name owners can create CAA records to specify authorized CAs that can issue SSL certificates.
-For security reasons, only authorized CAs can issue SSL certificates for the domain names used by your website. Setting CAA records enhances security for your website.
-CAs will perform a DNS lookup for CAA records when they issue certificates.
-- If a CA does not find a CAA record, it can issue a certificate for the domain name.
Any other CAs can also issue certificates for this domain name. Insecure certificates may be issued, and messages indicating that your website is insecure when users access your website.
- - If the CA finds a CAA record that authorizes it to issue certificates, it will issue a certificate for the domain name.
- If the CA finds a CAA record but the record does not authorize it to issue certificates, the CA will not be able to issue SSL certificates for the domain name.
Certification Authority Authorization (CAA) is to ensure that HTTPS certificates are issued by authorized certificate authorities (CAs). CAA complies with all IETF RFC 6844 requirements. As of September 8, 2017, all CAs are required to check CAA record sets before they can issue certificates.
+-CAA Specifications
Domain name owners can create CAA record sets to specify authorized CAs that can issue SSL certificates.
+Only authorized CAs can issue SSL certificates for the domain names used by your website. Setting CAA record sets enhances security for your website.
+CAs will perform a DNS lookup for CAA record sets when they issue certificates.
+- If a CA does not find a CAA record set, the CA can issue a certificate for the domain name.
Other CAs can also issue certificates for this domain name, but these certificates may be insecure, and there will be messages indicating that your website is insecure when end users access your website.
+ - If a CA finds a CAA record set that authorizes it to issue certificates, the CA will issue a certificate for the domain name.
- If a CA finds a CAA record set that does not authorize it to issue certificates, the CA will not be able to issue SSL certificates for the domain name.
CAA Record
A CAA record consists of a flag byte [flag], a property tag, and a property value [tag]-[value]. You can create multiple CAA records for a domain name.
+CAA Record Set
A CAA record set consists of a flag byte [flag], a property tag, and a property value [tag]-[value]. You can create multiple CAA record sets for a domain name.
-Table 1 Configuration of CAA records Function
+-Table 1 Configuration of CAA record sets Function
Example
+Example CAA Record Set
Description
Configure a CAA record for one domain name.
+Configure a CAA record set for one domain name.
0 issue "ca.example.com"
0 issue ";"
No CA is allowed to issue certificates for the domain name domain.com.
+No CA is allowed to issue certificates for the domain name (domain.com).
Configure the CA to report violations to the domain name holder.
+Enable a CA to report violations to the domain name holder.
0 iodef "mailto:admin@domain.com"
If a certificate request violates the CAA record, the CA will notify the domain name holder of the violation.
+If a certificate request violates the CAA record set, the CA will notify the domain name holder of the violation.
0 iodef "http:// domain.com/log/"
@@ -47,7 +47,7 @@0 issuewild "ca.example.com"
The specified CA (ca.example.com) can issue wildcard certificates for the domain name.
+The authorized CA (ca.example.com) can issue wildcard certificates for the domain name.
Configuration example
@@ -56,15 +56,15 @@0 issuewild "ca.def.com"
0 iodef "mailto:admin@domain.com"
The example configures a CAA record for the domain name domain.com.
-- Only CA ca.abc.com can issue certificates of all types.
- Only CA ca.def.com can issue wildcard certificates.
- Any other CAs are not allowed to issue certificates.
- When a violation occurs, the CA sends a notification to admin@domain.com.
A CAA record set is configured for domain.com.
+- Only CA ca.abc.com can issue certificates of all types.
- Only CA ca.def.com can issue wildcard certificates.
- Any other CAs are not allowed to issue certificates.
- If a violation occurs, the CA sends a notification to admin@domain.com.
Checking Whether a CAA Record Has Taken Effect
Use Domain Information Groper (dig) to check whether the CAA record has taken effect. dig is a network administration command-line tool for querying the Domain Name System. If your OS does not support dig commands, install the dig tool.
+Checking Whether a CAA Record Set Has Taken Effect
Use Domain Information Groper (dig) to check whether the CAA record set has taken effect. dig is a network administration command-line tool for querying the Domain Name System. If your OS does not support dig commands, install the dig tool.
Command format: dig [Record set type] [Domain name] +trace.
Example command:
dig caa www.example.com +trace
diff --git a/docs/dns/umn/dns_faq_1100.html b/docs/dns/umn/dns_faq_1100.html index 66eebc67..bcc474ae 100644 --- a/docs/dns/umn/dns_faq_1100.html +++ b/docs/dns/umn/dns_faq_1100.html @@ -1,6 +1,6 @@ -FAQs
+FAQ
diff --git a/docs/dns/umn/dns_faq_140217.html b/docs/dns/umn/dns_faq_140217.html index 3e869f91..bc5d8da0 100644 --- a/docs/dns/umn/dns_faq_140217.html +++ b/docs/dns/umn/dns_faq_140217.html @@ -1,7 +1,7 @@-
diff --git a/docs/dns/umn/dns_faq_1402.html b/docs/dns/umn/dns_faq_1402.html
index 344f1587..53c4cf03 100644
--- a/docs/dns/umn/dns_faq_1402.html
+++ b/docs/dns/umn/dns_faq_1402.html
@@ -21,7 +21,7 @@
Can DNS Point a Domain Name to a Specific Port?
-DNS cannot point a domain name to an IP address with a specific port (Server IP address:Port number).
+No. DNS cannot point a domain name to an IP address with a specific port (Server IP address:Port number).
diff --git a/docs/dns/umn/dns_faq_1405.html b/docs/dns/umn/dns_faq_1405.html index bc6c9c00..770e3585 100644 --- a/docs/dns/umn/dns_faq_1405.html +++ b/docs/dns/umn/dns_faq_1405.html @@ -4,12 +4,12 @@diff --git a/docs/dns/umn/dns_faq_1406.html b/docs/dns/umn/dns_faq_1406.html index 0c38b63e..1d058a8f 100644 --- a/docs/dns/umn/dns_faq_1406.html +++ b/docs/dns/umn/dns_faq_1406.html @@ -4,12 +4,12 @@diff --git a/docs/dns/umn/dns_pd_0001.html b/docs/dns/umn/dns_pd_0001.html index 04b87af9..a81c24ae 100644 --- a/docs/dns/umn/dns_pd_0001.html +++ b/docs/dns/umn/dns_pd_0001.html @@ -11,7 +11,7 @@-Selecting an AZ
When deploying resources, consider your applications' requirements on disaster recovery (DR) and network latency.
- For high DR capability, deploy resources in different AZs within the same region.
- For lower network latency, deploy resources in the same AZ.
Regions and Endpoints
Before you use an API to call resources, specify its region and endpoint. For more details, see Regions and Endpoints.
+Regions and Endpoints
Before you use an API to call resources, specify its region and endpoint. For more details, see Regions and Endpoints.
diff --git a/docs/dns/umn/dns_pd_0002.html b/docs/dns/umn/dns_pd_0002.html new file mode 100644 index 00000000..a18e7468 --- /dev/null +++ b/docs/dns/umn/dns_pd_0002.html @@ -0,0 +1,149 @@ + + +Permissions
++If you need to assign different permissions to personnel in your enterprise to access your DNS resources, Identity and Access Management (IAM) is a good choice for fine-grained permissions management. IAM provides identity authentication, permissions management, and access control, helping you to securely access your cloud resources.
+With IAM, you can create IAM users and assign permissions to control their access to specific resources. For example, if you want some software developers in your enterprise to use DNS resources but do not want them to delete DNS resources or perform any other high-risk operations, you can create IAM users and grant permission to use DNS resources but not permission to delete them.
+If your account does not require individual IAM users for permissions management, you can skip this section.
+IAM is a free service. You only pay for the resources in your account.
++DNS Permissions
New IAM users do not have any permissions assigned by default. You need to first add them to one or more groups and attach policies or roles to these groups. The users then inherit permissions from the groups and can perform specified operations on cloud services based on the permissions they have been assigned.
+DNS resources include the following:
+- Public zone: global-level resource
- Private zone: project-level resource
- PTR record: project-level resource
DNS permissions for global-level resources cannot be set in the global service project and must be granted for each project.
+When you set Scope to Region-specific projects and select the specified projects in the specified regions, the users only have permissions for DNS in the selected projects. If you set Scope to All resources, the users have permissions for DNS in all region-specific projects. When accessing DNS, the users need to switch to the authorized region.
+You can grant permissions by using roles and policies.
+- Roles: A coarse-grained authorization strategy provided by IAM to assign permissions based on users' job responsibilities. Only a limited number of service-level roles are available for authorization. Cloud services depend on each other. When you grant permissions using roles, you also need to attach dependent roles. Roles are not ideal for fine-grained authorization and least privilege access.
- Policies: A fine-grained authorization strategy that defines permissions required to perform operations on specific cloud resources under certain conditions. This type of authorization is more flexible and is ideal for least privilege access. For example, you can grant users only permissions to manage DNS resources of a certain type. A majority of fine-grained policies contain permissions for specific APIs, and permissions are defined using API actions. For the API actions supported by DNS, see "Permissions and Supported Actions" in the Domain Name Service API Reference.
Table 1 lists system-defined permissions supported by DNS. + ++Table 2 lists common operations supported by system-defined permissions for DNS.
+ ++
+Table 2 Common operations supported by system-defined permissions Operation
+DNS Administrator
+Creating a public zone
+Supported
+Viewing a public zone
+Supported
+Modifying a public zone
+Supported
+Deleting a public zone
+Supported
+Creating a private zone
+Supported
+Viewing a private zone
+Supported
+Modifying a private zone
+Supported
+Deleting a private zone
+Supported
+Associating a VPC with a private zone
+Supported
+Disassociating a VPC from a private zone
+Supported
+Adding a record set
+Supported
+Viewing a record set
+Supported
+Modify a record set
+Supported
+Deleting a record set
+Supported
+Creating a PTR record
+Supported
+Viewing a PTR record
+Supported
+Modifying a PTR record
+Supported
+Deleting a PTR record
+Supported
++Helpful Links
- IAM Service Overview
- Creating a User and Granting DNS Permissions
- "Permissions Policies and Supported Actions" in the Domain Name Service API Reference
++ diff --git a/docs/dns/umn/dns_pd_0004.html b/docs/dns/umn/dns_pd_0004.html index 44e68171..af0d2a06 100644 --- a/docs/dns/umn/dns_pd_0004.html +++ b/docs/dns/umn/dns_pd_0004.html @@ -4,7 +4,7 @@++Parent topic: Overview+-
-
- Domain Name Format and Structure
+ - Domain Name Format and DNS Hierarchy
- Record Set
diff --git a/docs/dns/umn/dns_pd_0005.html b/docs/dns/umn/dns_pd_0005.html
index b559b601..784dcfb2 100644
--- a/docs/dns/umn/dns_pd_0005.html
+++ b/docs/dns/umn/dns_pd_0005.html
@@ -1,38 +1,38 @@
- - Flexibly customize private domain names in your VPCs.
- Associate one or more multiple VPCs with one domain name.
- Use private DNS servers to prevent DNS spoofing and quickly respond to requests for accessing ECSs in VPCs as well as OBS and RDS resources.
- Flexibly customize private domain names in your VPCs.
- Associate one or more multiple VPCs with one domain name.
- Use private DNS servers to prevent DNS spoofing and quickly respond to requests for accessing ECSs in VPCs as well as OBS and SMN resources.
- Managing ECS Host Names
- Keeping Your Website Up and Running Even While Your Server Is Being Replaced
- Accessing Cloud Resources
- ECSs for website A: weba01.region1.az1.com – weba10.region1.az1.com
- ECSs for website B: webb01.region1.az1.com – webb10.region1.az1.com
- ECS0: primary service node
- ECS1: public service interface
- RDS1: service database
- ECS2 and RDS2: backup service node and backup database
- ECS0: primary service node
- ECS1: public service node
- RDS1: service database
- ECS2 and RDS2: backup service node and backup database
- If a public DNS server is configured for the subnet where the ECS resides and the VPC of this subnet has been associated with a private zone, requests to access cloud services will be routed over the Internet.
Figure 3 shows the process for resolving a domain name when an ECS accesses cloud services.
-Requests are routed on the Internet, resulting in an increase in network latency.
- - If a private DNS server is configured for the subnet, it directly processes the requests to access cloud resources.
When the ECS accesses these cloud services, the private DNS server returns their private IP addresses, instead of routing requests over the Internet. This reduces network latency and improves access speed. Steps 1 to 4 on the left of Figure 3 shows the process.
+- If a public DNS server is configured for the VPC subnet where the ECS resides, requests to access cloud services will be routed over the Internet.
Figure 3 shows the process for resolving a domain name when an ECS accesses cloud services such as OBS and SMN.
+Requests are routed over the Internet, resulting in an increase in network latency.
+ - If a private DNS server is configured for the subnet, the private DNS server directly processes the requests to access cloud services.
When the ECS accesses the cloud services, the private DNS server returns their private IP addresses, instead of routing requests over the Internet. This reduces network latency and improves access speed. Steps 1 to 4 on the left of Figure 3 shows the process.
- If a public DNS server is configured for the VPC subnet where the ECS resides, requests to access cloud services will be routed over the Internet.
- A domain name is segmented using dots (.) into multiple labels.
- A domain name label can contain letters, digits, and hyphens (-) and cannot start or end with a hyphen.
- A label cannot exceed 63 characters.
- The total length of a domain name, including the dot at the end, cannot exceed 254 characters.
- Root domain: . (a dot)
- Top-level domain: for example, .com, .net, .org, and .cn
- Second-level domain: subdomains of the top-level domain names, such as example.com, example.net, and example.org
- Third-level domain: subdomains of the second-level domain names, such as abc.example.com, abc.example.net, and abc.example.org
- The next-level domain names are similarly expanded by adding prefixes to the previous-level domain names, such as def.abc.example.com, def.abc.example.net, and def.abc.example.org.
- User management refers to management of users, user groups, and user group permissions.
- Resource management refers to control operations that can be performed by users on cloud service resources.
- Public zone: global-level resources. However, you need to add permissions for users in the region, instead of in the global service.
- Private zone and PTR record: region-level resources. You need to add permissions for users in the project.
- Public zone: global-level resource. However, you need to add permissions for users in the region, instead of in the global service.
- Private zone and PTR record: region-level resources. You need to add permissions for users in the project.
- Quick Start
+ - Before You Start
- - Routing Internet Traffic to a Website
+ - Configuring a Public Zone
- Configuring a Private Zone
diff --git a/docs/dns/umn/dns_qs_0006.html b/docs/dns/umn/dns_qs_0006.html
index 3895c992..7b728b4e 100644
--- a/docs/dns/umn/dns_qs_0006.html
+++ b/docs/dns/umn/dns_qs_0006.html
@@ -1,43 +1,44 @@
- Log in to the management console.
- In the service list, choose Network > Domain Name Service.
The DNS console is displayed.
- - In the navigation pane, choose Private Zones.
The Private Zones page is displayed.
- - Click in the upper left corner and select the desired region and project.
- Click Create Private Zone.
- Set Name to example.com and select the VPC where the ECS resides.
For details about more parameters, see Creating a Private Zone.
-Figure 2 Creating a private zone-
- Click OK.
- Switch back to the Private Zones page.View the created private zone. - - \ No newline at end of file diff --git a/docs/dns/umn/dns_usermanual_0002.html b/docs/dns/umn/dns_usermanual_0002.html index 5019d5d2..ba568087 100644 --- a/docs/dns/umn/dns_usermanual_0002.html +++ b/docs/dns/umn/dns_usermanual_0002.html @@ -1,6 +1,6 @@ -
Click the zone name to view zone details. You can view SOA and NS record sets automatically generated by the system.
-- The SOA record set defines the DNS server that is the authoritative information source for a particular domain name.
- The NS record set defines authoritative DNS servers for a zone.
Creating a Private Zone
- Create a private zone.Create a private zone to allow access to your ECS using a private domain name example.com.-
- Log in to the management console.
- In the service list, choose Network > Domain Name Service.
The DNS console is displayed.
+ - In the navigation pane on the left, choose Private Zones.
The Private Zones page is displayed.
+ - Click in the upper left corner and select the desired region and project.
- Click Create Private Zone.
- Set Domain Name to example.com and select the VPC where the ECS resides.
Set other parameters by referring to Creating a Private Zone.
+Figure 2 Creating a private zone+
- Click OK.
- Switch back to the Private Zones page.You can view the created private zone in the private zone list.
Click the domain name to view SOA and NS record sets automatically generated for the zone.
+
-Add an A Record Set
To access the ECS using example.com, add an A record set.
-- On the Private Zones page, click the name of the private zone you created.
The Record Sets page is displayed.
- - Click Add Record Set.
- Set the parameters as follows:
- Name: Leave this parameter blank. The system automatically considers example.com to be the name, and requests are routed to example.com.
- Type: Set it to A – Map domains to IPv4 addresses.
- Value: Enter the private IP address of the ECS.
Retain the default values for other parameters. For details, see Adding an A Record Set.
-Figure 3 Add Record Set-
- Click OK.
- Switch back to the Record Sets page.
View the added record set in the record set list of the zone and ensure that the status of the record set is Normal.
+ - Add an A record set to the domain name.
To access the ECS using example.com, add an A record set.
+- On the Private Zones page, click the domain name of the private zone you created.
The Record Sets page is displayed.
+ - Click Add Record Set.
- Configure the parameters as follows:
- Name: Leave this parameter blank. The DNS service automatically considers example.com as the name, and requests are routed to example.com.
- Type: Retain the default setting A – Map domains to IPv4 addresses.
- Value: Enter the private IP address of the ECS.
Configure other parameters by referring to Adding an A Record Set.
+Figure 3 Add Record Set+
- Click OK.
- Switch back to the Record Sets tab.
The added record set is in the Normal state.
- On the Private Zones page, click the domain name of the private zone you created.
(Optional) Configure DNS Servers for the VPC Subnet
To ensure that private domain names can be resolved in a VPC, change the DNS servers for the VPC subnet to those provided by the DNS service.
-Query the private DNS servers provided by the DNS service
-- Log in to the management console.
- In the service list, choose Network > Domain Name Service.
The DNS console is displayed.
- - In the navigation pane, choose Private Zones.
The Private Zones page is displayed.
- - Click in the upper left corner and select the desired region and project.
- In the private zone list, click the name of the zone and view the DNS servers.
Change the DNS servers
-- Go to the private zone list.
- Click the VPC name under Associated VPC.
On the VPC console, change the DNS servers of the VPC subnet.
+ - Change the DNS server addresses of the VPC subnet.
To ensure that the private domain name can be resolved in the associated VPC, verify that the DNS server addresses for the VPC subnet are those provided by the DNS service. If the DNS server addresses are not those provided by the DNS service, change them.
+Query the private DNS server addresses provided by the DNS service.
+- Log in to the management console.
- In the service list, choose Network > Domain Name Service.
The DNS console is displayed.
+ - In the navigation pane on the left, choose Private Zones.
The Private Zones page is displayed.
+ - Click in the upper left corner and select the desired region and project.
- In the private zone list, click the domain name of the zone and view the DNS server addresses.
Change the DNS server addresses.
+- Go to the private zone list.
- Click the VPC name under Associated VPC.
On the VPC console, change the DNS server addresses for the VPC subnet.
For details, see Modifying a Subnet.
@@ -46,10 +47,3 @@Private Zone
+Private Zones
-
diff --git a/docs/dns/umn/dns_usermanual_0003.html b/docs/dns/umn/dns_usermanual_0003.html
index 8346a4ff..c9fbd104 100644
--- a/docs/dns/umn/dns_usermanual_0003.html
+++ b/docs/dns/umn/dns_usermanual_0003.html
@@ -1,28 +1,21 @@
- Log in to the management console.
- In the service list, choose Network > Domain Name Service.
The DNS console is displayed.
- - In the navigation pane, choose Private Zones.
The Private Zones page is displayed.
- - Click in the upper left corner and select the desired region and project.
- Locate the private zone with which you want to associate the VPC and click Associate VPC under Operation.
- Select the VPC you want to associate.If no VPCs are available, create one on the VPC console and then associate the private zone with it.Figure 1 Associating a VPC+
Procedure
- Log in to the management console.
- In the service list, choose Network > Domain Name Service.
The DNS console is displayed.
+ - In the navigation pane on the left, choose Private Zones.
The Private Zones page is displayed.
+ - Click in the upper left corner and select the desired region and project.
- Locate the private zone with which you want to associate the VPC and click Associate VPC under Operation.
- Select the VPC you want to associate. -
- Click OK.
The VPC is displayed under Associated VPC.
+ - Click OK.
The VPC is displayed under Associated VPC.
- - \ No newline at end of file diff --git a/docs/dns/umn/dns_usermanual_0004.html b/docs/dns/umn/dns_usermanual_0004.html index 630d6245..fe2bc80a 100644 --- a/docs/dns/umn/dns_usermanual_0004.html +++ b/docs/dns/umn/dns_usermanual_0004.html @@ -1,27 +1,20 @@-Parent topic: Private Zone+Parent topic: Private ZonesDisassociating a VPC from a Private Zone
-Scenarios
Disassociate a VPC from a private zone if you do not want to the private domain name to work in this VPC. If a private zone has only one VPC associated, you cannot disassociate the VPC.
- If you do not intend to use private domain names, delete the private zone.
+-Scenarios
Disassociate a VPC from a private zone if you do not want the private domain name to be resolved in this VPC. If a private zone has only one VPC associated, you cannot disassociate the VPC.
+ If you do not intend to use private domain names, delete the private zone configured for it.
Procedure
- Log in to the management console.
- In the service list, choose Network > Domain Name Service.
The DNS console is displayed.
- - In the navigation pane, choose Private Zones.
The Private Zones page is displayed.
- - Click in the upper left corner and select the desired region and project.
- Locate the private zone from which a VPC is to be disassociated, select the VPC to be disassociated under Associated VPC, and click
on the right of the VPC.Figure 1 Associated VPC-
- In the Disassociate VPC dialog box, click Yes.Figure 2 Disassociating a VPC+
Procedure
- Log in to the management console.
- In the service list, choose Network > Domain Name Service.
The DNS console is displayed.
+ - In the navigation pane on the left, choose Private Zones.
The Private Zones page is displayed.
+ - Click in the upper left corner and select the desired region and project.
- Locate the private zone from which a VPC is to be disassociated, select the VPC to be disassociated under Associated VPC, and click
on the right of the VPC.Figure 1 Associated VPCs+
- In the Disassociate VPC dialog box, click Yes.Figure 2 Disassociating a VPC
- - \ No newline at end of file diff --git a/docs/dns/umn/dns_usermanual_0006.html b/docs/dns/umn/dns_usermanual_0006.html index a88668e6..914617ac 100644 --- a/docs/dns/umn/dns_usermanual_0006.html +++ b/docs/dns/umn/dns_usermanual_0006.html @@ -4,28 +4,30 @@-Parent topic: Private Zone+Parent topic: Private Zonesdiff --git a/docs/dns/umn/dns_usermanual_0007.html b/docs/dns/umn/dns_usermanual_0007.html index 9bb27cc3..d3338cd6 100644 --- a/docs/dns/umn/dns_usermanual_0007.html +++ b/docs/dns/umn/dns_usermanual_0007.html @@ -1,110 +1,109 @@-
+
- Record Set Types and Configuration Rules
+ - Adding an A Record Set
- - Adding an AAAA Record Set
-
- - Adding an NS Record Set
- - Adding a CNAME Record Set
- Adding an MX Record Set
+ - Adding an AAAA Record Set
+ - Adding a TXT Record Set
- Adding an SRV Record Set
+ - Adding an NS Record Set
+ - Adding a CAA Record Set
- - Adding a PTR Record
+ - Adding a PTR Record Set
-Parent topic: Record Set+Parent topic: Record SetsAdding an A Record Set
-Scenarios
If you want to use a domain name to access websites, web applications, or cloud servers configured with IPv4 addresses, you can add an A record set for the domain name.
+-Scenarios
If you want end users to access your website, web application, or cloud server configured with an IPv4 address via its domain name, add an A record set for this domain name.
For more information about the types of record sets, see Record Set Types and Configuration Rules.
Prerequisites
You have a web server and obtained an IPv4 address.
+-Prerequisites
You have a website, web application, or cloud server and obtained an IPv4 address.
Procedure
- Log in to the management console.
- In the service list, choose Network > Domain Name Service.
The DNS console is displayed.
-
- In the navigation pane, choose Public Zones or Private Zones.
The zone list is displayed.
- - (Optional) If you have selected Private Zones, click on the upper left corner to select the region and project.
- Click the zone name.
- Click Add Record Set.
The Add Record Set dialog box is displayed.
- - Set required parameters based on Table 1.
-
Table 1 Parameters for adding an A record set Parameter
+Procedure
- Log in to the management console.
- In the service list, choose Network > Domain Name Service.
The DNS console is displayed.
+ - In the navigation pane, choose Public Zones or Private Zones.
The zone list is displayed.
+ - (Optional) If you have selected Private Zones, click
on the upper left corner to select the region and project. - Click the domain name.
- Click Add Record Set.
The Add Record Set dialog box is displayed.
+ - Configure the parameters based on Table 1.
+-
Table 1 Parameters for adding an A record set Parameter
Description
+Description
Example Value
+Example Value
Name
+Name
Prefix of the domain name to be resolved
-For example, if the zone name is example.com, the domain name prefix can be as follows:
-- www: The domain name is www.example.com, which is usually used for a website.
- Left blank: The domain name is example.com.
In some cases, you may need to set the record set name to the at sign (@). However, the at sign is not supported. Leave the Name blank.
- - abc: The domain name is abc.example.com, a subdomain of example.com.
- mail: The domain name is mail.example.com, which is typically used for an email server.
- *: The domain name is *.example.com, which is a wildcard domain name, indicating all subdomains of example.com.
Prefix of the domain name to be resolved.
+For example, if the domain name is example.com, the prefix can be as follows:
+- www: The domain name is www.example.com, which is usually used for a website.
- Left blank: The domain name is example.com.
The Name field cannot be set to an at sign (@). Just leave it blank.
+ - abc: The domain name is abc.example.com, a subdomain of example.com.
- mail: The domain name is mail.example.com, which is typically used for email servers.
- *: The domain name is *.example.com, which is a wildcard domain name, indicating all subdomains of example.com.
www
+www
Type
+Type
Type of the record set
-If a message is displayed indicating that the record set you are trying to create exists, the record set conflicts with an existing record set.
+Type of the record set.
+A message may be displayed indicating that the record set you are trying to add conflicts with an existing record set.
A – Map domains to IPv4 addresses
+A – Map domains to IPv4 addresses
TTL (s)
+TTL (s)
Cache duration of the record set on a local DNS server, in seconds
+Cache duration of the record set on a local DNS server, in seconds.
The value ranges from 1 to 2147483647, and the default is 300.
If your service address changes frequently, set TTL to a smaller value.
The default value is 300, which is, 5 minutes.
+300
Value
+Value
IPv4 addresses mapped to the domain name
+IPv4 addresses mapped to the domain name.
You can enter a maximum of 50 record values, each on a separate line.
192.168.12.2
+192.168.12.2
192.168.12.3
Tags
+Tag
(Optional) Identifier of a resource
-Each tag contains a key and a value. You can add a maximum of 20 tags to a record set. This parameter is displayed when you enable Other Settings.
+(Optional) Identifier of a record set. Each tag contains a key and a value. You can add a maximum of 20 tags to a record set.
For details about tag key and value requirements, see Table 2.
example_key1
+example_key1
example_value1
Description
+Description
(Optional) Supplementary information about the record set
+(Optional) Supplementary information about the record set.
You can enter a maximum of 255 characters.
N/A
+N/A
Table 2 Tag key and value requirements Parameter
+-Table 2 Tag key and value requirements Parameter
Requirements
+Requirements
Example Value
+Example Value
Key
+Key
- Cannot be left blank.
- Must be unique for each resource.
- Can contain a maximum of 36 characters.
- Cannot be left blank.
- Must be unique for each resource.
- Can contain a maximum of 36 characters.
- Can contain only letters, digits, hyphens (-), at signs (@), and underscores (_).
example_key1
+example_key1
Value
+Value
- Cannot be left blank.
- Can contain a maximum of 43 characters.
- Cannot be left blank.
- Can contain a maximum of 43 characters.
- Can contain only letters, digits, hyphens (-), at signs (@), and underscores (_).
example_value1
+example_value1
- Click OK.
- Switch back to the Record Sets page.
View the added record set in the record set list of the zone and ensure that the status of the record set is Normal.
+- Click OK.
- Switch back to the Record Sets tab.
-The added record set is in the Normal state.
Related Operations
For more information about how to configure A record sets, see Routing Internet Traffic to a Website.
+Related Operations
For details about how to configure A record sets, see Configuring a Public Zone.
diff --git a/docs/dns/umn/dns_usermanual_0008.html b/docs/dns/umn/dns_usermanual_0008.html index 19d43fe1..ab2ebb75 100644 --- a/docs/dns/umn/dns_usermanual_0008.html +++ b/docs/dns/umn/dns_usermanual_0008.html @@ -1,106 +1,105 @@Adding an AAAA Record Set
-Scenarios
If you want to use a domain name to access websites, web applications, or cloud servers configured with IPv6 addresses, you can add an AAAA record set for the domain name.
+Scenarios
If you want end users to access your website, web application, or cloud server configured with an IPv6 address via its domain name, add an AAAA record set for this domain name.
For more details, see Record Set Types and Configuration Rules.
-Prerequisites
You have a web server and obtained an IPv6 address.
Procedure
- Log in to the management console.
- In the service list, choose Network > Domain Name Service.
The DNS console is displayed.
-
- In the navigation pane, choose Public Zones or Private Zones.
The zone list is displayed.
- - (Optional) If you have selected Private Zones, click on the upper left corner to select the region and project.
- Click the zone name.
- Click Add Record Set.
The Add Record Set dialog box is displayed.
- - Set required parameters based on Table 1.
-
Table 1 Parameters for adding an AAAA record set Parameter
+Procedure
- Log in to the management console.
- In the service list, choose Network > Domain Name Service.
The DNS console is displayed.
+ - In the navigation pane, choose Public Zones or Private Zones.
The zone list is displayed.
+ - (Optional) If you have selected Private Zones, click on the upper left corner to select the region and project.
- Click the domain name.
- Click Add Record Set.
The Add Record Set dialog box is displayed.
+ - Configure the parameters based on Table 1.
+-
Table 1 Parameters for adding an AAAA record set Parameter
Description
+Description
Example Value
+Example Value
Name
+Name
Prefix of the domain name to be resolved
-For example, if the zone name is example.com, the domain name prefix can be as follows:
-- www: The domain name is www.example.com, which is usually used for a website.
- Left blank: The domain name is example.com.
In some cases, you may need to set the record set name to the at sign (@). However, the at sign is not supported. Leave the Name blank.
- - abc: The domain name is abc.example.com, a subdomain of example.com.
- mail: The domain name is mail.example.com, which is typically used for an email server.
- *: The domain name is *.example.com, which is a wildcard domain name, indicating all subdomains of example.com.
Prefix of the domain name to be resolved.
+For example, if the domain name is example.com, the prefix can be as follows:
+- www: The domain name is www.example.com, which is usually used for a website.
- Left blank: The domain name is example.com.
The Name field cannot be set to an at sign (@). Just leave it blank.
+ - abc: The domain name is abc.example.com, a subdomain of example.com.
- mail: The domain name is mail.example.com, which is typically used for email servers.
- *: The domain name is *.example.com, which is a wildcard domain name, indicating all subdomains of example.com.
www
+www
Type
+Type
Type of the record set
-If a message is displayed indicating that the record set you are trying to create exists, the record set conflicts with an existing record set.
+Type of the record set.
+A message may be displayed indicating that the record set you are trying to add conflicts with an existing record set.
AAAA – Map domains to IPv6 addresses
+AAAA – Map domains to IPv6 addresses
TTL (s)
+TTL (s)
Cache duration of the record set on a local DNS server, in seconds
+Cache duration of the record set on a local DNS server, in seconds.
The value ranges from 1 to 2147483647, and the default is 300.
If your service address changes frequently, set TTL to a smaller value.
The default value is 300, which is, 5 minutes.
+300
Value
+Value
IPv6 addresses mapped to the domain name
+IPv6 addresses mapped to the domain name
You can enter a maximum of 50 record values, each on a separate line.
ff03:0db8:85a3:0:0:8a2e:0370:7334
+ff03:0db8:85a3:0:0:8a2e:0370:7334
Tags
+Tag
(Optional) Identifier of a resource
-Each tag contains a key and a value. You can add a maximum of 20 tags to a record set. This parameter is displayed when you enable Other Settings.
+(Optional) Identifier of a record set. Each tag contains a key and a value. You can add a maximum of 20 tags to a record set.
For details about tag key and value requirements, see Table 2.
example_key1
+example_key1
example_value1
Description
+Description
(Optional) Supplementary information about the record set
+(Optional) Supplementary information about the record set.
You can enter a maximum of 255 characters.
-
+-
Table 2 Tag key and value requirements Parameter
+-Table 2 Tag key and value requirements Parameter
Requirements
+Requirements
Example Value
+Example Value
Key
+Key
- Cannot be left blank.
- Must be unique for each resource.
- Can contain a maximum of 36 characters.
- Cannot be left blank.
- Must be unique for each resource.
- Can contain a maximum of 36 characters.
- Can contain only letters, digits, hyphens (-), at signs (@), and underscores (_).
example_key1
+example_key1
Value
+Value
- Cannot be left blank.
- Can contain a maximum of 43 characters.
- Cannot be left blank.
- Can contain a maximum of 43 characters.
- Can contain only letters, digits, hyphens (-), at signs (@), and underscores (_).
example_value1
+example_value1
- Click OK.
- Switch back to the Record Sets page.
View the added record set in the record set list of the zone and ensure that the status of the record set is Normal.
+- Click OK.
- Switch back to the Record Sets tab.
diff --git a/docs/dns/umn/dns_usermanual_0009.html b/docs/dns/umn/dns_usermanual_0009.html index 8e92bea8..990c9fc1 100644 --- a/docs/dns/umn/dns_usermanual_0009.html +++ b/docs/dns/umn/dns_usermanual_0009.html @@ -4,105 +4,104 @@The added record set is in the Normal state.
-Scenarios
If you want to specify authoritative DNS servers for a domain name, you can add NS record sets.
For more details, see Record Set Types and Configuration Rules.
Constraints
- You can create NS record sets only in public zones.
- After a public zone is created, the system automatically adds an NS record set for the domain name. This NS record set cannot be modified or deleted. Therefore, you can add NS record sets only in the following scenarios:
- The Name parameter is not left blank. This means that you can add NS record sets for subdomains of a domain name.
- The value of the Line parameter is not set to Default. This means that you can add NS record sets for the domain name with other resolution lines.
-Constraints
- You can create NS record sets only in public zones.
- After a public zone is created, an NS record set is automatically created for this zone and cannot be deleted. You can add NS record sets only in the following scenarios:
- The Name parameter is not left blank. This means that you can add NS record sets for subdomains of a domain name.
- The value of the Line parameter is not set to Default. This means that you can add NS record sets for the domain name with other resolution lines.
Procedure
- Log in to the management console.
- In the service list, choose Network > Domain Name Service.
The DNS console is displayed.
-
- In the navigation pane, choose Public Zones.
The Public Zones page is displayed.
- - Click the zone name.
- Click Add Record Set.
The Add Record Set dialog box is displayed.
-
- Set required parameters based on Table 1.
-
Table 1 Parameters for adding an NS record set Parameter
+Procedure
- Log in to the management console.
- In the service list, choose Network > Domain Name Service.
The DNS console is displayed.
+ - In the navigation pane on the left, choose Public Zones.
The Public Zones page is displayed.
+ - Click the domain name.
- Click Add Record Set.
The Add Record Set dialog box is displayed.
+
- Configure the parameters based on Table 1.
+-
Table 1 Parameters for adding an NS record set Parameter
Description
+Description
Example Value
+Example Value
Name
+Name
Prefix of the domain name to be resolved
-For example, if the zone name is example.com, the domain name prefix can be as follows:
-- www: The domain name is www.example.com, which is usually used for a website.
- Left blank: The domain name is example.com.
In some cases, you may need to set the record set name to the at sign (@). However, the at sign is not supported. Leave the Name blank.
- - abc: The domain name is abc.example.com, a subdomain of example.com.
- mail: The domain name is mail.example.com, which is typically used for an email server.
- *: The domain name is *.example.com, which is a wildcard domain name, indicating all subdomains of example.com.
Prefix of the domain name to be resolved.
+For example, if the domain name is example.com, the prefix can be as follows:
+- www: The domain name is www.example.com, which is usually used for a website.
- Left blank: The domain name is example.com.
The Name field cannot be set to an at sign (@). Just leave it blank.
+ - abc: The domain name is abc.example.com, a subdomain of example.com.
- mail: The domain name is mail.example.com, which is typically used for email servers.
- *: The domain name is *.example.com, which is a wildcard domain name, indicating all subdomains of example.com.
abc
+abc
Type
+Type
Type of the record set
-If a message is displayed indicating that the record set you are trying to create exists, the record set conflicts with an existing record set.
+Type of the record set
+A message may be displayed indicating that the record set you are trying to add conflicts with an existing record set.
NS – Delegate subdomains to other name servers
+NS – Delegate subdomains to other name servers
TTL (s)
+TTL (s)
Cache duration of the record set on a local DNS server, in seconds
+Cache duration of the record set on a local DNS server, in seconds.
The value ranges from 1 to 2147483647, and the default is 300.
If your service address changes frequently, set TTL to a smaller value.
The default value is 300, which is, 5 minutes.
+300
Value
+Value
DNS server address
+DNS server address
You can enter a maximum of 50 record values, each on a separate line.
ns1.example.net
+ns1.example.net
ns2.example.net
Tags
+Tag
(Optional) Identifier of a resource
-Each tag contains a key and a value. You can add a maximum of 20 tags to a record set. This parameter is displayed when you enable Other Settings.
+(Optional) Identifier of a record set. Each tag contains a key and a value. You can add a maximum of 20 tags to a record set.
For details about tag key and value requirements, see Table 2.
example_key1
+example_key1
example_value1
Description
+Description
(Optional) Supplementary information about the record set
+(Optional) Supplementary information about the record set.
You can enter a maximum of 255 characters.
-
+-
Table 2 Tag key and value requirements Parameter
+-Table 2 Tag key and value requirements Parameter
Requirements
+Requirements
Example Value
+Example Value
Key
+Key
- Cannot be left blank.
- Must be unique for each resource.
- Can contain a maximum of 36 characters.
- Cannot be left blank.
- Must be unique for each resource.
- Can contain a maximum of 36 characters.
- Can contain only letters, digits, hyphens (-), at signs (@), and underscores (_).
example_key1
+example_key1
Value
+Value
- Cannot be left blank.
- Can contain a maximum of 43 characters.
- Cannot be left blank.
- Can contain a maximum of 43 characters.
- Can contain only letters, digits, hyphens (-), at signs (@), and underscores (_).
example_value1
+example_value1
- Switch back to the Record Sets page.
View the added record set in the record set list of the zone and ensure that the status of the record set is Normal.
+- Switch back to the Record Sets tab.
diff --git a/docs/dns/umn/dns_usermanual_0010.html b/docs/dns/umn/dns_usermanual_0010.html index 4f0b101d..30e88b43 100644 --- a/docs/dns/umn/dns_usermanual_0010.html +++ b/docs/dns/umn/dns_usermanual_0010.html @@ -6,100 +6,99 @@The added record set is in the Normal state.
-Constraints
- You can leave the Name parameter blank when adding a CNAME record set.
- You cannot create a CNAME record set with the same name and resolution line as an NS record set.
Procedure
- Log in to the management console.
- In the service list, choose Network > Domain Name Service.
The DNS console is displayed.
-
- In the navigation pane, choose Public Zones or Private Zones.
The zone list is displayed.
- - (Optional) If you have selected Private Zones, click on the upper left corner to select the region and project.
- Click the zone name.
- Click Add Record Set.
The Add Record Set dialog box is displayed.
-
- Set required parameters based on Table 1.
-
Table 1 Parameters for adding a CNAME record set Parameter
+Procedure
- Log in to the management console.
- In the service list, choose Network > Domain Name Service.
The DNS console is displayed.
+ - In the navigation pane, choose Public Zones or Private Zones.
The zone list is displayed.
+ - (Optional) If you have selected Private Zones, click on the upper left corner to select the region and project.
- Click the domain name.
- Click Add Record Set.
The Add Record Set dialog box is displayed.
+ - Configure the parameters based on Table 1.
+-
Table 1 Parameters for adding a CNAME record set Parameter
Description
+Description
Example Value
+Example Value
Name
+Name
Prefix of the domain name to be resolved
-For example, if the zone name is example.com, the domain name prefix can be as follows:
-- www: The domain name is www.example.com, which is usually used for a website.
- Left blank: The domain name is example.com.
In some cases, you may need to set the record set name to the at sign (@). However, the at sign is not supported. Leave the Name blank.
- - abc: The domain name is abc.example.com, a subdomain of example.com.
- mail: The domain name is mail.example.com, which is typically used for an email server.
- *: The domain name is *.example.com, which is a wildcard domain name, indicating all subdomains of example.com.
Prefix of the domain name to be resolved.
+For example, if the domain name is example.com, the prefix can be as follows:
+- www: The domain name is www.example.com, which is usually used for a website.
- Left blank: The domain name is example.com.
The Name field cannot be set to an at sign (@). Just leave it blank.
+ - abc: The domain name is abc.example.com, a subdomain of example.com.
- mail: The domain name is mail.example.com, which is typically used for email servers.
- *: The domain name is *.example.com, which is a wildcard domain name, indicating all subdomains of example.com.
Left blank
+Left blank
Type
+Type
Type of the record set
-If a message is displayed indicating that the record set you are trying to create exists, the record set conflicts with an existing record set.
+Type of the record set
+A message may be displayed indicating that the record set you are trying to add conflicts with an existing record set.
CNAME – Map one domain to another
+CNAME – Map one domain to another
TTL (s)
+TTL (s)
Cache duration of the record set on a local DNS server, in seconds
+Cache duration of the record set on a local DNS server, in seconds.
The value ranges from 1 to 2147483647, and the default is 300.
If your service address changes frequently, set TTL to a smaller value.
The default value is 300, which is, 5 minutes.
+300
Value
+Value
Domain name alias. You can enter only one domain name.
+Domain name alias. You can enter only one domain name.
webserver01.example.com
+webserver01.example.com
Tags
+Tag
(Optional) Identifier of a resource
-Each tag contains a key and a value. You can add a maximum of 20 tags to a record set. This parameter is displayed when you enable Other Settings.
+(Optional) Identifier of a record set. Each tag contains a key and a value. You can add a maximum of 20 tags to a record set.
For details about tag key and value requirements, see Table 2.
example_key1
+example_key1
example_value1
Description
+Description
(Optional) Supplementary information about the record set
+(Optional) Supplementary information about the record set.
You can enter a maximum of 255 characters.
-
+-
Table 2 Tag key and value requirements Parameter
+-Table 2 Tag key and value requirements Parameter
Requirements
+Requirements
Example Value
+Example Value
Key
+Key
- Cannot be left blank.
- Must be unique for each resource.
- Can contain a maximum of 36 characters.
- Cannot be left blank.
- Must be unique for each resource.
- Can contain a maximum of 36 characters.
- Can contain only letters, digits, hyphens (-), at signs (@), and underscores (_).
example_key1
+example_key1
Value
+Value
- Cannot be left blank.
- Can contain a maximum of 43 characters.
- Cannot be left blank.
- Can contain a maximum of 43 characters.
- Can contain only letters, digits, hyphens (-), at signs (@), and underscores (_).
example_value1
+example_value1
- Click OK.
- Switch back to the Record Sets page.
View the added record set in the record set list of the zone and ensure that the status of the record set is Normal.
+- Click OK.
- Switch back to the Record Sets tab.
diff --git a/docs/dns/umn/dns_usermanual_0011.html b/docs/dns/umn/dns_usermanual_0011.html index d7641f6e..06c8bc2e 100644 --- a/docs/dns/umn/dns_usermanual_0011.html +++ b/docs/dns/umn/dns_usermanual_0011.html @@ -1,109 +1,108 @@The added record set is in the Normal state.
Adding an MX Record Set
-Scenarios
If you want to specify email servers mapped a domain name, you can add MX record sets.
+Scenarios
If you want to map email servers to a domain name, you can add MX record sets.
For details about other types of record sets, see Record Set Types and Configuration Rules.
-Prerequisites
You have deployed an email server and obtained its domain name.
Procedure
- Log in to the management console.
- In the service list, choose Network > Domain Name Service.
The DNS console is displayed.
-
- In the navigation pane, choose Public Zones or Private Zones.
The zone list is displayed.
- - (Optional) If you have selected Private Zones, click on the upper left corner to select the region and project.
- Click the zone name.
- Click Add Record Set.
The Add Record Set dialog box is displayed.
-
- Set required parameters based on Table 1.
-
Table 1 Parameters for adding an MX record set Parameter
+Procedure
- Log in to the management console.
- In the service list, choose Network > Domain Name Service.
The DNS console is displayed.
+ - In the navigation pane, choose Public Zones or Private Zones.
The zone list is displayed.
+ - (Optional) If you have selected Private Zones, click on the upper left corner to select the region and project.
- Click the domain name.
- Click Add Record Set.
The Add Record Set dialog box is displayed.
+ - Configure the parameters based on Table 1.
+-
Table 1 Parameters for adding an MX record set Parameter
Description
+Description
Example Value
+Example Value
Name
+Name
Prefix of the domain name to be resolved
-For example, if the zone name is example.com, the domain name prefix can be as follows:
-- www: The domain name is www.example.com, which is usually used for a website.
- Left blank: The domain name is example.com.
In some cases, you may need to set the record set name to the at sign (@). However, the at sign is not supported. Leave the Name blank.
- - abc: The domain name is abc.example.com, a subdomain of example.com.
- mail: The domain name is mail.example.com, which is typically used for an email server.
- *: The domain name is *.example.com, which is a wildcard domain name, indicating all subdomains of example.com.
Prefix of the domain name to be resolved.
+For example, if the domain name is example.com, the prefix can be as follows:
+- www: The domain name is www.example.com, which is usually used for a website.
- Left blank: The domain name is example.com.
The Name field cannot be set to an at sign (@). Just leave it blank.
+ - abc: The domain name is abc.example.com, a subdomain of example.com.
- mail: The domain name is mail.example.com, which is typically used for email servers.
- *: The domain name is *.example.com, which is a wildcard domain name, indicating all subdomains of example.com.
Left blank
+Left blank
Type
+Type
Type of the record set
-If a message is displayed indicating that the record set you are trying to create exists, the record set conflicts with an existing record set.
+Type of the record set
+A message may be displayed indicating that the record set you are trying to add conflicts with an existing record set.
MX – Map domains to email servers
+MX – Map domains to email servers
TTL (s)
+TTL (s)
Cache duration of the record set on a local DNS server, in seconds
+Cache duration of the record set on a local DNS server, in seconds.
The value ranges from 1 to 2147483647, and the default is 300.
If your service address changes frequently, set TTL to a smaller value.
The default value is 300, which is, 5 minutes.
+300
Value
+Value
Email server address
+Email server address
You can enter a maximum of 50 record values, each on a separate line.
The format is [priority][mail server host name].
Configuration rules:- priority: priority for an email server to receive emails. A smaller value indicates a higher priority.
- mail server host name: domain name provided by the email service provider
10 mailserver.example.com
+10 mailserver.example.com.
Tags
+Tag
(Optional) Identifier of a resource
-Each tag contains a key and a value. You can add a maximum of 20 tags to a record set. This parameter is displayed when you enable Other Settings.
+(Optional) Identifier of a record set. Each tag contains a key and a value. You can add a maximum of 20 tags to a record set.
For details about tag key and value requirements, see Table 2.
example_key1
+example_key1
example_value1
Description
+Description
(Optional) Supplementary information about the record set
+(Optional) Supplementary information about the record set.
You can enter a maximum of 255 characters.
The description of the hostname.
+-
Table 2 Tag key and value requirements Parameter
+-Table 2 Tag key and value requirements Parameter
Requirements
+Requirements
Example Value
+Example Value
Key
+Key
- Cannot be left blank.
- Must be unique for each resource.
- Can contain a maximum of 36 characters.
- Cannot be left blank.
- Must be unique for each resource.
- Can contain a maximum of 36 characters.
- Can contain only letters, digits, hyphens (-), at signs (@), and underscores (_).
example_key1
+example_key1
Value
+Value
- Cannot be left blank.
- Can contain a maximum of 43 characters.
- Cannot be left blank.
- Can contain a maximum of 43 characters.
- Can contain only letters, digits, hyphens (-), at signs (@), and underscores (_).
example_value1
+example_value1
- Click OK.
- Switch back to the Record Sets page.
View the added record set in the record set list of the zone and ensure that the status of the record set is Normal.
+- Click OK.
- Switch back to the Record Sets tab.
diff --git a/docs/dns/umn/dns_usermanual_0012.html b/docs/dns/umn/dns_usermanual_0012.html index 10b3106a..43044523 100644 --- a/docs/dns/umn/dns_usermanual_0012.html +++ b/docs/dns/umn/dns_usermanual_0012.html @@ -4,109 +4,108 @@The added record set is in the Normal state.
-Scenarios
A TXT record set provides description for a domain name.
For details about other record set types, see Record Set Types and Configuration Rules.
Procedure
- Log in to the management console.
- In the service list, choose Network > Domain Name Service.
The DNS console is displayed.
-
- In the navigation pane, choose Public Zones or Private Zones.
The zone list is displayed.
- - (Optional) If you have selected Private Zones, click on the upper left corner to select the region and project.
- Click the zone name.
- Click Add Record Set.
The Add Record Set dialog box is displayed.
-
- Set required parameters based on Table 1.
-
Table 1 Parameters for adding a TXT record set Parameter
+Procedure
- Log in to the management console.
- In the service list, choose Network > Domain Name Service.
The DNS console is displayed.
+ - In the navigation pane, choose Public Zones or Private Zones.
The zone list is displayed.
+ - (Optional) If you have selected Private Zones, click on the upper left corner to select the region and project.
- Click the domain name.
- Click Add Record Set.
The Add Record Set dialog box is displayed.
+ - Configure the parameters based on Table 1.
+-
Table 1 Parameters for adding a TXT record set Parameter
Description
+Description
Example Value
+Example Value
Name
+Name
Prefix of the domain name to be resolved
-For example, if the zone name is example.com, the domain name prefix can be as follows:
-- www: The domain name is www.example.com, which is usually used for a website.
- Left blank: The domain name is example.com.
In some cases, you may need to set the record set name to the at sign (@). However, the at sign is not supported. Leave the Name blank.
- - abc: The domain name is abc.example.com, a subdomain of example.com.
- mail: The domain name is mail.example.com, which is typically used for an email server.
- *: The domain name is *.example.com, which is a wildcard domain name, indicating all subdomains of example.com.
Prefix of the domain name to be resolved.
+For example, if the domain name is example.com, the prefix can be as follows:
+- www: The domain name is www.example.com, which is usually used for a website.
- Left blank: The domain name is example.com.
The Name field cannot be set to an at sign (@). Just leave it blank.
+ - abc: The domain name is abc.example.com, a subdomain of example.com.
- mail: The domain name is mail.example.com, which is typically used for email servers.
- *: The domain name is *.example.com, which is a wildcard domain name, indicating all subdomains of example.com.
Left blank
+Left blank
Type
+Type
Type of the record set
-If a message is displayed indicating that the record set you are trying to create exists, the record set conflicts with an existing record set.
+Type of the record set
+A message may be displayed indicating that the record set you are trying to add conflicts with an existing record set.
TXT – Specify text records
+TXT – Specify text records
TTL (s)
+TTL (s)
Cache duration of the record set on a local DNS server, in seconds
+Cache duration of the record set on a local DNS server, in seconds.
The value ranges from 1 to 2147483647, and the default is 300.
If your service address changes frequently, set TTL to a smaller value.
The default value is 300, which is, 5 minutes.
+300
Value
+Value
Text content
+Text content
Configuration rules:
- Text record values must be enclosed in double quotation marks.
- One or more text record values are supported, each on a separate line.
- A single text record value can contain multiple character strings, each of which is double quoted and separated from others using a space.
One character string cannot exceed 255 characters.
A value must not exceed 4096 characters.
- The value cannot be left blank.
- The text cannot contain a backslash (\).
Tags
+Tag
(Optional) Identifier of a resource
-Each tag contains a key and a value. You can add a maximum of 20 tags to a record set. This parameter is displayed when you enable Other Settings.
+(Optional) Identifier of a record set. Each tag contains a key and a value. You can add a maximum of 20 tags to a record set.
For details about tag key and value requirements, see Table 2.
example_key1
+example_key1
example_value1
Description
+Description
(Optional) Supplementary information about the record set
+(Optional) Supplementary information about the record set.
You can enter a maximum of 255 characters.
-
+-
Table 2 Tag key and value requirements Parameter
+-Table 2 Tag key and value requirements Parameter
Requirements
+Requirements
Example Value
+Example Value
Key
+Key
- Cannot be left blank.
- Must be unique for each resource.
- Can contain a maximum of 36 characters.
- Cannot be left blank.
- Must be unique for each resource.
- Can contain a maximum of 36 characters.
- Can contain only letters, digits, hyphens (-), at signs (@), and underscores (_).
example_key1
+example_key1
Value
+Value
- Cannot be left blank.
- Can contain a maximum of 43 characters.
- Cannot be left blank.
- Can contain a maximum of 43 characters.
- Can contain only letters, digits, hyphens (-), at signs (@), and underscores (_).
example_value1
+example_value1
- Click OK.
- Switch back to the Record Sets page.
View the added record set in the record set list of the zone and ensure that the status of the record set is Normal.
+- Click OK.
- Switch back to the Record Sets tab.
diff --git a/docs/dns/umn/dns_usermanual_0013.html b/docs/dns/umn/dns_usermanual_0013.html index e03b95e6..802809a0 100644 --- a/docs/dns/umn/dns_usermanual_0013.html +++ b/docs/dns/umn/dns_usermanual_0013.html @@ -1,109 +1,108 @@The added record set is in the Normal state.
Adding an SRV Record Set
-Scenarios
To record services provided by a server, you can add SRV record sets for a domain name.
+-Scenarios
To tag a server to show what services it provides, you can add SRV record sets for a domain name.
For details about other record set types, see Record Set Types and Configuration Rules.
Procedure
- Log in to the management console.
- In the service list, choose Network > Domain Name Service.
The DNS console is displayed.
-
- In the navigation pane, choose Public Zones or Private Zones.
The zone list is displayed.
- - (Optional) If you have selected Private Zones, click on the upper left corner to select the region and project.
- Click the zone name.
- Click Add Record Set.
The Add Record Set dialog box is displayed.
-
- Set required parameters based on Table 1.
-
Table 1 Parameters for adding an SRV record set Parameter
+Procedure
- Log in to the management console.
- In the service list, choose Network > Domain Name Service.
The DNS console is displayed.
+ - In the navigation pane, choose Public Zones or Private Zones.
The zone list is displayed.
+ - (Optional) If you have selected Private Zones, click on the upper left corner to select the region and project.
- Click the domain name.
- Click Add Record Set.
The Add Record Set dialog box is displayed.
+ - Configure the parameters based on Table 1.
+-
Table 1 Parameters for adding an SRV record set Parameter
Description
+Description
Example Value
+Example Value
Name
+Name
Service (for example, FTP, SSH, or SIP) provided over the specified protocol (for example, TCP or UDP) on a host
+Service (for example, FTP, SSH, or SIP) provided over the specified protocol (for example, TCP or UDP) on a host
The format is _Service name._Protocol.
_ftp._tcp
+_ftp._tcp
_ftp._tcp indicates that the host provides the FTP service over TCP.
Type
+Type
Type of the record set
-If a message is displayed indicating that the record set you are trying to create exists, the record set conflicts with an existing record set.
+Type of the record set
+A message may be displayed indicating that the record set you are trying to add conflicts with an existing record set.
SRV – Record servers providing specific services
+SRV – Record servers providing specific services
TTL (s)
+TTL (s)
Cache duration of the record set on a local DNS server, in seconds
+Cache duration of the record set on a local DNS server, in seconds.
The value ranges from 1 to 2147483647, and the default is 300.
If your service address changes frequently, set TTL to a smaller value.
The default value is 300, which is, 5 minutes.
+300
Value
+Value
Server address
+Server address
You can enter a maximum of 50 record values, each on a separate line.
The value format is [priority] [weight] [port number] [server address].
Configuration rules:
-- The priority, weight, and port number range from 0 to 65535.
- A smaller priority value indicates a higher priority.
- A larger weight value indicates a larger weight.
- The server address is the domain name of the target server.
Ensure that the domain name can be resolved.
+- The priority, weight, and port number range from 0 to 65535.
- A smaller value indicates a higher priority.
- A larger value indicates a larger weight.
- The server address is the domain name of the target server.
NOTE:The system checks the priority values first. If the priority values are the same, the system will check the weight values.
+NOTE:If the record set values have the same priority, requests to the domain name will be routed based on weights.
2 1 2355 example_server.test.com
+2 1 2355 example_server.test.com
Tags
+Tag
(Optional) Identifier of a resource
-Each tag contains a key and a value. You can add a maximum of 20 tags to a record set. This parameter is displayed when you enable Other Settings.
+(Optional) Identifier of a record set. Each tag contains a key and a value. You can add a maximum of 20 tags to a record set.
For details about tag key and value requirements, see Table 2.
example_key1
+example_key1
example_value1
Description
+Description
(Optional) Supplementary information about the record set
+(Optional) Supplementary information about the record set.
You can enter a maximum of 255 characters.
-
+-
Table 2 Tag key and value requirements Parameter
+-Table 2 Tag key and value requirements Parameter
Requirements
+Requirements
Example Value
+Example Value
Key
+Key
- Cannot be left blank.
- Must be unique for each resource.
- Can contain a maximum of 36 characters.
- Cannot be left blank.
- Must be unique for each resource.
- Can contain a maximum of 36 characters.
- Can contain only letters, digits, hyphens (-), at signs (@), and underscores (_).
example_key1
+example_key1
Value
+Value
- Cannot be left blank.
- Can contain a maximum of 43 characters.
- Cannot be left blank.
- Can contain a maximum of 43 characters.
- Can contain only letters, digits, hyphens (-), at signs (@), and underscores (_).
example_value1
+example_value1
- Click OK.
- Switch back to the Record Sets page.
View the added record set in the record set list of the zone and ensure that the status of the record set is Normal.
+- Click OK.
- Switch back to the Record Sets tab.
diff --git a/docs/dns/umn/dns_usermanual_0014.html b/docs/dns/umn/dns_usermanual_0014.html index ba0f3066..21438481 100644 --- a/docs/dns/umn/dns_usermanual_0014.html +++ b/docs/dns/umn/dns_usermanual_0014.html @@ -7,108 +7,107 @@The added record set is in the Normal state.
-Constraints
CAA record sets can be added only to public zones.
Procedure
- Log in to the management console.
- In the service list, choose Network > Domain Name Service.
The DNS console is displayed.
-
- In the navigation pane, choose Public Zones.
The Public Zones page is displayed.
- - Click the zone name.
- Click Add Record Set.
The Add Record Set dialog box is displayed.
-
- Set required parameters based on Table 1. -
Associating a VPC with a Private Zone
-Scenarios
Associate a VPC with a private zone so that the private domain name can work in this VPC.
- This VPC must be the same as the VPC where the servers are deployed. Otherwise, the domain name cannot be resolved.
+-Scenarios
Associate a VPC with a private zone so that the private domain name can be resolved within this VPC.
+ 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.
Procedure
Private Zone
-What Is a Private Zone?
A private zone contains information about how to map domain names used within VPCs such as ecs.com to private IP addresses such as 192.168.1.1. With private domain names, your ECSs can communicate with each other within the VPCs without having to connect to the Internet. You can also access cloud services, such as OBS and SMN, via the private DNS server.
+Private Domain Name Resolution
+- - \ No newline at end of file diff --git a/docs/dns/umn/dns_pd_0006.html b/docs/dns/umn/dns_pd_0006.html index c89a347a..222d992d 100644 --- a/docs/dns/umn/dns_pd_0006.html +++ b/docs/dns/umn/dns_pd_0006.html @@ -1,10 +1,10 @@-Private Zone
A private zone contains information about how to map a domain name (such as ecs.com) and its subdomains used within one or more VPCs to private IP addresses (such as 192.168.1.1). With private domain names, your ECSs can communicate with each other within a VPC without having to connect to the Internet. These ECSs can also access cloud services, such as OBS and SMN, over a private network.
Figure 1 shows the process how a private domain name is resolved.
- -When an ECS in the VPC requests a private domain name, the private DNS server directly returns a private IP address mapped to the domain name.
+Figure 1 shows how a private domain name is resolved by a private DNS server.
+ +When an ECS in the VPC requests to access a private domain name, the private DNS server directly returns a private IP address mapped to the domain name.
Private zones allow you to:
-You can use private domain names in the following scenarios:
- +-Managing ECS Host Names
You can plan host names based on the locations, usages, and account information of ECSs, and map the host names to private IP addresses, helping you manage ECSs more easily.
For example, if you have deployed 20 ECSs in an AZ, 10 for website A and 10 for website B, you can plan their host names (private domain names) as follows:
After you configure the host names, you will be able to quickly determine the locations and usages of ECSs during routine management and maintenance.
See Configuring a Private Zone for detailed operations.
Replacing an ECS Without Service Interruption
As the number of Internet users is continuously increasing, a website application deployed only on one server can hardly handle concurrent requests during business spikes. A common practice is to deploy the application on multiple servers and distribute the load across servers.
-These servers are in the same VPC and communicate with each other using private IP addresses that are coded into internal APIs called among ECSs. If one server is replaced in the system, its private IP address changes accordingly. As a result, you need to change this IP address in the APIs and re-publish the website. This poses challenges for system maintenance.
-If you create a private zone for each server in the VPCs and map their host names to private IP addresses, they will be able to communicate using private domain names. When you replace any of the ECSs, you only need to change the IP address in record sets, instead of modifying the code.
-Figure 2 shows a typical scenario of private zones.
- -ECSs and RDS instances are in the same VPC.
-When ECS1 becomes faulty, the backup server ECS2 must work instead. However, if no private domain names are configured for the two ECSs, you need to change the private IP addresses in the code for ECS0. This will interrupt services, and you will need to publish the website again.
-Now assume that you have configured private domain names for the ECSs and have included these domain names in the code. If ECS1 becomes faulty, you only need to change the DNS records to direct traffic to ECS2. Services are not interrupted, and you do not need to publish the website again.
+Keeping Your Website Up and Running Even While Your Server Is Being Replaced
As the number of Internet users is continuously increasing, a website or web application deployed on a single server can hardly handle concurrent requests during peak hours. A common practice is to deploy the website or application on multiple servers and distribute the load across the servers.
+These servers are in the same VPC and communicate with each other using private IP addresses that are coded into internal APIs called among the servers. If one of these servers is replaced, its private IP address changes. As a result, you need to change this IP address in the APIs and re-publish the website. This poses challenges for system maintenance.
+If you create a private zone for each server and configure record sets to map their private domain names to the private IP addresses, they will be able to communicate using private domain names. When you replace any of the servers, you only need to change the private IP address in the record set, instead of modifying the code.
+Figure 2 illustrates such use of private domain name resolution.
+ +The ECSs and RDS instances are in the same VPC.
+When ECS1 becomes faulty, ECS2 must take over. However, if no private zones are configured for the two ECSs, you need to change the private IP addresses in the code for ECS0. This will interrupt services, and you will need to publish the website again.
+Now assume that you have configured private zones for the ECSs and have included their private names in the code. If ECS1 becomes faulty, you only need to change the DNS records to direct traffic to ECS2. Services are not interrupted, and you do not need to publish the website again.
Accessing Cloud Resources
Configure private domain names for ECSs so that they can access other cloud services, such as SMN and OBS, without connecting to the Internet.
When you create an ECS, note the following:
-@@ -41,10 +41,3 @@Reverse Resolution
-- - \ No newline at end of file diff --git a/docs/dns/umn/dns_pd_0008.html b/docs/dns/umn/dns_pd_0008.html index 1ca3ccc4..9b1d4e4e 100644 --- a/docs/dns/umn/dns_pd_0008.html +++ b/docs/dns/umn/dns_pd_0008.html @@ -1,42 +1,42 @@ -Reverse resolution involves obtaining a domain name based on an IP address and is typically used to improve credibility of email servers.
-After a recipient server receives an email, it checks whether the IP address and domain name of the sender server are trustworthy and determines whether the email is spam. If the recipient server cannot obtain the domain name mapped to the IP address of the sender server, it considers that the email is sent by a malicious host and rejects it. It is necessary to configure pointer records (PTR) to point the IP addresses of your email servers to domain names.
+Reverse resolution, also called as reverse DNS lookup, resolves an IP address back to a host name. This is typically used to affirm the credibility of email servers.
+After a recipient server receives an email, it checks whether the IP address and domain name of the sender server are trustworthy and determines whether the email is spam. If the recipient server cannot obtain the domain name mapped to the IP address of the sender server, it concludes that the email is sent by a malicious host and rejects it. It is necessary to configure pointer records (PTR) to point the IP addresses of your email servers to domain names.
In the following figure, an ECS serves as an email server, and a PTR record is configured to map the EIP of the ECS to the domain name configured for accessing the email server.
- + Figure 1 shows only the process for reverse resolution. Information about how an email server checks the credibility of the sender's IP address and whether domain name is available on the Internet is not provided here.
If no PTR records are configured, the recipient server will treat emails from the email server as spam or malicious and discard them.
@@ -16,10 +16,3 @@Related Services
+Integration with Other Services
Table 1 shows the relationships between DNS and other services.
-Table 1 Related services Description
+Table 1 DNS and other services Related Service
Related Service
+Description
Reference
+Reference
Provide public domain name resolution services for ECSs.
+Elastic Cloud Server (ECS)
Elastic Cloud Server (ECS)
+DNS can resolve the domain names to IP addresses of ECSs where a website or application is deployed so that end users can use domain name to access the website or application.
+ Create VPCs for the DNS service.
+Virtual Private Cloud (VPC)
Virtual Private Cloud (VPC)
+DNS can resolve private domain names that are used for network connections within VPCs.
+ Host static website resources to map domain names to buckets.
+Object Storage Service (OBS)
Object Storage Service (OBS)
+DNS maps your domain name to a bucket's access domain name for you to access the static websites hosted in the bucket.
Using a User-Defined Domain Name to Configure Static Website
+Using a User-Defined Domain Name to Configure Static Website
Record operations performed on the DNS service
+Cloud Trace Service (CTS)
Cloud Trace Service (CTS)
+CTS can record the operations performed on the DNS service.
+ Domain Name Format and Structure
+Domain Name Format and DNS Hierarchy
A valid domain name meets the following requirements:
Domain names are classified into the following levels based on their structure:
+A domain name is divided into the following levels based on its structure:
diff --git a/docs/dns/umn/dns_pd_0011.html b/docs/dns/umn/dns_pd_0011.html index e988bfed..75d2c249 100644 --- a/docs/dns/umn/dns_pd_0011.html +++ b/docs/dns/umn/dns_pd_0011.html @@ -1,7 +1,7 @@Project
-Projects are used to group and isolate OpenStack resources, including computing, storage, and network resources. Multiple projects can be created for one account. A project can be a department or a project team.
+Projects are used to group and isolate cloud resources, including computing, storage, and network resources. Multiple projects can be created for one account. A project can be a department or a project team.
Public zones are global-level resources, while private zones and PTR records are resources at the region level. Private zones and PTR records are isolated and managed based on projects. You need to create, query, and configure private zones or PTR records in specific regions and projects.
diff --git a/docs/dns/umn/dns_pd_0013.html b/docs/dns/umn/dns_pd_0013.html index df7ed7e8..b38fdbe7 100644 --- a/docs/dns/umn/dns_pd_0013.html +++ b/docs/dns/umn/dns_pd_0013.html @@ -4,7 +4,7 @@The system provides two types of permissions by default: user management and resource management.
The DNS service provides the following resources: public zones, private zones, and PTR records.
-For details, see section Permissions.
diff --git a/docs/dns/umn/dns_qs_0001.html b/docs/dns/umn/dns_qs_0001.html index 9be3d9d7..efc99277 100644 --- a/docs/dns/umn/dns_qs_0001.html +++ b/docs/dns/umn/dns_qs_0001.html @@ -1,10 +1,10 @@ -Quick Start
-DNS provides domain name resolution services in different network scenarios.
-Selecting a Service Type
Select a DNS service type based on Table 1.
+Before You Start
+DNS provides a set of functions for different scenarios.
+When DNS Is Required
You can select a type of function based on Table 1 to suit your network scenario.
-Table 1 DNS service types Type
+Table 1 Scenarios where DNS is required Function
Scenario
Public domain resolution
+Public domain name resolution
Map domain names to web servers or web applications on the Internet.
+Domain names are mapped to the public IP addresses of web servers or web applications on the Internet so that end users are routed to your website or application.
+ Private domain resolution
+Private domain name resolution
Map private domain names to private IP addresses within VPCs.
+Domain names are mapped to the private IP addresses within the VPCs for accessing cloud resources or cloud services over a private network.
Reverse resolution
Obtain public domain names based on IP addresses. PTR records are mainly used to build email servers.
+EIPs are mapped to domain names, which is often used by email servers against spammers.
-
-
Configuring a Private Zone
-Scenarios
If you have deployed ECSs and other cloud services on the cloud, you can configure private domain names for the ECSs so that they can communicate using domain names within VPCs.
-You can create any private zones for domain names that are unique within VPCs. You do not need to register the domain names.
-This section describes how to configure a private zone for a private domain name and add an A record set.
+-Scenario
If you have deployed ECSs and other cloud services within VPCs, you can configure private domain names for the ECSs so that they can communicate with each other or access the cloud services over a private network.
+You can create any private zones that are unique within VPCs. You do not need to register the domain names.
Prerequisites
You have created an ECS and obtained its VPC name and private IP address.
+-Prerequisites
You have created an ECS and obtained its VPC name and private IP address.
Process
Figure 1 shows the process for configuring a private zone for a domain name.
- +-Process Flow
Figure 1 shows the process of configuring a private zone for routing traffic within VPCs.
+ + To ensure that the private domain name can be resolved in the associated VPC, verify that the DNS server addresses for the VPC subnet are those provided by the DNS service. If the DNS server addresses are not those provided by the DNS service, change them.
+You can also change the DNS server addresses of the VPC subnet where the domain name is used.
+Create a Private Zone
Create a private zone to allow access to your ECS using a private domain name.
- - Configure the parameters based on Table 3. +
- On the Private Zones page, click the domain name of the private zone you created.
