What Are Huawei Cloud Private DNS Server Addresses?
Private DNS servers are used in VPCs to:
- Resolve private domain names and internal domain names of cloud services.
- Work as a proxy for requests to public domain names. The following record sets are supported: A, CNAME, MX, AAAA, TXT, SRV, NS, SOA, and PTR.
Compared with public DNS servers (for example, 114.114.114.114), private DNS servers provided by Huawei Cloud DNS can:
- Resolve private domain names used in VPCs.
- Enable access to cloud services such as OBS and SMN.
- Allow ECSs without EIPs to access the Internet.
Table 1 lists private DNS server addresses provided by Huawei Cloud DNS in different regions.
- Set DNS Server Address for the VPC subnet where an ECS resides to the private DNS server addresses available in each region. For details, see How Do I Change Default DNS Servers of an ECS to Huawei Cloud Private DNS Servers?
Table 1 lists the private DNS server addresses available in each region.
- If you set DNS Server Address to external DNS server addresses, traffic will be routed to public IP addresses when the ECS accesses other cloud services, which may incur additional traffic fees.
- When an ECS accesses a third-party domain name on the Internet, the private DNS server functions as a recursive DNS server, and the authoritative DNS server returns the final resolution result. Whether the resolution result is reliable or optimal depends on uncontrollable factors such as third-party authoritative DNS. It is recommended that the ECS access cloud services over their private domain names.
- When a Huawei Cloud private DNS server recursively resolves a third-party domain name on the Internet, IP addresses of dynamic BGP serve as the egress. If you use a static BGP EIP, the access latency may not be optimal. If you have requirements on the access latency of third-party domain names, use dynamic BGP EIPs.
- When a private DNS server resolves domain names or works as a DNS proxy for handling requests for resolving public domain names, DNS Security Extensions (DNSSEC) and DNS extensions are not supported. If your application is highly dependent on DNSSEC, you can create a DNS server via ECS to achieve this function.
| Region | Private DNS Server Address |
|---|---|
| CN North-Beijing1 | 100.125.1.250 |
| 100.125.21.250 | |
| CN North-Beijing4 | 100.125.1.250 |
| 100.125.129.250 | |
| CN North-Ulanqab1 | 100.125.1.250 |
| 100.125.107.250 | |
| CN North3 | 100.125.248.9 |
| 100.125.248.10 | |
| CN Southwest-Guiyang1 | 100.125.1.250 |
| 100.125.129.250 | |
| CN South-Guangzhou | 100.125.1.250 |
| 100.125.136.29 | |
| CN East-Shanghai1 | 100.125.1.250 |
| 100.125.64.250 | |
| CN East-Shanghai2 | 100.125.17.29 |
| 100.125.135.29 | |
| CN East-Qingdao | 100.125.251.249 |
| 100.125.251.250 | |
| CN East2 | 100.125.248.9 |
| 100.125.248.10 | |
| CN South-Shenzhen | 100.125.1.250 |
| 100.125.1.111 | |
| CN-Hong Kong | 100.125.1.250 |
| 100.125.3.250 | |
| AP-Bangkok | 100.125.1.250 |
| 100.125.1.251 | |
| AP-Singapore | 100.125.1.250 |
| 100.125.128.250 | |
| AP-Jakarta | 100.125.2.250 |
| 100.125.2.251 | |
| AP-Manila | 100.125.241.9 |
| 100.125.241.10 | |
| AF-Johannesburg | 100.125.1.250 |
| 100.125.1.14 | |
| AF-Cairo | 100.125.251.249 |
| 100.125.251.250 | |
| TR-Istanbul | 100.125.2.250 |
| 100.125.2.251 | |
| LA-Santiago | 100.125.1.250 |
| 100.125.0.250 | |
| LA-Sao Paulo1 | 100.125.1.22 |
| 100.125.1.90 | |
| LA-Mexico City1 | 100.125.1.22 |
| 100.125.1.90 | |
| LA-Mexico City2 | 100.125.1.250 |
| 100.125.1.242 | |
| ME-Riyadh | 100.125.250.249 |
| 100.125.250.250 |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot
