Resolver Overview

What Is a Resolver?

DNS Resolver answers DNS queries to and from your on-premises data center after your data center is connected to the cloud over Direct Connect or VPN.

Generally, on-premises data centers can access cloud resources over a Direct Connect or VPN connection. However, for security purposes, on-premises servers are not allowed to access the DNS service on the cloud directly. If your on-premises servers need to access private domain names used within VPCs, or your cloud servers use Huawei Cloud private DNS to access an on-premises domain name, you need to set up DNS on your cloud servers for forwarding DNS queries between the cloud DNS and on-premises DNS. This increases management and maintenance costs and causes reliability risks.

With Huawei Cloud DNS Resolver, on-premises servers and cloud servers can easily communicate with each other in hybrid cloud scenarios.

• DNS Resolver is now available in CN North-Ulanqab1, CN Southwest-Guiyang1, AP-Bangkok, AP-Singapore, AP-Jakarta, LA-Sao Paulo1, TR-Istanbul, AF-Johannesburg, and ME-Riyadh.
• Both inbound and outbound endpoints do not support DNSSEC.
• By default, cloud servers use private DNS for domain name resolution. Do not change private DNS addresses, or forwarding rules will not take effect.

Where to Use

• On-premises servers access a cloud service domain name. For this to work, you need to create an inbound endpoint and configure forwarding rules on the on-premises DNS servers to forward the DNS queries for the cloud service domain name to the IP addresses specified in the inbound endpoint.

  For details, see Managing Inbound Endpoints.

• Cloud servers access an on-premises domain name. For this to work, you need to create an outbound endpoint, configure endpoint rules, and specify the on-premises domain name to be accessed and the IP addresses of on-premises DNS servers. Huawei Cloud private DNS then forwards the DNS queries for the on-premises domain name to the on-premises DNS servers based on the endpoint rules.

  For details, see Managing Outbound Endpoints.