forked from docs/doc-exports
DNS UMN 0930 version
Reviewed-by: Kucerak, Kristian <kristian.kucerak@t-systems.com> Co-authored-by: Qin Ying, Fan <fanqinying@huawei.com> Co-committed-by: Qin Ying, Fan <fanqinying@huawei.com>
This commit is contained in:
parent
97c594f41f
commit
97832252bc
652
docs/dns/umn/ALL_META.TXT.json
Normal file
652
docs/dns/umn/ALL_META.TXT.json
Normal file
File diff suppressed because it is too large
Load Diff
587
docs/dns/umn/CLASS.TXT.json
Normal file
587
docs/dns/umn/CLASS.TXT.json
Normal file
File diff suppressed because it is too large
Load Diff
3
docs/dns/umn/PARAMETERS.txt
Normal file
3
docs/dns/umn/PARAMETERS.txt
Normal file
@ -0,0 +1,3 @@
|
|||||||
|
version=""
|
||||||
|
language="en-us"
|
||||||
|
type=""
|
13
docs/dns/umn/dns_faq_006.html
Normal file
13
docs/dns/umn/dns_faq_006.html
Normal file
@ -0,0 +1,13 @@
|
|||||||
|
<a name="dns_faq_006"></a><a name="dns_faq_006"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Will I Be Billed for the DNS Service?</h1>
|
||||||
|
<div id="body1473682115482"><p id="dns_faq_006__p6580081113617">Yes.</p>
|
||||||
|
<p id="dns_faq_006__p34422971113632">The DNS service is charged in two parts:</p>
|
||||||
|
<ul id="dns_faq_006__ul1045217411375"><li id="dns_faq_006__li2214904411375">Zone: charged based on how long the domain name is managed</li><li id="dns_faq_006__li16637701184559">Record set: charged based on the domain name resolution counts</li></ul>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="dns_faq_1402.html">DNS Overview</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
12
docs/dns/umn/dns_faq_007.html
Normal file
12
docs/dns/umn/dns_faq_007.html
Normal file
@ -0,0 +1,12 @@
|
|||||||
|
<a name="dns_faq_007"></a><a name="dns_faq_007"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">How Many Zones, PTR Records, and Record Sets Can I Create?</h1>
|
||||||
|
<div id="body1473737884957"><p id="dns_faq_007__p4841552892354">By default, you can use an account to create up to 50 public zones, 50 private zones, 50 PTR records, and 500 record sets.</p>
|
||||||
|
<p id="dns_faq_007__p36682672114047">If the quotas do not meet your service requirements, contact customer service to request an increased quota.</p>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="dns_faq_1402.html">DNS Overview</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
13
docs/dns/umn/dns_faq_008.html
Normal file
13
docs/dns/umn/dns_faq_008.html
Normal file
@ -0,0 +1,13 @@
|
|||||||
|
<a name="dns_faq_008"></a><a name="dns_faq_008"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">What Can I Do If the System Prompts that the Domain Name Already Exists When I Create a Public Zone?</h1>
|
||||||
|
<div id="body1473737884958"><p id="dns_faq_008__p31716631153527">If the system prompts that the domain name has been created by another user when you create a public zone, send an email to <strong id="dns_faq_008__b8676311114912">cloud-products@telekom.de</strong> for identity authentication. After the authentication is approved, the system sends an email to notify you that you can re-create the zone.</p>
|
||||||
|
<div class="p" id="dns_faq_008__p41911933153527">Provide the following information in the email:<ul id="dns_faq_008__ul491779142729"><li id="dns_faq_008__li57172881142729">Involved domain name</li><li id="dns_faq_008__li44793884142729">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</li></ul>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="dns_faq_1405.html">Public Zones</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
13
docs/dns/umn/dns_faq_009.html
Normal file
13
docs/dns/umn/dns_faq_009.html
Normal file
@ -0,0 +1,13 @@
|
|||||||
|
<a name="dns_faq_009"></a><a name="dns_faq_009"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Why Was the Email Address Format Changed in the SOA Record?</h1>
|
||||||
|
<div id="body1484624343246"><p id="dns_faq_009__p3110562492847">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 <strong id="dns_faq_009__b1777118503202">HOSTMASTER@</strong><em id="dns_faq_009__i14512549205">Domain name</em> as the email address.</p>
|
||||||
|
<p id="dns_faq_009__p4001883493814">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.</p>
|
||||||
|
<p id="dns_faq_009__p60348772144337">For example, if you enter <strong id="dns_faq_009__b84235270614459">test.hostmaster@example.com</strong> when you create the zone, the email address displayed in the SOA record set is <strong id="dns_faq_009__b842352706144559">test\.hostmaster.example.com</strong>.</p>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="dns_faq_1402.html">DNS Overview</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
13
docs/dns/umn/dns_faq_010.html
Normal file
13
docs/dns/umn/dns_faq_010.html
Normal file
@ -0,0 +1,13 @@
|
|||||||
|
<a name="dns_faq_010"></a><a name="dns_faq_010"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Does DNS Support Wildcard Entries?</h1>
|
||||||
|
<div id="body1487816828175"><p id="dns_faq_010__p13453949165030">DNS allows you to configure wildcard entries.</p>
|
||||||
|
<p id="dns_faq_010__p9777305102713">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.</p>
|
||||||
|
<p id="dns_faq_010__p8060118">DNS supports wildcard entries for the following record set types: A, AAAA, MX, CNAME, TXT, CAA, and SRV.</p>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="dns_faq_1402.html">DNS Overview</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
14
docs/dns/umn/dns_faq_011.html
Normal file
14
docs/dns/umn/dns_faq_011.html
Normal file
@ -0,0 +1,14 @@
|
|||||||
|
<a name="dns_faq_011"></a><a name="dns_faq_011"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">How Are Zones Queried to Resolve a Domain Name?</h1>
|
||||||
|
<div id="body1493171896152"><p id="dns_faq_011__p35723779152428">When a domain name resolution request is initiated, a matched subdomain is first queried.</p>
|
||||||
|
<ul id="dns_faq_011__ul704442152432"><li id="dns_faq_011__li42703860152432">If a zone is created for the subdomain, the system returns the result based on the zone configuration.</li><li id="dns_faq_011__li66562933152530">If a zone is not created for the subdomain, the system queries the domain name in the zone created for the domain name.</li></ul>
|
||||||
|
<p id="dns_faq_011__p15661941152538">For example, suppose you have created one zone named <strong id="dns_faq_011__b12925638193310">example.com</strong> and added an A record set to it, with the <strong id="dns_faq_011__b17491033151920">Name</strong> field set to <strong id="dns_faq_011__b153371536171912">www</strong>, and you have also created another zone named <strong id="dns_faq_011__b4532713173419">www.example.com</strong> but have not added an A record set to this zone.</p>
|
||||||
|
<p id="dns_faq_011__p3085515161116">If a visitor accesses www.example.com, the domain name is first queried in the zone named <strong id="dns_faq_011__b1994525383415">www.example.com</strong>. However, no result will be returned because no record sets have been added to the zone.</p>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="dns_faq_1402.html">DNS Overview</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
181
docs/dns/umn/dns_faq_031.html
Normal file
181
docs/dns/umn/dns_faq_031.html
Normal file
File diff suppressed because it is too large
Load Diff
78
docs/dns/umn/dns_faq_032.html
Normal file
78
docs/dns/umn/dns_faq_032.html
Normal file
@ -0,0 +1,78 @@
|
|||||||
|
<a name="dns_faq_032"></a><a name="dns_faq_032"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">What Is CAA?</h1>
|
||||||
|
<div id="body1519870470780"><p id="dns_faq_032__p61745197150">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.</p>
|
||||||
|
<div class="section" id="dns_faq_032__section78537244532"><h4 class="sectiontitle">CAA Specifications</h4><p id="dns_faq_032__p16333165717483">Domain name owners can create CAA records to specify authorized CAs that can issue SSL certificates.</p>
|
||||||
|
<p id="dns_faq_032__p14564171123">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.</p>
|
||||||
|
<p id="dns_faq_032__p1770902113565">CAs will perform a DNS lookup for CAA records when they issue certificates.</p>
|
||||||
|
<ul id="dns_faq_032__ul23651723135614"><li id="dns_faq_032__li899581619517">If a CA does not find a CAA record, it can issue a certificate for the domain name.<p id="dns_faq_032__p106161250711"><a name="dns_faq_032__li899581619517"></a><a name="li899581619517"></a>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.</p>
|
||||||
|
</li><li id="dns_faq_032__li1092914272586">If the CA finds a CAA record that authorizes it to issue certificates, it will issue a certificate for the domain name.</li><li id="dns_faq_032__li202122027165612">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.</li></ul>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="dns_faq_032__section167971597533"><h4 class="sectiontitle">CAA Record</h4><p id="dns_faq_032__p16909334125413">A CAA record consists of a flag byte <strong id="dns_faq_032__b842352706155045">[flag]</strong>, a property tag, and a property value <strong id="dns_faq_032__b842352706155051">[tag]-[value]</strong>. You can create multiple CAA records for a domain name.</p>
|
||||||
|
|
||||||
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="dns_faq_032__table17725641112120" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Configuration of CAA records</caption><thead align="left"><tr id="dns_faq_032__row187268412211"><th align="left" class="cellrowborder" valign="top" width="24.242424242424242%" id="mcps1.3.3.3.2.4.1.1"><p id="dns_faq_032__p17260416215">Function</p>
|
||||||
|
</th>
|
||||||
|
<th align="left" class="cellrowborder" valign="top" width="23.232323232323235%" id="mcps1.3.3.3.2.4.1.2"><p id="dns_faq_032__p107261741132119">Example</p>
|
||||||
|
</th>
|
||||||
|
<th align="left" class="cellrowborder" valign="top" width="52.52525252525253%" id="mcps1.3.3.3.2.4.1.3"><p id="dns_faq_032__p6726104110214">Description</p>
|
||||||
|
</th>
|
||||||
|
</tr>
|
||||||
|
</thead>
|
||||||
|
<tbody><tr id="dns_faq_032__row117262041172112"><td class="cellrowborder" rowspan="2" valign="top" width="24.242424242424242%" headers="mcps1.3.3.3.2.4.1.1 "><p id="dns_faq_032__p137261841172118">Configure a CAA record for one domain name.</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="23.232323232323235%" headers="mcps1.3.3.3.2.4.1.2 "><p id="dns_faq_032__p19726184114218">0 issue "ca.example.com"</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="52.52525252525253%" headers="mcps1.3.3.3.2.4.1.3 "><p id="dns_faq_032__p45933152818">Only the specified CA (<strong id="dns_faq_032__b193760717517189">ca.example.com</strong>) can issue certificates for a particular domain name (<strong id="dns_faq_032__b110240485517189">domain.com</strong>). Requests to issue certificates for the domain name by other CAs will be rejected.</p>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
<tr id="dns_faq_032__row127268411218"><td class="cellrowborder" valign="top" headers="mcps1.3.3.3.2.4.1.1 "><p id="dns_faq_032__p072612416211">0 issue ";"</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" headers="mcps1.3.3.3.2.4.1.2 "><p id="dns_faq_032__p14726134152119">No CA is allowed to issue certificates for the domain name <strong id="dns_faq_032__b84235270615569">domain.com</strong>.</p>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
<tr id="dns_faq_032__row5726341122120"><td class="cellrowborder" rowspan="2" valign="top" width="24.242424242424242%" headers="mcps1.3.3.3.2.4.1.1 "><p id="dns_faq_032__p149740122612">Configure the CA to report violations to the domain name holder.</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="23.232323232323235%" headers="mcps1.3.3.3.2.4.1.2 "><p id="dns_faq_032__p1172624172110">0 iodef "mailto:admin@domain.com"</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="52.52525252525253%" headers="mcps1.3.3.3.2.4.1.3 "><p id="dns_faq_032__p572613411210">If a certificate request violates the CAA record, the CA will notify the domain name holder of the violation.</p>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
<tr id="dns_faq_032__row6726114118217"><td class="cellrowborder" valign="top" headers="mcps1.3.3.3.2.4.1.1 "><p id="dns_faq_032__p1472634172117">0 iodef "http:// domain.com/log/"</p>
|
||||||
|
<p id="dns_faq_032__p15945133714424">0 iodef "https:// domain.com/log/"</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" headers="mcps1.3.3.3.2.4.1.2 "><p id="dns_faq_032__p177261419213">Requests to issue certificates by unauthorized CAs will be recorded.</p>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
<tr id="dns_faq_032__row1091554812514"><td class="cellrowborder" valign="top" width="24.242424242424242%" headers="mcps1.3.3.3.2.4.1.1 "><p id="dns_faq_032__p15915144822517">Authorize a CA to issue wildcard certificates.</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="23.232323232323235%" headers="mcps1.3.3.3.2.4.1.2 "><p id="dns_faq_032__p591564812251">0 issuewild "ca.example.com"</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="52.52525252525253%" headers="mcps1.3.3.3.2.4.1.3 "><p id="dns_faq_032__p69154484255">The specified CA (<strong id="dns_faq_032__b8423527061622">ca.example.com</strong>) can issue wildcard certificates for the domain name.</p>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
<tr id="dns_faq_032__row6815165112515"><td class="cellrowborder" valign="top" width="24.242424242424242%" headers="mcps1.3.3.3.2.4.1.1 "><p id="dns_faq_032__p08156512257">Configuration example</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="23.232323232323235%" headers="mcps1.3.3.3.2.4.1.2 "><p id="dns_faq_032__p76671429277">0 issue "ca.abc.com"</p>
|
||||||
|
<p id="dns_faq_032__p3667742162717">0 issuewild "ca.def.com"</p>
|
||||||
|
<p id="dns_faq_032__p166794217275">0 iodef "mailto:admin@domain.com"</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="52.52525252525253%" headers="mcps1.3.3.3.2.4.1.3 "><p id="dns_faq_032__p79761441164912">The example configures a CAA record for the domain name <strong id="dns_faq_032__b8423527061647">domain.com</strong>.</p>
|
||||||
|
<ul id="dns_faq_032__ul2285344104918"><li id="dns_faq_032__li20765750104917">Only CA <strong id="dns_faq_032__b84235270616425">ca.abc.com</strong> can issue certificates of all types.</li><li id="dns_faq_032__li6981012155212">Only CA <strong id="dns_faq_032__b84235270616454">ca.def.com</strong> can issue wildcard certificates.</li><li id="dns_faq_032__li12561158144911">Any other CAs are not allowed to issue certificates.</li><li id="dns_faq_032__li92852445491">When a violation occurs, the CA sends a notification to <strong id="dns_faq_032__b84235270616554">admin@domain.com</strong>.</li></ul>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
</tbody>
|
||||||
|
</table>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="dns_faq_032__section614411459319"><h4 class="sectiontitle">Checking Whether a CAA Record Has Taken Effect</h4><p id="dns_faq_032__p4344564452">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.</p>
|
||||||
|
<p id="dns_faq_032__p4991101111475">Command format: <strong id="dns_faq_032__b1877112419248">dig</strong> [<em id="dns_faq_032__i1930613526455">Record set type</em>] [<em id="dns_faq_032__i7500656194520">Domain name</em>] <strong id="dns_faq_032__b6133449247">+trace</strong>.</p>
|
||||||
|
<p id="dns_faq_032__p2023713557484">Example command:</p>
|
||||||
|
<p id="dns_faq_032__p10698153811445"><strong id="dns_faq_032__b161441034155213">dig caa www.example.com +trace</strong></p>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="dns_faq_1402.html">DNS Overview</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
15
docs/dns/umn/dns_faq_1100.html
Normal file
15
docs/dns/umn/dns_faq_1100.html
Normal file
@ -0,0 +1,15 @@
|
|||||||
|
<a name="dns_faq_1100"></a><a name="dns_faq_1100"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">FAQs</h1>
|
||||||
|
<div id="body1473682115482"></div>
|
||||||
|
<div>
|
||||||
|
<ul class="ullinks">
|
||||||
|
<li class="ulchildlink"><strong><a href="dns_faq_1402.html">DNS Overview</a></strong><br>
|
||||||
|
</li>
|
||||||
|
<li class="ulchildlink"><strong><a href="dns_faq_1405.html">Public Zones</a></strong><br>
|
||||||
|
</li>
|
||||||
|
<li class="ulchildlink"><strong><a href="dns_faq_1406.html">Private Zones</a></strong><br>
|
||||||
|
</li>
|
||||||
|
</ul>
|
||||||
|
</div>
|
||||||
|
|
27
docs/dns/umn/dns_faq_1402.html
Normal file
27
docs/dns/umn/dns_faq_1402.html
Normal file
@ -0,0 +1,27 @@
|
|||||||
|
<a name="dns_faq_1402"></a><a name="dns_faq_1402"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">DNS Overview</h1>
|
||||||
|
<div id="body1589365795409"></div>
|
||||||
|
<div>
|
||||||
|
<ul class="ullinks">
|
||||||
|
<li class="ulchildlink"><strong><a href="dns_faq_006.html">Will I Be Billed for the DNS Service?</a></strong><br>
|
||||||
|
</li>
|
||||||
|
<li class="ulchildlink"><strong><a href="dns_faq_007.html">How Many Zones, PTR Records, and Record Sets Can I Create?</a></strong><br>
|
||||||
|
</li>
|
||||||
|
<li class="ulchildlink"><strong><a href="dns_faq_010.html">Does DNS Support Wildcard Entries?</a></strong><br>
|
||||||
|
</li>
|
||||||
|
<li class="ulchildlink"><strong><a href="dns_faq_011.html">How Are Zones Queried to Resolve a Domain Name?</a></strong><br>
|
||||||
|
</li>
|
||||||
|
<li class="ulchildlink"><strong><a href="dns_faq_009.html">Why Was the Email Address Format Changed in the SOA Record?</a></strong><br>
|
||||||
|
</li>
|
||||||
|
<li class="ulchildlink"><strong><a href="dns_faq_032.html">What Is CAA?</a></strong><br>
|
||||||
|
</li>
|
||||||
|
<li class="ulchildlink"><strong><a href="dns_faq_140217.html">Can DNS Point a Domain Name to a Specific Port?</a></strong><br>
|
||||||
|
</li>
|
||||||
|
</ul>
|
||||||
|
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="dns_faq_1100.html">FAQs</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
11
docs/dns/umn/dns_faq_140217.html
Normal file
11
docs/dns/umn/dns_faq_140217.html
Normal file
@ -0,0 +1,11 @@
|
|||||||
|
<a name="dns_faq_140217"></a><a name="dns_faq_140217"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Can DNS Point a Domain Name to a Specific Port?</h1>
|
||||||
|
<div id="body0000001116629161"><p id="dns_faq_140217__p8060118">DNS cannot point a domain name to an IP address with a specific port (<em id="dns_faq_140217__i57924704410">Server IP address</em>:<em id="dns_faq_140217__i11881195016448">Port number</em>).</p>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="dns_faq_1402.html">DNS Overview</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
15
docs/dns/umn/dns_faq_1405.html
Normal file
15
docs/dns/umn/dns_faq_1405.html
Normal file
@ -0,0 +1,15 @@
|
|||||||
|
<a name="dns_faq_1405"></a><a name="dns_faq_1405"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Public Zones</h1>
|
||||||
|
<div id="body1589365795409"></div>
|
||||||
|
<div>
|
||||||
|
<ul class="ullinks">
|
||||||
|
<li class="ulchildlink"><strong><a href="dns_faq_008.html">What Can I Do If the System Prompts that the Domain Name Already Exists When I Create a Public Zone?</a></strong><br>
|
||||||
|
</li>
|
||||||
|
</ul>
|
||||||
|
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="dns_faq_1100.html">FAQs</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
15
docs/dns/umn/dns_faq_1406.html
Normal file
15
docs/dns/umn/dns_faq_1406.html
Normal file
@ -0,0 +1,15 @@
|
|||||||
|
<a name="dns_faq_1406"></a><a name="dns_faq_1406"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Private Zones</h1>
|
||||||
|
<div id="body1589441300631"></div>
|
||||||
|
<div>
|
||||||
|
<ul class="ullinks">
|
||||||
|
<li class="ulchildlink"><strong><a href="dns_faq_031.html">How Can I Configure a PTR Record to Map the IP Address of an ECS to a Domain Name?</a></strong><br>
|
||||||
|
</li>
|
||||||
|
</ul>
|
||||||
|
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="dns_faq_1100.html">FAQs</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
22
docs/dns/umn/dns_pd_0001.html
Normal file
22
docs/dns/umn/dns_pd_0001.html
Normal file
@ -0,0 +1,22 @@
|
|||||||
|
<a name="dns_pd_0001"></a><a name="dns_pd_0001"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Region and AZ</h1>
|
||||||
|
<div id="body1558578225705"><div class="section" id="dns_pd_0001__en-us_topic_0184026189_section388255972712"><h4 class="sectiontitle">Concept</h4><p id="dns_pd_0001__en-us_topic_0184026189_p212716216381">A region and availability zone (AZ) identify the location of a data center. You can create resources in a specific region and AZ.</p>
|
||||||
|
<ul id="dns_pd_0001__en-us_topic_0184026189_ul86578533460"><li id="dns_pd_0001__en-us_topic_0184026189_li14657175334618">A region is a physical data center, which is completely isolated to improve fault tolerance and stability. The region that is selected during resource creation cannot be changed after the resource is created.</li><li id="dns_pd_0001__en-us_topic_0184026189_li45875020473">An AZ is a physical location where resources use independent power supplies and networks. A region contains one or more AZs that are physically isolated but interconnected through internal networks. Because AZs are isolated from each other, any fault that occurs in one AZ will not affect others.</li></ul>
|
||||||
|
<p id="dns_pd_0001__en-us_topic_0184026189_p1479174514614"><a href="#dns_pd_0001__en-us_topic_0184026189_fig8747114281212">Figure 1</a> shows the relationship between regions and AZs.</p>
|
||||||
|
<div class="fignone" id="dns_pd_0001__en-us_topic_0184026189_fig8747114281212"><a name="dns_pd_0001__en-us_topic_0184026189_fig8747114281212"></a><a name="en-us_topic_0184026189_fig8747114281212"></a><span class="figcap"><b>Figure 1 </b>Regions and AZs</span><br><span><img class="vsd" id="dns_pd_0001__en-us_topic_0184026189_image12748194211128" src="en-us_image_0184026531.png"></span></div>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="dns_pd_0001__en-us_topic_0184026189_section67281149192216"><h4 class="sectiontitle">Selecting a Region</h4><p id="dns_pd_0001__en-us_topic_0184026189_p68521454132212">Select a region closest to your target users for lower network latency and quick access.</p>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="dns_pd_0001__en-us_topic_0184026189_section193971112578"><h4 class="sectiontitle">Selecting an AZ</h4><p id="dns_pd_0001__en-us_topic_0184026189_p859161416717">When deploying resources, consider your applications' requirements on disaster recovery (DR) and network latency.</p>
|
||||||
|
<ul id="dns_pd_0001__en-us_topic_0184026189_ul157203571473"><li id="dns_pd_0001__en-us_topic_0184026189_li7720175710711">For high DR capability, deploy resources in different AZs within the same region.</li><li id="dns_pd_0001__en-us_topic_0184026189_li109763595719">For lower network latency, deploy resources in the same AZ.</li></ul>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="dns_pd_0001__en-us_topic_0184026189_section1110135820407"><h4 class="sectiontitle">Regions and Endpoints</h4><p id="dns_pd_0001__en-us_topic_0184026189_p361784821111">Before you use an API to call resources, specify its region and endpoint. For more details, see <a href="https://docs.otc.t-systems.com/en-us/endpoint/index.html" target="_blank" rel="noopener noreferrer">Regions and Endpoints</a>.</p>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="dns_pd_0004.html">Product Concepts</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
23
docs/dns/umn/dns_pd_0004.html
Normal file
23
docs/dns/umn/dns_pd_0004.html
Normal file
@ -0,0 +1,23 @@
|
|||||||
|
<a name="dns_pd_0004"></a><a name="dns_pd_0004"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Product Concepts</h1>
|
||||||
|
<div id="body1571705601685"></div>
|
||||||
|
<div>
|
||||||
|
<ul class="ullinks">
|
||||||
|
<li class="ulchildlink"><strong><a href="dns_pd_0009.html">Domain Name Format and Structure</a></strong><br>
|
||||||
|
</li>
|
||||||
|
<li class="ulchildlink"><strong><a href="en-us_topic_0035467692.html">Record Set</a></strong><br>
|
||||||
|
</li>
|
||||||
|
<li class="ulchildlink"><strong><a href="dns_pd_0001.html">Region and AZ</a></strong><br>
|
||||||
|
</li>
|
||||||
|
<li class="ulchildlink"><strong><a href="dns_pd_0011.html">Project</a></strong><br>
|
||||||
|
</li>
|
||||||
|
<li class="ulchildlink"><strong><a href="dns_pd_0013.html">User Permissions</a></strong><br>
|
||||||
|
</li>
|
||||||
|
</ul>
|
||||||
|
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_0035204977.html">Overview</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
50
docs/dns/umn/dns_pd_0005.html
Normal file
50
docs/dns/umn/dns_pd_0005.html
Normal file
@ -0,0 +1,50 @@
|
|||||||
|
<a name="dns_pd_0005"></a><a name="dns_pd_0005"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Private Zone</h1>
|
||||||
|
<div id="body1545614829280"><div class="section" id="dns_pd_0005__section99761335172316"><h4 class="sectiontitle">What Is a Private Zone?</h4><p id="dns_pd_0005__p20171183872315">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.</p>
|
||||||
|
</div>
|
||||||
|
<p id="dns_pd_0005__p19364144289"><a href="#dns_pd_0005__fig9226124091216">Figure 1</a> shows the process how a private domain name is resolved.</p>
|
||||||
|
<div class="fignone" id="dns_pd_0005__fig9226124091216"><a name="dns_pd_0005__fig9226124091216"></a><a name="fig9226124091216"></a><span class="figcap"><b>Figure 1 </b>Process for resolving a private domain name</span><br><span><img id="dns_pd_0005__image82385421523" src="en-us_image_0159806763.png" title="Click to enlarge" class="imgResize"></span></div>
|
||||||
|
<p id="dns_pd_0005__p938254641419">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.</p>
|
||||||
|
<p id="dns_pd_0005__p32875415203">Private zones allow you to:</p>
|
||||||
|
<ul id="dns_pd_0005__ul776553314221"><li id="dns_pd_0005__li1258193792212">Flexibly customize private domain names in your VPCs.</li><li id="dns_pd_0005__li95811837192210">Associate one or more multiple VPCs with one domain name.</li><li id="dns_pd_0005__li175821437142212">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.</li></ul>
|
||||||
|
<p id="dns_pd_0005__p19129174912483">You can use private domain names in the following scenarios:</p>
|
||||||
|
<ul id="dns_pd_0005__ul1746715292710"><li id="dns_pd_0005__li1246742192714"><a href="#dns_pd_0005__section147015342425">Managing ECS Host Names</a></li><li id="dns_pd_0005__li13467929273"><a href="#dns_pd_0005__section2827056164219">Replacing an ECS Without Service Interruption</a></li><li id="dns_pd_0005__li846742202716"><a href="#dns_pd_0005__section1567083834313">Accessing Cloud Resources</a></li></ul>
|
||||||
|
<div class="section" id="dns_pd_0005__section147015342425"><a name="dns_pd_0005__section147015342425"></a><a name="section147015342425"></a><h4 class="sectiontitle">Managing ECS Host Names</h4><p id="dns_pd_0005__p991752911511">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.</p>
|
||||||
|
<p id="dns_pd_0005__p1885155117616">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:</p>
|
||||||
|
<ul id="dns_pd_0005__ul2044091392312"><li id="dns_pd_0005__li1944019131233">ECSs for website A: weba01.region1.az1.com – weba10.region1.az1.com</li><li id="dns_pd_0005__li14401133231">ECSs for website B: webb01.region1.az1.com – webb10.region1.az1.com</li></ul>
|
||||||
|
<p id="dns_pd_0005__p2588829757">After you configure the host names, you will be able to quickly determine the locations and usages of ECSs during routine management and maintenance.</p>
|
||||||
|
<p id="dns_pd_0005__p12727325115011">See <a href="dns_qs_0006.html">Configuring a Private Zone</a> for detailed operations.</p>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="dns_pd_0005__section2827056164219"><a name="dns_pd_0005__section2827056164219"></a><a name="section2827056164219"></a><h4 class="sectiontitle">Replacing an ECS Without Service Interruption</h4><p id="dns_pd_0005__p18884181233311">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.</p>
|
||||||
|
<p id="dns_pd_0005__p88845123333">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.</p>
|
||||||
|
<p id="dns_pd_0005__p4202038343">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.</p>
|
||||||
|
<p id="dns_pd_0005__p732504613346"><a href="#dns_pd_0005__fig8326104683415">Figure 2</a> shows a typical scenario of private zones.</p>
|
||||||
|
<div class="fignone" id="dns_pd_0005__fig8326104683415"><a name="dns_pd_0005__fig8326104683415"></a><a name="fig8326104683415"></a><span class="figcap"><b>Figure 2 </b>Configuring private DNS for cloud servers</span><br><span><img class="imgResize" id="dns_pd_0005__image12001424120" src="en-us_image_0196001479.png" title="Click to enlarge"></span></div>
|
||||||
|
<p id="dns_pd_0005__p163271646153413">ECSs and RDS instances are in the same VPC.</p>
|
||||||
|
<ul id="dns_pd_0005__ul11327154633410"><li id="dns_pd_0005__li6328846183416">ECS0: primary service node</li><li id="dns_pd_0005__li1932864603414">ECS1: public service interface</li><li id="dns_pd_0005__li1532964611348">RDS1: service database</li><li id="dns_pd_0005__li13301746183411">ECS2 and RDS2: backup service node and backup database</li></ul>
|
||||||
|
<p id="dns_pd_0005__p133074683418">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.</p>
|
||||||
|
<p id="dns_pd_0005__p033016465347">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.</p>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="dns_pd_0005__section1567083834313"><a name="dns_pd_0005__section1567083834313"></a><a name="section1567083834313"></a><h4 class="sectiontitle">Accessing Cloud Resources</h4><p id="dns_pd_0005__p1447513561116">Configure private domain names for ECSs so that they can access other cloud services, such as SMN and OBS, without connecting to the Internet.</p>
|
||||||
|
<p id="dns_pd_0005__p118754371890">When you create an ECS, note the following:</p>
|
||||||
|
<ul id="dns_pd_0005__ul1952162421511"><li id="dns_pd_0005__li962212415153">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.<p id="dns_pd_0005__p1777016196164"><a name="dns_pd_0005__li962212415153"></a><a name="li962212415153"></a><a href="#dns_pd_0005__fig42701320112215">Figure 3</a> shows the process for resolving a domain name when an ECS accesses cloud services.</p>
|
||||||
|
<p id="dns_pd_0005__p6623241171718">Requests are routed on the Internet, resulting in an increase in network latency.</p>
|
||||||
|
</li><li id="dns_pd_0005__li911572421611">If a private DNS server is configured for the subnet, it directly processes the requests to access cloud resources.<p id="dns_pd_0005__p175621528201515"><a name="dns_pd_0005__li911572421611"></a><a name="li911572421611"></a>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 <a href="#dns_pd_0005__fig42701320112215">Figure 3</a> shows the process.</p>
|
||||||
|
</li></ul>
|
||||||
|
<div class="fignone" id="dns_pd_0005__fig42701320112215"><a name="dns_pd_0005__fig42701320112215"></a><a name="fig42701320112215"></a><span class="figcap"><b>Figure 3 </b>Accessing cloud services</span><br><span><img id="dns_pd_0005__image238319185325" src="en-us_image_0000001133045125.png" title="Click to enlarge" class="imgResize"></span></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_0035204977.html">Overview</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
||||||
|
|
||||||
|
<script language="JavaScript">
|
||||||
|
<!--
|
||||||
|
image_size('.imgResize');
|
||||||
|
var msg_imageMax = "view original image";
|
||||||
|
var msg_imageClose = "close";
|
||||||
|
//--></script>
|
25
docs/dns/umn/dns_pd_0006.html
Normal file
25
docs/dns/umn/dns_pd_0006.html
Normal file
@ -0,0 +1,25 @@
|
|||||||
|
<a name="dns_pd_0006"></a><a name="dns_pd_0006"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Reverse Resolution</h1>
|
||||||
|
<div id="body1544408293219"><p id="dns_pd_0006__p870153112156">Reverse resolution involves obtaining a domain name based on an IP address and is typically used to improve credibility of email servers.</p>
|
||||||
|
<p id="dns_pd_0006__p13711315155">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.</p>
|
||||||
|
<p id="dns_pd_0006__p0711631131516">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.</p>
|
||||||
|
<div class="fignone" id="dns_pd_0006__fig272143141518"><a name="dns_pd_0006__fig272143141518"></a><a name="fig272143141518"></a><span class="figcap"><b>Figure 1 </b>Reverse resolution</span><br><span><img class="imgResize" id="dns_pd_0006__image21649580419" src="en-us_image_0165559749.png" title="Click to enlarge"></span></div>
|
||||||
|
<div class="note" id="dns_pd_0006__note1626614121213"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="dns_pd_0006__p226712413129"><a href="#dns_pd_0006__fig272143141518">Figure 1</a> 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.</p>
|
||||||
|
</div></div>
|
||||||
|
<p id="dns_pd_0006__p128213111510">If no PTR records are configured, the recipient server will treat emails from the email server as spam or malicious and discard them.</p>
|
||||||
|
<p id="dns_pd_0006__p6690174317271">See <a href="en-us_topic_0040322596.html">Configuring a PTR Record</a> for detailed operations.</p>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_0035204977.html">Overview</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
||||||
|
|
||||||
|
<script language="JavaScript">
|
||||||
|
<!--
|
||||||
|
image_size('.imgResize');
|
||||||
|
var msg_imageMax = "view original image";
|
||||||
|
var msg_imageClose = "close";
|
||||||
|
//--></script>
|
51
docs/dns/umn/dns_pd_0008.html
Normal file
51
docs/dns/umn/dns_pd_0008.html
Normal file
@ -0,0 +1,51 @@
|
|||||||
|
<a name="dns_pd_0008"></a><a name="dns_pd_0008"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Related Services</h1>
|
||||||
|
<div id="body1471073508374"><p id="dns_pd_0008__p1680281384513"><a href="#dns_pd_0008__table750930164612">Table 1</a> shows the relationships between DNS and other services.</p>
|
||||||
|
|
||||||
|
<div class="tablenoborder"><a name="dns_pd_0008__table750930164612"></a><a name="table750930164612"></a><table cellpadding="4" cellspacing="0" summary="" id="dns_pd_0008__table750930164612" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Related services</caption><thead align="left"><tr id="dns_pd_0008__row95109094618"><th align="left" class="cellrowborder" valign="top" width="33.33333333333333%" id="mcps1.3.2.2.4.1.1"><p id="dns_pd_0008__p13510603466">Description</p>
|
||||||
|
</th>
|
||||||
|
<th align="left" class="cellrowborder" valign="top" width="33.33333333333333%" id="mcps1.3.2.2.4.1.2"><p id="dns_pd_0008__p851018064618"><strong id="dns_pd_0008__b1061211918811">Related Service</strong></p>
|
||||||
|
</th>
|
||||||
|
<th align="left" class="cellrowborder" valign="top" width="33.33333333333333%" id="mcps1.3.2.2.4.1.3"><p id="dns_pd_0008__p145100054619"><strong id="dns_pd_0008__b187046151688">Reference</strong></p>
|
||||||
|
</th>
|
||||||
|
</tr>
|
||||||
|
</thead>
|
||||||
|
<tbody><tr id="dns_pd_0008__row651090164615"><td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.2.2.4.1.1 "><p id="dns_pd_0008__p3510140154618">Provide public domain name resolution services for ECSs.</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.2.2.4.1.2 "><p id="dns_pd_0008__p1551015016463">Elastic Cloud Server (ECS)</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.2.2.4.1.3 "><p id="dns_pd_0008__p20928194416557"><a href="en-us_topic_0035467699.html">Routing Internet Traffic to a Website</a></p>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
<tr id="dns_pd_0008__row53061925165214"><td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.2.2.4.1.1 "><p id="dns_pd_0008__p15307162515215">Create VPCs for the DNS service.</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.2.2.4.1.2 "><p id="dns_pd_0008__p16307162512523">Virtual Private Cloud (VPC)</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.2.2.4.1.3 "><p id="dns_pd_0008__p1530175916531"><a href="dns_qs_0006.html">Configuring a Private Zone</a></p>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
<tr id="dns_pd_0008__row2510140184614"><td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.2.2.4.1.1 "><p id="dns_pd_0008__p251020004619">Host static website resources to map domain names to buckets.</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.2.2.4.1.2 "><p id="dns_pd_0008__p1651010104613">Object Storage Service (OBS)</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.2.2.4.1.3 "><p id="dns_pd_0008__p1751019094618"><a href="https://docs.otc.t-systems.com/en-us/usermanual/obs/obs_03_0338.html" target="_blank" rel="noopener noreferrer">Using a User-Defined Domain Name to Configure Static Website</a></p>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
<tr id="dns_pd_0008__row125103084616"><td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.2.2.4.1.1 "><p id="dns_pd_0008__p11510900462">Record operations performed on the DNS service</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.2.2.4.1.2 "><p id="dns_pd_0008__p175102006466">Cloud Trace Service (CTS)</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.2.2.4.1.3 "><p id="dns_pd_0008__p19510907463"><a href="dns_usermanual_0043.html">DNS Operations Recorded by CTS</a></p>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
</tbody>
|
||||||
|
</table>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_0035204977.html">Overview</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
14
docs/dns/umn/dns_pd_0009.html
Normal file
14
docs/dns/umn/dns_pd_0009.html
Normal file
@ -0,0 +1,14 @@
|
|||||||
|
<a name="dns_pd_0009"></a><a name="dns_pd_0009"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Domain Name Format and Structure</h1>
|
||||||
|
<div id="body1471437528572"><p id="dns_pd_0009__p235855617375">A valid domain name meets the following requirements:</p>
|
||||||
|
<ul id="dns_pd_0009__ul1635825653714"><li id="dns_pd_0009__li1635816567373">A domain name is segmented using dots (.) into multiple labels.</li><li id="dns_pd_0009__li7358125613376">A domain name label can contain letters, digits, and hyphens (-) and cannot start or end with a hyphen.</li><li id="dns_pd_0009__li4360155693717">A label cannot exceed 63 characters.</li><li id="dns_pd_0009__li7360105620377">The total length of a domain name, including the dot at the end, cannot exceed 254 characters.</li></ul>
|
||||||
|
<p id="dns_pd_0009__p8060118">Domain names are classified into the following levels based on their structure:</p>
|
||||||
|
<ul id="dns_pd_0009__ul44922951234235"><li id="dns_pd_0009__li3236963816536">Root domain: . (a dot)</li><li id="dns_pd_0009__li62820813234235">Top-level domain: for example, .com, .net, .org, and .cn</li><li id="dns_pd_0009__li6157692234319">Second-level domain: subdomains of the top-level domain names, such as example.com, example.net, and example.org</li><li id="dns_pd_0009__li659910023441">Third-level domain: subdomains of the second-level domain names, such as abc.example.com, abc.example.net, and abc.example.org</li><li id="dns_pd_0009__li659224823451">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.</li></ul>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="dns_pd_0004.html">Product Concepts</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
12
docs/dns/umn/dns_pd_0011.html
Normal file
12
docs/dns/umn/dns_pd_0011.html
Normal file
@ -0,0 +1,12 @@
|
|||||||
|
<a name="dns_pd_0011"></a><a name="dns_pd_0011"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Project</h1>
|
||||||
|
<div id="body1502162460570"><p id="dns_pd_0011__p16454058112126">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.</p>
|
||||||
|
<p id="dns_pd_0011__p17151420203515">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.</p>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="dns_pd_0004.html">Product Concepts</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
15
docs/dns/umn/dns_pd_0013.html
Normal file
15
docs/dns/umn/dns_pd_0013.html
Normal file
@ -0,0 +1,15 @@
|
|||||||
|
<a name="dns_pd_0013"></a><a name="dns_pd_0013"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">User Permissions</h1>
|
||||||
|
<div id="body8662426"><p id="dns_pd_0013__en-us_topic_0054121392_p366227111256">The system provides two types of permissions by default: user management and resource management.</p>
|
||||||
|
<ul id="dns_pd_0013__u0471142da3d24388a34be64fda7a4773"><li id="dns_pd_0013__l8f41f2bee5a543de8deec8a993447fbd">User management refers to management of users, user groups, and user group permissions.</li><li id="dns_pd_0013__lb581aeef73e244c1884ded8d9f86776e">Resource management refers to control operations that can be performed by users on cloud service resources.</li></ul>
|
||||||
|
<p id="dns_pd_0013__p134783816465">The DNS service provides the following resources: public zones, private zones, and PTR records.</p>
|
||||||
|
<ul id="dns_pd_0013__ul52902040184610"><li id="dns_pd_0013__li829013403467">Public zone: global-level resources. However, you need to add permissions for users in the region, instead of in the global service.</li><li id="dns_pd_0013__li14576542114616">Private zone and PTR record: region-level resources. You need to add permissions for users in the project.</li></ul>
|
||||||
|
<p id="dns_pd_0013__en-us_topic_0054121392_p556181412556">For details, see section <a href="https://docs.otc.t-systems.com/en-us/permissions/index.html" target="_blank" rel="noopener noreferrer">Permissions</a>.</p>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="dns_pd_0004.html">Product Concepts</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
46
docs/dns/umn/dns_qs_0001.html
Normal file
46
docs/dns/umn/dns_qs_0001.html
Normal file
@ -0,0 +1,46 @@
|
|||||||
|
<a name="dns_qs_0001"></a><a name="dns_qs_0001"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Quick Start</h1>
|
||||||
|
<div id="body1540257032189"><p id="dns_qs_0001__p11279173055213">DNS provides domain name resolution services in different network scenarios.</p>
|
||||||
|
<div class="section" id="dns_qs_0001__section56191217531"><h4 class="sectiontitle">Selecting a Service Type</h4><p id="dns_qs_0001__p88161626124915">Select a DNS service type based on <a href="#dns_qs_0001__table977612405507">Table 1</a>.</p>
|
||||||
|
|
||||||
|
<div class="tablenoborder"><a name="dns_qs_0001__table977612405507"></a><a name="table977612405507"></a><table cellpadding="4" cellspacing="0" summary="" id="dns_qs_0001__table977612405507" frame="border" border="1" rules="all"><caption><b>Table 1 </b>DNS service types</caption><thead align="left"><tr id="dns_qs_0001__row87771409504"><th align="left" class="cellrowborder" valign="top" width="21.782178217821784%" id="mcps1.3.2.3.2.4.1.1"><p id="dns_qs_0001__p15777740175016">Type</p>
|
||||||
|
</th>
|
||||||
|
<th align="left" class="cellrowborder" valign="top" width="40.59405940594059%" id="mcps1.3.2.3.2.4.1.2"><p id="dns_qs_0001__p47771140115015">Scenario</p>
|
||||||
|
</th>
|
||||||
|
<th align="left" class="cellrowborder" valign="top" width="37.62376237623762%" id="mcps1.3.2.3.2.4.1.3"><p id="dns_qs_0001__p11777174055015">Reference</p>
|
||||||
|
</th>
|
||||||
|
</tr>
|
||||||
|
</thead>
|
||||||
|
<tbody><tr id="dns_qs_0001__row3777840175020"><td class="cellrowborder" valign="top" width="21.782178217821784%" headers="mcps1.3.2.3.2.4.1.1 "><p id="dns_qs_0001__p167777403501">Public domain resolution</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="40.59405940594059%" headers="mcps1.3.2.3.2.4.1.2 "><p id="dns_qs_0001__p777716406501">Map domain names to web servers or web applications on the Internet.</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="37.62376237623762%" headers="mcps1.3.2.3.2.4.1.3 "><p id="dns_qs_0001__p2956133163814"><a href="en-us_topic_0035467699.html">Routing Internet Traffic to a Website</a></p>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
<tr id="dns_qs_0001__row1577754016507"><td class="cellrowborder" valign="top" width="21.782178217821784%" headers="mcps1.3.2.3.2.4.1.1 "><p id="dns_qs_0001__p4777640105010">Private domain resolution</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="40.59405940594059%" headers="mcps1.3.2.3.2.4.1.2 "><p id="dns_qs_0001__p3777134025015">Map private domain names to private IP addresses within VPCs.</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="37.62376237623762%" headers="mcps1.3.2.3.2.4.1.3 "><p id="dns_qs_0001__p127771940205011"><a href="dns_qs_0006.html">Configuring a Private Zone</a></p>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
<tr id="dns_qs_0001__row187779402501"><td class="cellrowborder" valign="top" width="21.782178217821784%" headers="mcps1.3.2.3.2.4.1.1 "><p id="dns_qs_0001__p117774407505">Reverse resolution</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="40.59405940594059%" headers="mcps1.3.2.3.2.4.1.2 "><p id="dns_qs_0001__p157771840155010">Obtain public domain names based on IP addresses. PTR records are mainly used to build email servers.</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="37.62376237623762%" headers="mcps1.3.2.3.2.4.1.3 "><p id="dns_qs_0001__p157771840105017"><a href="en-us_topic_0040322596.html">Configuring a PTR Record</a></p>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
</tbody>
|
||||||
|
</table>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="dns_qs_0005.html">Getting Started</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
17
docs/dns/umn/dns_qs_0005.html
Normal file
17
docs/dns/umn/dns_qs_0005.html
Normal file
@ -0,0 +1,17 @@
|
|||||||
|
<a name="dns_qs_0005"></a><a name="dns_qs_0005"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Getting Started</h1>
|
||||||
|
<div id="body1471073508374"></div>
|
||||||
|
<div>
|
||||||
|
<ul class="ullinks">
|
||||||
|
<li class="ulchildlink"><strong><a href="dns_qs_0001.html">Quick Start</a></strong><br>
|
||||||
|
</li>
|
||||||
|
<li class="ulchildlink"><strong><a href="en-us_topic_0035467699.html">Routing Internet Traffic to a Website</a></strong><br>
|
||||||
|
</li>
|
||||||
|
<li class="ulchildlink"><strong><a href="dns_qs_0006.html">Configuring a Private Zone</a></strong><br>
|
||||||
|
</li>
|
||||||
|
<li class="ulchildlink"><strong><a href="en-us_topic_0040322596.html">Configuring a PTR Record</a></strong><br>
|
||||||
|
</li>
|
||||||
|
</ul>
|
||||||
|
</div>
|
||||||
|
|
55
docs/dns/umn/dns_qs_0006.html
Normal file
55
docs/dns/umn/dns_qs_0006.html
Normal file
@ -0,0 +1,55 @@
|
|||||||
|
<a name="dns_qs_0006"></a><a name="dns_qs_0006"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Configuring a Private Zone</h1>
|
||||||
|
<div id="body1493135545672"><div class="section" id="dns_qs_0006__section788725015149"><h4 class="sectiontitle"><strong id="dns_qs_0006__b842352706173019">Scenarios</strong></h4><p id="dns_qs_0006__p118115521312">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.</p>
|
||||||
|
<p id="dns_qs_0006__p98631353181614">You can create any private zones for domain names that are unique within VPCs. You do not need to register the domain names.</p>
|
||||||
|
<p id="dns_qs_0006__p19364144289">This section describes how to configure a private zone for a private domain name and add an A record set.</p>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="dns_qs_0006__section6577675115583"><h4 class="sectiontitle"><strong id="dns_qs_0006__b842352706102921">Prerequisites</strong></h4><p id="dns_qs_0006__p520715385501">You have created an ECS and obtained its VPC name and private IP address.</p>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="dns_qs_0006__section1246892417214"><h4 class="sectiontitle">Process</h4><p id="dns_qs_0006__p468645813171"><a href="#dns_qs_0006__f28bbf91c2c3e4b9c875c6375167fc7b1">Figure 1</a> shows the process for configuring a private zone for a domain name.</p>
|
||||||
|
<div class="fignone" id="dns_qs_0006__f28bbf91c2c3e4b9c875c6375167fc7b1"><a name="dns_qs_0006__f28bbf91c2c3e4b9c875c6375167fc7b1"></a><a name="f28bbf91c2c3e4b9c875c6375167fc7b1"></a><span class="figcap"><b>Figure 1 </b>Process for configuring a private zone</span><br><span><img id="dns_qs_0006__image147331733151415" src="en-us_image_0202562548.png" title="Click to enlarge" class="imgResize"></span></div>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="dns_qs_0006__section6593003511349"><h4 class="sectiontitle">Create a Private Zone</h4><p id="dns_qs_0006__p1381989515">Create a private zone to allow access to your ECS using a private domain name.</p>
|
||||||
|
<ol id="dns_qs_0006__ol5302846714436"><li id="dns_qs_0006__en-us_topic_0035467699_li52833639155823">Log in to the management console.</li><li id="dns_qs_0006__en-us_topic_0035467699_li52641116155830">In the service list, choose <strong id="dns_qs_0006__en-us_topic_0035467699_b253764512375">Network</strong> > <strong id="dns_qs_0006__en-us_topic_0035467699_b561505711379">Domain Name Service</strong>.<p id="dns_qs_0006__en-us_topic_0035467699_en-us_topic_0035467699_p179595731633">The DNS console is displayed.</p>
|
||||||
|
</li><li id="dns_qs_0006__en-us_topic_0035467699_li1829314716351">In the navigation pane, choose <strong id="dns_qs_0006__b842352706202035">Private Zones</strong>.<p id="dns_qs_0006__en-us_topic_0035467699_p5173372716550">The <strong id="dns_qs_0006__b84235270618511">Private Zones</strong> page is displayed.</p>
|
||||||
|
</li><li id="dns_qs_0006__li125970120613">Click <span><img id="dns_qs_0006__image18511144023210" src="en-us_image_0148391090.png"></span> in the upper left corner and select the desired region and project.</li><li id="dns_qs_0006__li39503211319">Click <strong id="dns_qs_0006__b2859926485">Create Private Zone</strong>.</li><li id="dns_qs_0006__li1763585517362">Set <strong id="dns_qs_0006__b15744439132814">Name</strong> to <strong id="dns_qs_0006__b1149614283494">example.com</strong> and select the VPC where the ECS resides.<p id="dns_qs_0006__p820095615204">For details about more parameters, see <a href="en-us_topic_0057773658.html">Creating a Private Zone</a>.</p>
|
||||||
|
<div class="fignone" id="dns_qs_0006__fig176111710101018"><span class="figcap"><b>Figure 2 </b>Creating a private zone</span><br><span><img id="dns_qs_0006__image1222672318302" src="en-us_image_0000001124782805.png" title="Click to enlarge" class="imgResize"></span></div>
|
||||||
|
</li><li id="dns_qs_0006__li18372181212416">Click <strong id="dns_qs_0006__b0901517425">OK</strong>.</li><li id="dns_qs_0006__li130822544415">Switch back to the <strong id="dns_qs_0006__b837864204816">Private Zones</strong> page.<div class="p" id="dns_qs_0006__p11462172884414">View the created private zone.<div class="note" id="dns_qs_0006__note5649867419844"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="dns_qs_0006__p3872602219844">Click the zone name to view zone details. You can view SOA and NS record sets automatically generated by the system.</p>
|
||||||
|
<ul id="dns_qs_0006__ul37136635191010"><li id="dns_qs_0006__li27116903191010">The SOA record set defines the DNS server that is the authoritative information source for a particular domain name.</li><li id="dns_qs_0006__li8403156191010">The NS record set defines authoritative DNS servers for a zone.</li></ul>
|
||||||
|
</div></div>
|
||||||
|
</div>
|
||||||
|
</li></ol>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="dns_qs_0006__section14281725102412"><h4 class="sectiontitle">Add an A Record Set</h4><p id="dns_qs_0006__p741113403522">To access the ECS using example.com, add an A record set.</p>
|
||||||
|
<ol id="dns_qs_0006__ol16291135712514"><li id="dns_qs_0006__li229345716251">On the <strong id="dns_qs_0006__b29048444105549">Private Zones</strong> page, click the name of the private zone you created.<p id="dns_qs_0006__p1529514576258">The <strong id="dns_qs_0006__b6750141021820">Record Sets</strong> page is displayed.</p>
|
||||||
|
</li><li id="dns_qs_0006__li1696545145419">Click <strong id="dns_qs_0006__b18561214622">Add Record Set</strong>.</li><li id="dns_qs_0006__li6259141915436">Set the parameters as follows:<ul id="dns_qs_0006__ul1123017254491"><li id="dns_qs_0006__li12301725184918"><strong id="dns_qs_0006__b1142180144014">Name</strong>: Leave this parameter blank. The system automatically considers example.com to be the name, and requests are routed to example.com.</li><li id="dns_qs_0006__li1976965085516"><strong id="dns_qs_0006__b633934521617">Type</strong>: Set it to <strong id="dns_qs_0006__b19341104561616">A – Map domains to IPv4 addresses</strong>.</li><li id="dns_qs_0006__li16230122510491"><strong id="dns_qs_0006__b122713172719">Value</strong>: Enter the private IP address of the ECS.</li></ul>
|
||||||
|
<p id="dns_qs_0006__p1491217102338">Retain the default values for other parameters. For details, see <a href="dns_usermanual_0007.html">Adding an A Record Set</a>.</p>
|
||||||
|
<div class="fignone" id="dns_qs_0006__fig1896951915561"><span class="figcap"><b>Figure 3 </b>Add Record Set</span><br><span><img id="dns_qs_0006__image4809354133119" src="en-us_image_0000001124468095.png" title="Click to enlarge" class="imgResize"></span></div>
|
||||||
|
</li><li id="dns_qs_0006__li992141319437">Click <strong id="dns_qs_0006__b115291626204918">OK</strong>.</li><li id="dns_qs_0006__li443565732515">Switch back to the <strong id="dns_qs_0006__b551763234215">Record Sets</strong> page.<p id="dns_qs_0006__p677473481417">View the added record set in the record set list of the zone and ensure that the status of the record set is <strong id="dns_qs_0006__b73956595510">Normal</strong>.</p>
|
||||||
|
</li></ol>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="dns_qs_0006__section117401416132619"><h4 class="sectiontitle">(Optional) Configure DNS Servers for the VPC Subnet</h4><p id="dns_qs_0006__p47271451182614">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. </p>
|
||||||
|
<p id="dns_qs_0006__p1895754752812"><strong id="dns_qs_0006__b842352706164935">Query the private DNS servers provided by the DNS service</strong></p>
|
||||||
|
<ol id="dns_qs_0006__ol11732135112611"><li id="dns_qs_0006__li1173325182612">Log in to the management console.</li><li id="dns_qs_0006__li2073735111262">In the service list, choose <strong id="dns_qs_0006__dns_qs_0006_en-us_topic_0035467699_b253764512375">Network</strong> > <strong id="dns_qs_0006__dns_qs_0006_en-us_topic_0035467699_b561505711379">Domain Name Service</strong>.<p id="dns_qs_0006__dns_qs_0006_en-us_topic_0035467699_en-us_topic_0035467699_p179595731633">The DNS console is displayed.</p>
|
||||||
|
</li><li id="dns_qs_0006__li6741145192613">In the navigation pane, choose <strong id="dns_qs_0006__dns_qs_0006_b842352706202035">Private Zones</strong>.<p id="dns_qs_0006__dns_qs_0006_en-us_topic_0035467699_p5173372716550">The <strong id="dns_qs_0006__dns_qs_0006_b84235270618511">Private Zones</strong> page is displayed.</p>
|
||||||
|
</li><li id="dns_qs_0006__li18750155113266">Click <span><img id="dns_qs_0006__dns_qs_0006_image18511144023210" src="en-us_image_0148391090.png"></span> in the upper left corner and select the desired region and project.</li><li id="dns_qs_0006__li27556512264">In the private zone list, click the name of the zone and view the DNS servers.</li></ol>
|
||||||
|
<p id="dns_qs_0006__p86191541143512"><strong id="dns_qs_0006__b842352706165453">Change the DNS servers</strong></p>
|
||||||
|
<ol id="dns_qs_0006__ol15152133719400"><li id="dns_qs_0006__li04322551713">Go to the private zone list.</li><li id="dns_qs_0006__li215293744012">Click the VPC name under <strong id="dns_qs_0006__b842352706165723">Associated VPC</strong>.<p id="dns_qs_0006__p987210402285">On the VPC console, change the DNS servers of the VPC subnet.</p>
|
||||||
|
<p id="dns_qs_0006__p12143712211">For details, see <a href="https://docs.otc.t-systems.com/usermanual/vpc/vpc_vpc_0001.html" target="_blank" rel="noopener noreferrer">Modifying a Subnet</a>.</p>
|
||||||
|
</li></ol>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="dns_qs_0005.html">Getting Started</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
||||||
|
|
||||||
|
<script language="JavaScript">
|
||||||
|
<!--
|
||||||
|
image_size('.imgResize');
|
||||||
|
var msg_imageMax = "view original image";
|
||||||
|
var msg_imageClose = "close";
|
||||||
|
//--></script>
|
19
docs/dns/umn/dns_usermanual_0002.html
Normal file
19
docs/dns/umn/dns_usermanual_0002.html
Normal file
@ -0,0 +1,19 @@
|
|||||||
|
<a name="dns_usermanual_0002"></a><a name="dns_usermanual_0002"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Private Zone</h1>
|
||||||
|
<div id="body1545706717447"></div>
|
||||||
|
<div>
|
||||||
|
<ul class="ullinks">
|
||||||
|
<li class="ulchildlink"><strong><a href="dns_usermanual_0032.html">Overview</a></strong><br>
|
||||||
|
</li>
|
||||||
|
<li class="ulchildlink"><strong><a href="en-us_topic_0057773658.html">Creating a Private Zone</a></strong><br>
|
||||||
|
</li>
|
||||||
|
<li class="ulchildlink"><strong><a href="dns_usermanual_0033.html">Managing Private Zones</a></strong><br>
|
||||||
|
</li>
|
||||||
|
<li class="ulchildlink"><strong><a href="dns_usermanual_0003.html">Associating a VPC with a Private Zone</a></strong><br>
|
||||||
|
</li>
|
||||||
|
<li class="ulchildlink"><strong><a href="dns_usermanual_0004.html">Disassociating a VPC from a Private Zone</a></strong><br>
|
||||||
|
</li>
|
||||||
|
</ul>
|
||||||
|
</div>
|
||||||
|
|
28
docs/dns/umn/dns_usermanual_0003.html
Normal file
28
docs/dns/umn/dns_usermanual_0003.html
Normal file
@ -0,0 +1,28 @@
|
|||||||
|
<a name="dns_usermanual_0003"></a><a name="dns_usermanual_0003"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Associating a VPC with a Private Zone</h1>
|
||||||
|
<div id="body1546947844831"><div class="section" id="dns_usermanual_0003__section671410719483"><h4 class="sectiontitle"><strong id="dns_usermanual_0003__b254774511102">Scenarios</strong></h4><p id="dns_usermanual_0003__p1143111310482">Associate a VPC with a private zone so that the private domain name can work in this VPC.</p>
|
||||||
|
<div class="note" id="dns_usermanual_0003__note78221813184415"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="dns_usermanual_0003__en-us_topic_0057773658_p08151612103717">This VPC must be the same as the VPC where the servers are deployed. Otherwise, the domain name cannot be resolved.</p>
|
||||||
|
</div></div>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="dns_usermanual_0003__section117735276489"><h4 class="sectiontitle"><strong id="dns_usermanual_0003__b524815212010">Procedure</strong></h4><ol id="dns_usermanual_0003__ol11732135112611"><li id="dns_usermanual_0003__li1173325182612">Log in to the management console.</li><li id="dns_usermanual_0003__li2073735111262">In the service list, choose <strong id="dns_usermanual_0003__dns_qs_0006_en-us_topic_0035467699_b253764512375">Network</strong> > <strong id="dns_usermanual_0003__dns_qs_0006_en-us_topic_0035467699_b561505711379">Domain Name Service</strong>.<p id="dns_usermanual_0003__dns_qs_0006_en-us_topic_0035467699_en-us_topic_0035467699_p179595731633">The DNS console is displayed.</p>
|
||||||
|
</li><li id="dns_usermanual_0003__li6741145192613">In the navigation pane, choose <strong id="dns_usermanual_0003__dns_qs_0006_b842352706202035">Private Zones</strong>.<p id="dns_usermanual_0003__dns_qs_0006_en-us_topic_0035467699_p5173372716550">The <strong id="dns_usermanual_0003__dns_qs_0006_b84235270618511">Private Zones</strong> page is displayed.</p>
|
||||||
|
</li><li id="dns_usermanual_0003__li18750155113266">Click <span><img id="dns_usermanual_0003__dns_qs_0006_image18511144023210" src="en-us_image_0148391090.png"></span> in the upper left corner and select the desired region and project.</li></ol><ol start="5" id="dns_usermanual_0003__ol4752066601850"><li id="dns_usermanual_0003__li958438501921">Locate the private zone with which you want to associate the VPC and click <strong id="dns_usermanual_0003__b842352706191245">Associate VPC</strong> under <strong id="dns_usermanual_0003__b842352706191256">Operation</strong>.</li><li id="dns_usermanual_0003__li2715433302435">Select the VPC you want to associate.<div class="p" id="dns_usermanual_0003__p1445873411412"><a name="dns_usermanual_0003__li2715433302435"></a><a name="li2715433302435"></a>If no VPCs are available, create one on the VPC console and then associate the private zone with it.<div class="fignone" id="dns_usermanual_0003__fig51318324412"><span class="figcap"><b>Figure 1 </b>Associating a VPC</span><br><span><img id="dns_usermanual_0003__image113132164120" src="en-us_image_0198815181.png" title="Click to enlarge" class="imgResize"></span></div>
|
||||||
|
</div>
|
||||||
|
</li><li id="dns_usermanual_0003__li3069743802550">Click <strong id="dns_usermanual_0003__b842352706163651">OK</strong>.<p id="dns_usermanual_0003__p8682102032220">The VPC is displayed under <strong id="dns_usermanual_0003__b7207111124413">Associated VPC</strong>.</p>
|
||||||
|
</li></ol>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="dns_usermanual_0002.html">Private Zone</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
||||||
|
|
||||||
|
<script language="JavaScript">
|
||||||
|
<!--
|
||||||
|
image_size('.imgResize');
|
||||||
|
var msg_imageMax = "view original image";
|
||||||
|
var msg_imageClose = "close";
|
||||||
|
//--></script>
|
27
docs/dns/umn/dns_usermanual_0004.html
Normal file
27
docs/dns/umn/dns_usermanual_0004.html
Normal file
@ -0,0 +1,27 @@
|
|||||||
|
<a name="dns_usermanual_0004"></a><a name="dns_usermanual_0004"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Disassociating a VPC from a Private Zone</h1>
|
||||||
|
<div id="body1546947852996"><div class="section" id="dns_usermanual_0004__section901515124915"><h4 class="sectiontitle"><strong id="dns_usermanual_0004__b17491161812195">Scenarios</strong></h4><p id="dns_usermanual_0004__p3859286302626">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.</p>
|
||||||
|
<div class="note" id="dns_usermanual_0004__note947632017302"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="dns_usermanual_0004__p8477182012307">If you do not intend to use private domain names, delete the private zone.</p>
|
||||||
|
</div></div>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="dns_usermanual_0004__section394212924913"><h4 class="sectiontitle"><strong id="dns_usermanual_0004__b46101210192012">Procedure</strong></h4><ol id="dns_usermanual_0004__ol11732135112611"><li id="dns_usermanual_0004__li1173325182612">Log in to the management console.</li><li id="dns_usermanual_0004__li2073735111262">In the service list, choose <strong id="dns_usermanual_0004__dns_qs_0006_en-us_topic_0035467699_b253764512375">Network</strong> > <strong id="dns_usermanual_0004__dns_qs_0006_en-us_topic_0035467699_b561505711379">Domain Name Service</strong>.<p id="dns_usermanual_0004__dns_qs_0006_en-us_topic_0035467699_en-us_topic_0035467699_p179595731633">The DNS console is displayed.</p>
|
||||||
|
</li><li id="dns_usermanual_0004__li6741145192613">In the navigation pane, choose <strong id="dns_usermanual_0004__dns_qs_0006_b842352706202035">Private Zones</strong>.<p id="dns_usermanual_0004__dns_qs_0006_en-us_topic_0035467699_p5173372716550">The <strong id="dns_usermanual_0004__dns_qs_0006_b84235270618511">Private Zones</strong> page is displayed.</p>
|
||||||
|
</li><li id="dns_usermanual_0004__li18750155113266">Click <span><img id="dns_usermanual_0004__dns_qs_0006_image18511144023210" src="en-us_image_0148391090.png"></span> in the upper left corner and select the desired region and project.</li></ol><ol start="5" id="dns_usermanual_0004__ol14330980276"><li id="dns_usermanual_0004__li1219894402714">Locate the private zone from which a VPC is to be disassociated, select the VPC to be disassociated under <strong id="dns_usermanual_0004__b67202323401">Associated VPC</strong>, and click <span><img id="dns_usermanual_0004__image189481049122317" src="en-us_image_0210876854.png"></span> on the right of the VPC.<div class="fignone" id="dns_usermanual_0004__fig1823514684718"><span class="figcap"><b>Figure 1 </b>Associated VPC</span><br><span><img id="dns_usermanual_0004__image172350664715" src="en-us_image_0165052501.png" title="Click to enlarge" class="imgResize"></span></div>
|
||||||
|
</li><li id="dns_usermanual_0004__li11948951359">In the <strong id="dns_usermanual_0004__b84235270611454">Disassociate VPC</strong> dialog box, click <strong id="dns_usermanual_0004__b8423527061153">Yes</strong>.<div class="fignone" id="dns_usermanual_0004__fig179021444154919"><span class="figcap"><b>Figure 2 </b>Disassociating a VPC</span><br><span><img id="dns_usermanual_0004__image209011144154918" src="en-us_image_0165052502.png" title="Click to enlarge" class="imgResize"></span></div>
|
||||||
|
</li></ol>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="dns_usermanual_0002.html">Private Zone</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
||||||
|
|
||||||
|
<script language="JavaScript">
|
||||||
|
<!--
|
||||||
|
image_size('.imgResize');
|
||||||
|
var msg_imageMax = "view original image";
|
||||||
|
var msg_imageClose = "close";
|
||||||
|
//--></script>
|
31
docs/dns/umn/dns_usermanual_0006.html
Normal file
31
docs/dns/umn/dns_usermanual_0006.html
Normal file
@ -0,0 +1,31 @@
|
|||||||
|
<a name="dns_usermanual_0006"></a><a name="dns_usermanual_0006"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Adding Record Sets</h1>
|
||||||
|
<div id="body1548760313419"></div>
|
||||||
|
<div>
|
||||||
|
<ul class="ullinks">
|
||||||
|
<li class="ulchildlink"><strong><a href="dns_usermanual_0007.html">Adding an A Record Set</a></strong><br>
|
||||||
|
</li>
|
||||||
|
<li class="ulchildlink"><strong><a href="dns_usermanual_0008.html">Adding an AAAA Record Set</a></strong><br>
|
||||||
|
</li>
|
||||||
|
<li class="ulchildlink"><strong><a href="dns_usermanual_0009.html">Adding an NS Record Set</a></strong><br>
|
||||||
|
</li>
|
||||||
|
<li class="ulchildlink"><strong><a href="dns_usermanual_0010.html">Adding a CNAME Record Set</a></strong><br>
|
||||||
|
</li>
|
||||||
|
<li class="ulchildlink"><strong><a href="dns_usermanual_0011.html">Adding an MX Record Set</a></strong><br>
|
||||||
|
</li>
|
||||||
|
<li class="ulchildlink"><strong><a href="dns_usermanual_0012.html">Adding a TXT Record Set</a></strong><br>
|
||||||
|
</li>
|
||||||
|
<li class="ulchildlink"><strong><a href="dns_usermanual_0013.html">Adding an SRV Record Set</a></strong><br>
|
||||||
|
</li>
|
||||||
|
<li class="ulchildlink"><strong><a href="dns_usermanual_0014.html">Adding a CAA Record Set</a></strong><br>
|
||||||
|
</li>
|
||||||
|
<li class="ulchildlink"><strong><a href="dns_usermanual_0015.html">Adding a PTR Record</a></strong><br>
|
||||||
|
</li>
|
||||||
|
</ul>
|
||||||
|
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="dns_usermanual_0034.html">Record Set</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
115
docs/dns/umn/dns_usermanual_0007.html
Normal file
115
docs/dns/umn/dns_usermanual_0007.html
Normal file
File diff suppressed because it is too large
Load Diff
112
docs/dns/umn/dns_usermanual_0008.html
Normal file
112
docs/dns/umn/dns_usermanual_0008.html
Normal file
File diff suppressed because it is too large
Load Diff
114
docs/dns/umn/dns_usermanual_0009.html
Normal file
114
docs/dns/umn/dns_usermanual_0009.html
Normal file
File diff suppressed because it is too large
Load Diff
111
docs/dns/umn/dns_usermanual_0010.html
Normal file
111
docs/dns/umn/dns_usermanual_0010.html
Normal file
File diff suppressed because it is too large
Load Diff
115
docs/dns/umn/dns_usermanual_0011.html
Normal file
115
docs/dns/umn/dns_usermanual_0011.html
Normal file
File diff suppressed because it is too large
Load Diff
118
docs/dns/umn/dns_usermanual_0012.html
Normal file
118
docs/dns/umn/dns_usermanual_0012.html
Normal file
File diff suppressed because it is too large
Load Diff
115
docs/dns/umn/dns_usermanual_0013.html
Normal file
115
docs/dns/umn/dns_usermanual_0013.html
Normal file
File diff suppressed because it is too large
Load Diff
120
docs/dns/umn/dns_usermanual_0014.html
Normal file
120
docs/dns/umn/dns_usermanual_0014.html
Normal file
File diff suppressed because it is too large
Load Diff
113
docs/dns/umn/dns_usermanual_0015.html
Normal file
113
docs/dns/umn/dns_usermanual_0015.html
Normal file
File diff suppressed because it is too large
Load Diff
19
docs/dns/umn/dns_usermanual_0016.html
Normal file
19
docs/dns/umn/dns_usermanual_0016.html
Normal file
@ -0,0 +1,19 @@
|
|||||||
|
<a name="dns_usermanual_0016"></a><a name="dns_usermanual_0016"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Quota Adjustment</h1>
|
||||||
|
<div id="body1549867054365"><div class="section" id="dns_usermanual_0016__section102291042164212"><h4 class="sectiontitle">What Is Quota?</h4><p id="dns_usermanual_0016__p1415804616467">Quotas are enforced for service resources on the platform to prevent unforeseen spikes in resource usage. Quotas can limit the number and capacity of resources available to users, for example, the maximum number of zones, PTR records, or record sets that you can create.</p>
|
||||||
|
<p id="dns_usermanual_0016__p547171214515">If the existing resource quota cannot meet your service requirements, you can apply for a higher quota.</p>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="dns_usermanual_0016__section07760615438"><h4 class="sectiontitle">How Do I View My Quotas?</h4><ol id="dns_usermanual_0016__en-us_topic_0040259342_ol1222775692215"><li id="dns_usermanual_0016__en-us_topic_0040259342_li5648642910048">Log in to the management console.</li><li id="dns_usermanual_0016__en-us_topic_0040259342_li464234814566">Click <span><img id="dns_usermanual_0016__en-us_topic_0040259342_en-us_topic_0014250631_en-us_topic_0014250631_image1733511156361" src="en-us_image_0275513364.png"></span> in the upper left corner and select the desired region and project.</li><li id="dns_usermanual_0016__en-us_topic_0040259342_li3861581410048">In the upper right corner of the page, click <span><img id="dns_usermanual_0016__en-us_topic_0040259342_image99377514309" src="en-us_image_0152727234.png"></span>.<p id="dns_usermanual_0016__en-us_topic_0040259342_p1748884433119">The <strong id="dns_usermanual_0016__en-us_topic_0040259342_b695801964614">Service Quota</strong> page is displayed.</p>
|
||||||
|
</li><li id="dns_usermanual_0016__en-us_topic_0040259342_li1579070183211">View the used and total quota of each type of resources on the displayed page.<p id="dns_usermanual_0016__en-us_topic_0040259342_p97891720193417"><a name="dns_usermanual_0016__en-us_topic_0040259342_li1579070183211"></a><a name="en-us_topic_0040259342_li1579070183211"></a>If a quota cannot meet service requirements, apply for a higher quota.</p>
|
||||||
|
</li></ol>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="dns_usermanual_0016__section1233262919526"><h4 class="sectiontitle">How Do I Apply for a Higher Quota?</h4><p id="dns_usermanual_0016__en-us_topic_0040259342_p133802054172617">The system does not support online quota adjustment. If you need to adjust a quota, call the hotline or send an email to the customer service mailbox. Customer service personnel will timely process your request for quota adjustment and inform you of the real-time progress by making a call or sending an email.</p>
|
||||||
|
<p id="dns_usermanual_0016__en-us_topic_0040259342_p13745144852611">Before dialing the hotline number or sending an email, make sure that the following information has been obtained:</p>
|
||||||
|
<ul id="dns_usermanual_0016__en-us_topic_0040259342_ul37351029162712"><li id="dns_usermanual_0016__en-us_topic_0040259342_li12735132932714">Domain name, project name, and project ID, which can be obtained by performing the following operations:<p id="dns_usermanual_0016__en-us_topic_0040259342_p1973542918275"><a name="dns_usermanual_0016__en-us_topic_0040259342_li12735132932714"></a><a name="en-us_topic_0040259342_li12735132932714"></a>Log in to the management console using the cloud account, click the username in the upper right corner, select <strong id="dns_usermanual_0016__en-us_topic_0040259342_b592883891">My Credentials</strong> from the drop-down list, and obtain the domain name, project name, and project ID on the <strong id="dns_usermanual_0016__en-us_topic_0040259342_b1320563021">My Credentials</strong> page.</p>
|
||||||
|
</li><li id="dns_usermanual_0016__en-us_topic_0040259342_li13735182917270">Quota information, which includes:<ul id="dns_usermanual_0016__en-us_topic_0040259342_ul6735102912273"><li id="dns_usermanual_0016__en-us_topic_0040259342_li1073516296277">Service name</li><li id="dns_usermanual_0016__en-us_topic_0040259342_li6735152972712">Quota type</li><li id="dns_usermanual_0016__en-us_topic_0040259342_li773592992718">Required quota</li></ul>
|
||||||
|
</li></ul>
|
||||||
|
<p id="dns_usermanual_0016__en-us_topic_0040259342_p126761744182712"><a href="https://docs.otc.t-systems.com/en-us/public/learnmore.html" target="_blank" rel="noopener noreferrer">Learn how to obtain the service hotline and email address.</a></p>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
38
docs/dns/umn/dns_usermanual_0030.html
Normal file
38
docs/dns/umn/dns_usermanual_0030.html
Normal file
@ -0,0 +1,38 @@
|
|||||||
|
<a name="dns_usermanual_0030"></a><a name="dns_usermanual_0030"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Overview</h1>
|
||||||
|
<div id="body1570616052156"><p id="dns_usermanual_0030__p26101614202315">A public zone provides information to translate a domain name and its subdomains into IP addresses required for network communications on the Internet. Visitors can access your website by entering a domain name in the address box of a browser. DNS provides public domain names resolution. To resolve public domain names, you must host the registered domain names on the DNS service.</p>
|
||||||
|
<p id="dns_usermanual_0030__p146811920293">This chapter describes how to create and manage public zones.</p>
|
||||||
|
|
||||||
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="dns_usermanual_0030__table977612405507" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Public zone operations</caption><thead align="left"><tr id="dns_usermanual_0030__row87771409504"><th align="left" class="cellrowborder" valign="top" width="18.13181318131813%" id="mcps1.3.3.2.4.1.1"><p id="dns_usermanual_0030__p15777740175016">Operation</p>
|
||||||
|
</th>
|
||||||
|
<th align="left" class="cellrowborder" valign="top" width="37.32373237323732%" id="mcps1.3.3.2.4.1.2"><p id="dns_usermanual_0030__p47771140115015">Scenario</p>
|
||||||
|
</th>
|
||||||
|
<th align="left" class="cellrowborder" valign="top" width="44.54445444544455%" id="mcps1.3.3.2.4.1.3"><p id="dns_usermanual_0030__p11777174055015">Remarks</p>
|
||||||
|
</th>
|
||||||
|
</tr>
|
||||||
|
</thead>
|
||||||
|
<tbody><tr id="dns_usermanual_0030__row3777840175020"><td class="cellrowborder" valign="top" width="18.13181318131813%" headers="mcps1.3.3.2.4.1.1 "><p id="dns_usermanual_0030__p167777403501"><a href="en-us_topic_0035467702.html">Creating a Public Zone</a></p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="37.32373237323732%" headers="mcps1.3.3.2.4.1.2 "><p id="dns_usermanual_0030__p777716406501">Create a zone for your domain name.</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="44.54445444544455%" headers="mcps1.3.3.2.4.1.3 "><ul id="dns_usermanual_0030__ul446519315616"><li id="dns_usermanual_0030__li1686818375018">Public zones are global resources. You do not need to set a region or project.</li><li id="dns_usermanual_0030__li124657311462">Each user can add a maximum of 50 public zones.</li><li id="dns_usermanual_0030__li51110210711">The domain name can be a second-level domain name or one of its subdomains, for example, abc.example.com.</li></ul>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
<tr id="dns_usermanual_0030__row1577754016507"><td class="cellrowborder" valign="top" width="18.13181318131813%" headers="mcps1.3.3.2.4.1.1 "><p id="dns_usermanual_0030__p4777640105010"><a href="dns_usermanual_0031.html">Managing Public Zones</a></p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="37.32373237323732%" headers="mcps1.3.3.2.4.1.2 "><p id="dns_usermanual_0030__p3777134025015">Modify, delete, and view public zones.</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="44.54445444544455%" headers="mcps1.3.3.2.4.1.3 "><ul id="dns_usermanual_0030__ul18735122581518"><li id="dns_usermanual_0030__li47353256153">Once a public zone is created, its name cannot be modified.</li><li id="dns_usermanual_0030__li165411539169">After a public zone is deleted, all its record sets will also be deleted.</li></ul>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
</tbody>
|
||||||
|
</table>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_00352049771.html">Public Zone</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
32
docs/dns/umn/dns_usermanual_0031.html
Normal file
32
docs/dns/umn/dns_usermanual_0031.html
Normal file
@ -0,0 +1,32 @@
|
|||||||
|
<a name="dns_usermanual_0031"></a><a name="dns_usermanual_0031"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Managing Public Zones</h1>
|
||||||
|
<div id="body1570687817245"><div class="section" id="dns_usermanual_0031__section125317016203"><h4 class="sectiontitle"><strong id="dns_usermanual_0031__b191398438112">Scenarios</strong></h4><p id="dns_usermanual_0031__p4389381211647">You can view details of a public zone, modify a public zone, or delete a public zone.</p>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="dns_usermanual_0031__section15349122315204"><h4 class="sectiontitle">Modifying a Public Zone</h4><p id="dns_usermanual_0031__p5963715215821">Change the email address of the domain name administrator and description of the public zone.</p>
|
||||||
|
<div class="note" id="dns_usermanual_0031__note690345618481"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="dns_usermanual_0031__en-us_topic_0035467699_p3894942320387">For more information about the email address, see <a href="dns_faq_009.html">Why Was the Email Address Format Changed in the SOA Record?</a></p>
|
||||||
|
</div></div>
|
||||||
|
<ol id="dns_usermanual_0031__ol17644154320344"><li id="dns_usermanual_0031__li20644134343413">Log in to the management console.</li><li id="dns_usermanual_0031__li18644443113415">In the service list, choose <strong id="dns_usermanual_0031__en-us_topic_0035467699_b253764512375">Network</strong> > <strong id="dns_usermanual_0031__en-us_topic_0035467699_b561505711379">Domain Name Service</strong>.<p id="dns_usermanual_0031__en-us_topic_0035467699_en-us_topic_0035467699_p179595731633">The DNS console is displayed.</p>
|
||||||
|
</li><li id="dns_usermanual_0031__li56590911183934">In the navigation pane, choose <strong id="dns_usermanual_0031__en-us_topic_0035467699_b29951815195912">Public Zones</strong>.<p id="dns_usermanual_0031__en-us_topic_0035467699_en-us_topic_0035467699_p5173372716550">The <strong id="dns_usermanual_0031__en-us_topic_0035467699_b84235270618511">Public Zones</strong> page is displayed.</p>
|
||||||
|
</li></ol><ol start="4" id="dns_usermanual_0031__ol62939528215743"><li id="dns_usermanual_0031__li44636830215743">Locate the public zone you want to modify and click <strong id="dns_usermanual_0031__b842352706154223">Modify</strong> under <strong id="dns_usermanual_0031__b1022333411651">Operation</strong>.<p id="dns_usermanual_0031__p66187156215743">The <strong id="dns_usermanual_0031__b150010128313">Modify Public Zone</strong> dialog box is displayed.</p>
|
||||||
|
</li><li id="dns_usermanual_0031__li58813495215743">Change the email address or description of the zone as required.</li><li id="dns_usermanual_0031__li59559408215743">Click <strong id="dns_usermanual_0031__b842352706194656">OK</strong>.</li></ol>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="dns_usermanual_0031__section1756118128375"><h4 class="sectiontitle">Deleting a Public Zone</h4><p id="dns_usermanual_0031__p124381137145411">Delete a public zone when you no longer need it. After a public zone is deleted, the domain name and its subdomains cannot be resolved by the DNS service.</p>
|
||||||
|
<div class="notice" id="dns_usermanual_0031__note1143883711543"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="dns_usermanual_0031__p1043843719548">Before you delete a public zone, back up all record sets in the public zone.</p>
|
||||||
|
</div></div>
|
||||||
|
<ol id="dns_usermanual_0031__ol63221954193419"><li id="dns_usermanual_0031__li3322115419345">Log in to the management console.</li><li id="dns_usermanual_0031__li632285418347">In the service list, choose <strong id="dns_usermanual_0031__en-us_topic_0035467699_b253764512375_1">Network</strong> > <strong id="dns_usermanual_0031__en-us_topic_0035467699_b561505711379_1">Domain Name Service</strong>.<p id="dns_usermanual_0031__en-us_topic_0035467699_en-us_topic_0035467699_p179595731633_1">The DNS console is displayed.</p>
|
||||||
|
</li><li id="dns_usermanual_0031__li732285416348">In the navigation pane, choose <strong id="dns_usermanual_0031__en-us_topic_0035467699_b29951815195912_1">Public Zones</strong>.<p id="dns_usermanual_0031__en-us_topic_0035467699_en-us_topic_0035467699_p5173372716550_1">The <strong id="dns_usermanual_0031__en-us_topic_0035467699_b84235270618511_1">Public Zones</strong> page is displayed.</p>
|
||||||
|
</li></ol><ol start="4" id="dns_usermanual_0031__ol28672362105629"><li id="dns_usermanual_0031__li1460312111927">Locate the public zone you want to delete and click <strong id="dns_usermanual_0031__b16439851104316">Delete</strong> under <strong id="dns_usermanual_0031__b134695821">Operation</strong>.<p id="dns_usermanual_0031__p837216245010">The <strong id="dns_usermanual_0031__b1928517463413">Delete Public Zone</strong> dialog box is displayed.</p>
|
||||||
|
</li><li id="dns_usermanual_0031__li12797857111032">Click <strong id="dns_usermanual_0031__b550520531440">Yes</strong>.</li></ol>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="dns_usermanual_0031__section46971009387"><h4 class="sectiontitle">Viewing Details About a Public Zone</h4><p id="dns_usermanual_0031__p898152961917">View details about a public zone, such as zone ID, operation time, tag, and TTL, on the <strong id="dns_usermanual_0031__b186221241164014">Public Zones</strong> page.</p>
|
||||||
|
<ol id="dns_usermanual_0031__ol17542104182445"><li id="dns_usermanual_0031__li21168153182445">Log in to the management console.</li><li id="dns_usermanual_0031__li16568687183919">In the service list, choose <strong id="dns_usermanual_0031__en-us_topic_0035467699_b253764512375_2">Network</strong> > <strong id="dns_usermanual_0031__en-us_topic_0035467699_b561505711379_2">Domain Name Service</strong>.<p id="dns_usermanual_0031__en-us_topic_0035467699_en-us_topic_0035467699_p179595731633_2">The DNS console is displayed.</p>
|
||||||
|
</li></ol><ol start="3" id="dns_usermanual_0031__ol3095230910256"><li id="dns_usermanual_0031__li541508110260">On the <strong id="dns_usermanual_0031__b842352706184513">Dashboard</strong> page, click <strong id="dns_usermanual_0031__b5846185811453">Public Zones</strong> under <strong id="dns_usermanual_0031__b4435101711057">My Resources</strong>.</li><li id="dns_usermanual_0031__li24215569103150">Locate the public zone you want to view and click <span><img id="dns_usermanual_0031__image177321361141" src="en-us_image_0210877115.png"></span> before the zone name to view its details.</li></ol>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="en-us_topic_00352049771.html">Public Zone</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
55
docs/dns/umn/dns_usermanual_0032.html
Normal file
55
docs/dns/umn/dns_usermanual_0032.html
Normal file
@ -0,0 +1,55 @@
|
|||||||
|
<a name="dns_usermanual_0032"></a><a name="dns_usermanual_0032"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Overview</h1>
|
||||||
|
<div id="body1571390688924"><p id="dns_usermanual_0032__p66701421161812">Private zones provide configurations for private domain names that are only applicable within VPCs, and they map private domain names to private IP addresses and resolve domain names within VPCs.</p>
|
||||||
|
<ul id="dns_usermanual_0032__ul1820812192316"><li id="dns_usermanual_0032__li152080262317">You can create any domain names without registering them.</li><li id="dns_usermanual_0032__li1458119162315">One private zone can be associated with multiple VPCs, and domain names are valid only in VPCs.</li></ul>
|
||||||
|
<p id="dns_usermanual_0032__p26101614202315">To use private domain names, you must first create a private zone and associate VPCs with it.</p>
|
||||||
|
<p id="dns_usermanual_0032__p146811920293">This chapter describes how to create and manage private zones.</p>
|
||||||
|
|
||||||
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="dns_usermanual_0032__table977612405507" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Private zone operations</caption><thead align="left"><tr id="dns_usermanual_0032__row87771409504"><th align="left" class="cellrowborder" valign="top" width="18%" id="mcps1.3.5.2.4.1.1"><p id="dns_usermanual_0032__p15777740175016"><strong id="dns_usermanual_0032__b69322716212">Operation</strong></p>
|
||||||
|
</th>
|
||||||
|
<th align="left" class="cellrowborder" valign="top" width="27%" id="mcps1.3.5.2.4.1.2"><p id="dns_usermanual_0032__p47771140115015">Description</p>
|
||||||
|
</th>
|
||||||
|
<th align="left" class="cellrowborder" valign="top" width="55.00000000000001%" id="mcps1.3.5.2.4.1.3"><p id="dns_usermanual_0032__p11777174055015">Constraint</p>
|
||||||
|
</th>
|
||||||
|
</tr>
|
||||||
|
</thead>
|
||||||
|
<tbody><tr id="dns_usermanual_0032__row3777840175020"><td class="cellrowborder" valign="top" width="18%" headers="mcps1.3.5.2.4.1.1 "><p id="dns_usermanual_0032__p167777403501"><a href="en-us_topic_0057773658.html">Creating a Private Zone</a></p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="27%" headers="mcps1.3.5.2.4.1.2 "><p id="dns_usermanual_0032__p777716406501">Create a zone for your domain name.</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="55.00000000000001%" headers="mcps1.3.5.2.4.1.3 "><ul id="dns_usermanual_0032__ul446519315616"><li id="dns_usermanual_0032__li2327101013512">Private zones are project-level resources. When you create a private zone, select a region and project.</li><li id="dns_usermanual_0032__li124657311462">Each account can create a maximum of 50 private zones.</li><li id="dns_usermanual_0032__li490484114474">Private domain names must meet the following requirements:<ul id="dns_usermanual_0032__ul14785719184814"><li id="dns_usermanual_0032__li84851864814">Domain name labels are separated by dot (.), and each label does not exceed 63 characters.</li><li id="dns_usermanual_0032__li281471764811">A domain name label can contain letters, digits, and hyphens (-) and cannot start or end with a hyphen.</li><li id="dns_usermanual_0032__li1081783010496">The total length of a domain name cannot exceed 254 characters.</li></ul>
|
||||||
|
</li></ul>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
<tr id="dns_usermanual_0032__row1577754016507"><td class="cellrowborder" valign="top" width="18%" headers="mcps1.3.5.2.4.1.1 "><p id="dns_usermanual_0032__p4777640105010"><a href="dns_usermanual_0033.html">Managing Private Zones</a></p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="27%" headers="mcps1.3.5.2.4.1.2 "><p id="dns_usermanual_0032__p3777134025015">Modify, delete, and query private zones.</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="55.00000000000001%" headers="mcps1.3.5.2.4.1.3 "><ul id="dns_usermanual_0032__ul18735122581518"><li id="dns_usermanual_0032__li47353256153">The name of a private zone cannot be modified after the zone is created.</li><li id="dns_usermanual_0032__li165411539169">After a private zone is deleted, all its record sets will also be deleted.</li></ul>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
<tr id="dns_usermanual_0032__row187779402501"><td class="cellrowborder" valign="top" width="18%" headers="mcps1.3.5.2.4.1.1 "><p id="dns_usermanual_0032__p117774407505"><a href="dns_usermanual_0003.html">Associating a VPC with a Private Zone</a></p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="27%" headers="mcps1.3.5.2.4.1.2 "><p id="dns_usermanual_0032__p157771840155010">Configure private domain names for VPCs.</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="55.00000000000001%" headers="mcps1.3.5.2.4.1.3 "><ul id="dns_usermanual_0032__ul1440617181573"><li id="dns_usermanual_0032__li25725401814">You can only associate VPCs that you have created using your own account.</li><li id="dns_usermanual_0032__li154074180719">Each VPC can be associated only with one private zone. However, a private zone can have more than one VPC associated with it.</li></ul>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
<tr id="dns_usermanual_0032__row571111020281"><td class="cellrowborder" valign="top" width="18%" headers="mcps1.3.5.2.4.1.1 "><p id="dns_usermanual_0032__p17712180172818"><a href="dns_usermanual_0004.html">Disassociating a VPC from a Private Zone</a></p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="27%" headers="mcps1.3.5.2.4.1.2 "><p id="dns_usermanual_0032__p1871213013282">Disassociate a VPC from a private zone.</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="55.00000000000001%" headers="mcps1.3.5.2.4.1.3 "><ul id="dns_usermanual_0032__ul12572850789"><li id="dns_usermanual_0032__li9572165019814">After the disassociation, private domain names will not take effect in the VPC.</li><li id="dns_usermanual_0032__li14572145010815">If a private zone is only associated with one VPC, you cannot disassociate it.</li></ul>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
</tbody>
|
||||||
|
</table>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="dns_usermanual_0002.html">Private Zone</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
32
docs/dns/umn/dns_usermanual_0033.html
Normal file
32
docs/dns/umn/dns_usermanual_0033.html
Normal file
@ -0,0 +1,32 @@
|
|||||||
|
<a name="dns_usermanual_0033"></a><a name="dns_usermanual_0033"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Managing Private Zones</h1>
|
||||||
|
<div id="body1571390688925"><div class="section" id="dns_usermanual_0033__section125317016203"><h4 class="sectiontitle"><strong id="dns_usermanual_0033__b292010511194">Scenarios</strong></h4><p id="dns_usermanual_0033__p4389381211647">You can view details of a private zone, modify a private zone, or delete a private zone.</p>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="dns_usermanual_0033__section10328742215619"><h4 class="sectiontitle">Modifying a Private Zone</h4><p id="dns_usermanual_0033__p4267020922232">Change the email address of the domain name administrator and description of the private zone.</p>
|
||||||
|
<div class="note" id="dns_usermanual_0033__note690345618481"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="dns_usermanual_0033__en-us_topic_0035467699_p3894942320387">For more information about the email address, see <a href="dns_faq_009.html">Why Was the Email Address Format Changed in the SOA Record?</a></p>
|
||||||
|
</div></div>
|
||||||
|
<ol id="dns_usermanual_0033__ol12712641114013"><li id="dns_usermanual_0033__li371264154014">Log in to the management console.</li><li id="dns_usermanual_0033__li187121441154013">In the service list, choose <strong id="dns_usermanual_0033__dns_qs_0006_en-us_topic_0035467699_b253764512375">Network</strong> > <strong id="dns_usermanual_0033__dns_qs_0006_en-us_topic_0035467699_b561505711379">Domain Name Service</strong>.<p id="dns_usermanual_0033__dns_qs_0006_en-us_topic_0035467699_en-us_topic_0035467699_p179595731633">The DNS console is displayed.</p>
|
||||||
|
</li><li id="dns_usermanual_0033__li6741145192613">In the navigation pane, choose <strong id="dns_usermanual_0033__dns_qs_0006_b842352706202035">Private Zones</strong>.<p id="dns_usermanual_0033__dns_qs_0006_en-us_topic_0035467699_p5173372716550">The <strong id="dns_usermanual_0033__dns_qs_0006_b84235270618511">Private Zones</strong> page is displayed.</p>
|
||||||
|
</li><li id="dns_usermanual_0033__li18750155113266">Click <span><img id="dns_usermanual_0033__dns_qs_0006_image18511144023210" src="en-us_image_0148391090.png"></span> in the upper left corner and select the desired region and project.</li></ol><ol start="5" id="dns_usermanual_0033__ol4848756122232"><li id="dns_usermanual_0033__li1779208222232">Locate the private zone you want to modify and click <strong id="dns_usermanual_0033__b842352706154223">Modify</strong> under <strong id="dns_usermanual_0033__b1022333411651">Operation</strong>.<p id="dns_usermanual_0033__p2591101422232">The <strong id="dns_usermanual_0033__b773312475134">Modify Private Zone</strong> dialog box is displayed.</p>
|
||||||
|
</li><li id="dns_usermanual_0033__li3187253922232">Change the email address or description of the zone as required.</li><li id="dns_usermanual_0033__li1841740322232">Click <strong id="dns_usermanual_0033__b842352706194656">OK</strong>.</li></ol>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="dns_usermanual_0033__section5576188803045"><h4 class="sectiontitle">Deleting a Private Zone</h4><p id="dns_usermanual_0033__p154033110310">Delete a private zone when you no longer need it. After a private zone is deleted, the domain name and its subdomains cannot be resolved by the DNS service.</p>
|
||||||
|
<div class="notice" id="dns_usermanual_0033__note11485317172410"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="dns_usermanual_0033__p20485111732410">Before you delete a private zone, back up all record sets in the private zone.</p>
|
||||||
|
</div></div>
|
||||||
|
<ol id="dns_usermanual_0033__ol69221353144018"><li id="dns_usermanual_0033__li119228533401">Log in to the management console.</li><li id="dns_usermanual_0033__li1092215317402">In the service list, choose <strong id="dns_usermanual_0033__dns_qs_0006_en-us_topic_0035467699_b253764512375_1">Network</strong> > <strong id="dns_usermanual_0033__dns_qs_0006_en-us_topic_0035467699_b561505711379_1">Domain Name Service</strong>.<p id="dns_usermanual_0033__dns_qs_0006_en-us_topic_0035467699_en-us_topic_0035467699_p179595731633_1">The DNS console is displayed.</p>
|
||||||
|
</li><li id="dns_usermanual_0033__li5922175314407">In the navigation pane, choose <strong id="dns_usermanual_0033__dns_qs_0006_b842352706202035_1">Private Zones</strong>.<p id="dns_usermanual_0033__dns_qs_0006_en-us_topic_0035467699_p5173372716550_1">The <strong id="dns_usermanual_0033__dns_qs_0006_b84235270618511_1">Private Zones</strong> page is displayed.</p>
|
||||||
|
</li><li id="dns_usermanual_0033__li1592255324014">Click <span><img id="dns_usermanual_0033__dns_qs_0006_image18511144023210_1" src="en-us_image_0148391090.png"></span> in the upper left corner and select the desired region and project.</li></ol><ol start="5" id="dns_usermanual_0033__ol4889762803138"><li id="dns_usermanual_0033__li2199194903153">Locate the private zone you want to delete and click <strong id="dns_usermanual_0033__b1814289799">Delete</strong> under <strong id="dns_usermanual_0033__b842352706154238">Operation</strong>.<p id="dns_usermanual_0033__p837216245010">The <strong id="dns_usermanual_0033__b1691812215146">Delete Private Zone</strong> dialog box is displayed.</p>
|
||||||
|
</li><li id="dns_usermanual_0033__li6370981503153">Click <strong id="dns_usermanual_0033__b8423527061907">Yes</strong>.</li></ol>
|
||||||
|
</div>
|
||||||
|
<div class="section" id="dns_usermanual_0033__section6093022701347"><h4 class="sectiontitle">Viewing Details About a Private Zone</h4><p id="dns_usermanual_0033__p6932113260">View details about a private zone, such as zone ID, operation time, tag, and TTL, on the <strong id="dns_usermanual_0033__b521411002115">Private Zones</strong> page.</p>
|
||||||
|
<ol id="dns_usermanual_0033__ol11732135112611"><li id="dns_usermanual_0033__li1173325182612">Log in to the management console.</li><li id="dns_usermanual_0033__li2073735111262">In the service list, choose <strong id="dns_usermanual_0033__dns_qs_0006_en-us_topic_0035467699_b253764512375_2">Network</strong> > <strong id="dns_usermanual_0033__dns_qs_0006_en-us_topic_0035467699_b561505711379_2">Domain Name Service</strong>.<p id="dns_usermanual_0033__dns_qs_0006_en-us_topic_0035467699_en-us_topic_0035467699_p179595731633_2">The DNS console is displayed.</p>
|
||||||
|
</li></ol><ol start="3" id="dns_usermanual_0033__ol879440801427"><li id="dns_usermanual_0033__li541508110260">On the <strong id="dns_usermanual_0033__b842352706184513">Dashboard</strong> page, click <strong id="dns_usermanual_0033__b921350611149">Private Zones</strong> under <strong id="dns_usermanual_0033__b1581269311149">My Resources</strong>.</li><li id="dns_usermanual_0033__li876543010419">Click <span><img id="dns_usermanual_0033__dns_qs_0006_image18511144023210_2" src="en-us_image_0148391090.png"></span> in the upper left corner and select the desired region and project.</li><li id="dns_usermanual_0033__li2576394701459">Locate the private zone you want to view and click <span><img id="dns_usermanual_0033__image10286163494917" src="en-us_image_0210877115.png"></span> before the zone name to view its details.</li></ol>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="dns_usermanual_0002.html">Private Zone</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
19
docs/dns/umn/dns_usermanual_0034.html
Normal file
19
docs/dns/umn/dns_usermanual_0034.html
Normal file
@ -0,0 +1,19 @@
|
|||||||
|
<a name="dns_usermanual_0034"></a><a name="dns_usermanual_0034"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Record Set</h1>
|
||||||
|
<div id="body1522119855921"></div>
|
||||||
|
<div>
|
||||||
|
<ul class="ullinks">
|
||||||
|
<li class="ulchildlink"><strong><a href="dns_usermanual_0035.html">Overview</a></strong><br>
|
||||||
|
</li>
|
||||||
|
<li class="ulchildlink"><strong><a href="dns_usermanual_0601.html">Record Set Types and Configuration Rules</a></strong><br>
|
||||||
|
</li>
|
||||||
|
<li class="ulchildlink"><strong><a href="dns_usermanual_0006.html">Adding Record Sets</a></strong><br>
|
||||||
|
</li>
|
||||||
|
<li class="ulchildlink"><strong><a href="en-us_topic_0035467703.html">Managing Record Sets</a></strong><br>
|
||||||
|
</li>
|
||||||
|
<li class="ulchildlink"><strong><a href="dns_usermanual_0036.html">Creating a Wildcard DNS Record Set</a></strong><br>
|
||||||
|
</li>
|
||||||
|
</ul>
|
||||||
|
</div>
|
||||||
|
|
57
docs/dns/umn/dns_usermanual_0035.html
Normal file
57
docs/dns/umn/dns_usermanual_0035.html
Normal file
@ -0,0 +1,57 @@
|
|||||||
|
<a name="dns_usermanual_0035"></a><a name="dns_usermanual_0035"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Overview</h1>
|
||||||
|
<div id="body1570616052156"><p id="dns_usermanual_0035__p4864873411842">A record set is a collection of resource records that belong to the same domain name. A record set defines DNS record types and values.</p>
|
||||||
|
|
||||||
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="dns_usermanual_0035__table977612405507" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Record set management</caption><thead align="left"><tr id="dns_usermanual_0035__row87771409504"><th align="left" class="cellrowborder" valign="top" width="18%" id="mcps1.3.2.2.4.1.1"><p id="dns_usermanual_0035__p15777740175016"><strong id="dns_usermanual_0035__b751616527318">Operation</strong></p>
|
||||||
|
</th>
|
||||||
|
<th align="left" class="cellrowborder" valign="top" width="37%" id="mcps1.3.2.2.4.1.2"><p id="dns_usermanual_0035__p47771140115015">Scenario</p>
|
||||||
|
</th>
|
||||||
|
<th align="left" class="cellrowborder" valign="top" width="45%" id="mcps1.3.2.2.4.1.3"><p id="dns_usermanual_0035__p11777174055015">Constraint</p>
|
||||||
|
</th>
|
||||||
|
</tr>
|
||||||
|
</thead>
|
||||||
|
<tbody><tr id="dns_usermanual_0035__row39491753508"><td class="cellrowborder" valign="top" width="18%" headers="mcps1.3.2.2.4.1.1 "><p id="dns_usermanual_0035__p16949195317012"><a href="dns_usermanual_0601.html">Record Set Types and Configuration Rules</a></p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="37%" headers="mcps1.3.2.2.4.1.2 "><p id="dns_usermanual_0035__p17950153206">View record set types supported by the DNS service and their configuration rules.</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="45%" headers="mcps1.3.2.2.4.1.3 "><p id="dns_usermanual_0035__p10950205314014">None</p>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
<tr id="dns_usermanual_0035__row3777840175020"><td class="cellrowborder" valign="top" width="18%" headers="mcps1.3.2.2.4.1.1 "><p id="dns_usermanual_0035__p167777403501"><a href="dns_usermanual_0006.html">Adding Record Sets</a></p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="37%" headers="mcps1.3.2.2.4.1.2 "><p id="dns_usermanual_0035__p777716406501">Add record sets to a domain name.</p>
|
||||||
|
<p id="dns_usermanual_0035__p88151212814">For details, see <a href="dns_usermanual_0601.html#dns_usermanual_0601__table352893684543">Table 1</a>.</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="45%" headers="mcps1.3.2.2.4.1.3 "><ul id="dns_usermanual_0035__ul446519315616"><li id="dns_usermanual_0035__li947882511516">After a zone is created for a domain name, the system automatically creates the SOA and NS record sets.</li><li id="dns_usermanual_0035__li124657311462">A maximum of 500 record sets can be added in an account.</li></ul>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
<tr id="dns_usermanual_0035__row626642913510"><td class="cellrowborder" valign="top" width="18%" headers="mcps1.3.2.2.4.1.1 "><p id="dns_usermanual_0035__p1526818291553"><a href="en-us_topic_0035467703.html">Managing Record Sets</a></p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="37%" headers="mcps1.3.2.2.4.1.2 "><p id="dns_usermanual_0035__p112681929453">Modify, delete, and view record sets.</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="45%" headers="mcps1.3.2.2.4.1.3 "><ul id="dns_usermanual_0035__ul1356620454552"><li id="dns_usermanual_0035__li7566174535518">After a record set is added, its resolution line cannot be modified.</li><li id="dns_usermanual_0035__li192139321831">You cannot modify or delete SOA and NS record sets automatically generated by the system.</li></ul>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
<tr id="dns_usermanual_0035__row1577754016507"><td class="cellrowborder" valign="top" width="18%" headers="mcps1.3.2.2.4.1.1 "><p id="dns_usermanual_0035__p4777640105010"><a href="dns_usermanual_0036.html">Creating a Wildcard DNS Record Set</a></p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="37%" headers="mcps1.3.2.2.4.1.2 "><p id="dns_usermanual_0035__p3777134025015">Add a record set that matches all subdomains.</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="45%" headers="mcps1.3.2.2.4.1.3 "><p id="dns_usermanual_0035__p17565192975913">Wildcard DNS resolution does not support NS record sets.</p>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
</tbody>
|
||||||
|
</table>
|
||||||
|
</div>
|
||||||
|
<p id="dns_usermanual_0035__p131811443182417"><a href="#dns_usermanual_0035__fig748135752616">Figure 1</a> shows the process for configuring a record set on the DNS console.</p>
|
||||||
|
<div class="fignone" id="dns_usermanual_0035__fig748135752616"><a name="dns_usermanual_0035__fig748135752616"></a><a name="fig748135752616"></a><span class="figcap"><b>Figure 1 </b>Process for configuring a record set</span><br><span><img id="dns_usermanual_0035__image17690172342617" src="en-us_image_0202565181.png"></span></div>
|
||||||
|
<div class="note" id="dns_usermanual_0035__note5433153912715"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="dns_usermanual_0035__p44331239162714">Either a public or private zone can be created. For details, see the following:</p>
|
||||||
|
<ul id="dns_usermanual_0035__ul1523631191810"><li id="dns_usermanual_0035__li723612113180"><a href="en-us_topic_0035467702.html">Creating a Public Zone</a></li><li id="dns_usermanual_0035__li22366119181"><a href="en-us_topic_0057773658.html">Creating a Private Zone</a></li></ul>
|
||||||
|
</div></div>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="dns_usermanual_0034.html">Record Set</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
112
docs/dns/umn/dns_usermanual_0036.html
Normal file
112
docs/dns/umn/dns_usermanual_0036.html
Normal file
File diff suppressed because it is too large
Load Diff
15
docs/dns/umn/dns_usermanual_0038.html
Normal file
15
docs/dns/umn/dns_usermanual_0038.html
Normal file
@ -0,0 +1,15 @@
|
|||||||
|
<a name="dns_usermanual_0038"></a><a name="dns_usermanual_0038"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">PTR Record</h1>
|
||||||
|
<div id="body1572594571593"></div>
|
||||||
|
<div>
|
||||||
|
<ul class="ullinks">
|
||||||
|
<li class="ulchildlink"><strong><a href="dns_usermanual_0039.html">Overview</a></strong><br>
|
||||||
|
</li>
|
||||||
|
<li class="ulchildlink"><strong><a href="en-us_topic_0077500015.html">Creating a PTR Record</a></strong><br>
|
||||||
|
</li>
|
||||||
|
<li class="ulchildlink"><strong><a href="dns_usermanual_0040.html">Managing PTR Records</a></strong><br>
|
||||||
|
</li>
|
||||||
|
</ul>
|
||||||
|
</div>
|
||||||
|
|
38
docs/dns/umn/dns_usermanual_0039.html
Normal file
38
docs/dns/umn/dns_usermanual_0039.html
Normal file
@ -0,0 +1,38 @@
|
|||||||
|
<a name="dns_usermanual_0039"></a><a name="dns_usermanual_0039"></a>
|
||||||
|
|
||||||
|
<h1 class="topictitle1">Overview</h1>
|
||||||
|
<div id="body1572603064320"><p id="dns_usermanual_0039__p870153112156">Reverse resolution involves obtaining a domain name based on an IP address and is typically used to improve credibility of email servers.</p>
|
||||||
|
<p id="dns_usermanual_0039__p13711315155">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 fails to obtain the domain name mapped to the sender's IP address, it considers that the email is sent by a malicious host and rejects it. Therefore, it is necessary to map IP addresses of your email servers to domain names by adding PTR records.</p>
|
||||||
|
|
||||||
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="dns_usermanual_0039__table977612405507" frame="border" border="1" rules="all"><caption><b>Table 1 </b>PTR record description</caption><thead align="left"><tr id="dns_usermanual_0039__row87771409504"><th align="left" class="cellrowborder" valign="top" width="18.181818181818183%" id="mcps1.3.3.2.4.1.1"><p id="dns_usermanual_0039__p15777740175016">Operation</p>
|
||||||
|
</th>
|
||||||
|
<th align="left" class="cellrowborder" valign="top" width="32.323232323232325%" id="mcps1.3.3.2.4.1.2"><p id="dns_usermanual_0039__p47771140115015">Scenario</p>
|
||||||
|
</th>
|
||||||
|
<th align="left" class="cellrowborder" valign="top" width="49.494949494949495%" id="mcps1.3.3.2.4.1.3"><p id="dns_usermanual_0039__p11777174055015">Constraint</p>
|
||||||
|
</th>
|
||||||
|
</tr>
|
||||||
|
</thead>
|
||||||
|
<tbody><tr id="dns_usermanual_0039__row3777840175020"><td class="cellrowborder" valign="top" width="18.181818181818183%" headers="mcps1.3.3.2.4.1.1 "><p id="dns_usermanual_0039__p167777403501"><a href="en-us_topic_0077500015.html">Creating a PTR Record</a></p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="32.323232323232325%" headers="mcps1.3.3.2.4.1.2 "><p id="dns_usermanual_0039__p777716406501">Create PTR records for cloud resources such as ECS.</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="49.494949494949495%" headers="mcps1.3.3.2.4.1.3 "><ul id="dns_usermanual_0039__ul446519315616"><li id="dns_usermanual_0039__li1686818375018">PTR records are project-level resources. When you create a PTR record, you need to select a region and project.</li><li id="dns_usermanual_0039__li124657311462">Each user can add a maximum of 50 PTR records.</li></ul>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
<tr id="dns_usermanual_0039__row1577754016507"><td class="cellrowborder" valign="top" width="18.181818181818183%" headers="mcps1.3.3.2.4.1.1 "><p id="dns_usermanual_0039__p4777640105010"><a href="dns_usermanual_0040.html">Managing PTR Records</a></p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="32.323232323232325%" headers="mcps1.3.3.2.4.1.2 "><p id="dns_usermanual_0039__p3777134025015">Modify, delete, and query PTR records.</p>
|
||||||
|
</td>
|
||||||
|
<td class="cellrowborder" valign="top" width="49.494949494949495%" headers="mcps1.3.3.2.4.1.3 "><ul id="dns_usermanual_0039__ul18735122581518"><li id="dns_usermanual_0039__li47353256153">After you created a PTR record, its EIP cannot be changed.</li><li id="dns_usermanual_0039__li165411539169">After you delete a PTR record, the domain name mapped to your EIP will change to the default domain name.</li></ul>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
</tbody>
|
||||||
|
</table>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
<div>
|
||||||
|
<div class="familylinks">
|
||||||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="dns_usermanual_0038.html">PTR Record</a></div>
|
||||||
|
</div>
|
||||||
|
</div>
|
||||||
|
|
Some files were not shown because too many files have changed in this diff Show More
Loading…
x
Reference in New Issue
Block a user