PuppyIP Resource Center
Cloud Operations 5 min Published 2026-11-19

Connect Route 53 Global Resolver to AWS Cloud WAN for private DNS

If your sites already reach AWS Cloud WAN through Direct Connect or Site-to-Site VPN, clients can use Route 53 Global Resolver over that private network. Choose at least two supported Regions, create a Cloud WAN core network endpoint, and authorize the appropriate segment. For a private-only setup, follow the AWS tutorial and disable Public IP connectivity.

AWS Cloud WAN Route 53 Global Resolver Private DNS Anycast

Service eligibility and regional restrictions

PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.

Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.

Key Takeaways

  • Use Regions where both Global Resolver and Cloud WAN are available.
  • A core network endpoint needs at least two selected Regions. A resolver currently supports one core network endpoint.
  • Authorize clients through a DNS view and a Cloud WAN segment access source, and associate private hosted zones as needed.
  • Check for core network policy version 2026.10 or later if you need closest-Region routing.

Confirm each site's Cloud WAN path

On November 17, AWS announced that Global Resolver can serve anycast DNS over private connections managed through Cloud WAN. Clients can use a Direct Connect or Site-to-Site VPN connection already attached to Cloud WAN, without adding public DNS forwarding for this feature. A working private connection to AWS alone does not establish that it reaches the Cloud WAN core network you plan to use.

Verify which Regions support both services and whether you have permission to manage the relevant resources. The AWS private connectivity tutorial uses at least two Regions. The ability to create Global Resolver in one Region does not establish that you can create the endpoint with the same regional selection.

Create the resolver and its core network endpoint

Create a Route 53 Global Resolver and choose at least two suitable Regions. In a private-only setup, disable Public IP connectivity. Under Core network endpoints, create an endpoint for the relevant Cloud WAN core network. The endpoint's two or more Regions must be among the Regions you selected for the resolver.

An endpoint supports up to five private IP addresses. Choose privately routable IPv4 or IPv6 addresses that do not conflict with ranges in your Cloud WAN network, following the current AWS documentation. A resolver currently supports one core network endpoint. Before changing client settings, confirm which private addresses the clients will use and whether the existing network can reach them for DNS.

Verify reachability and query authorization separately

After connecting the core network, create a DNS view and add an access source of type Cloud WAN segment. Select the segment whose clients should be allowed to query. For private Route 53 names, associate the relevant private hosted zones with the intended view using the AWS documentation. Verify private names separately even if public DNS queries succeed.

For example, an office segment and an engineering segment may use the same core network, while only engineering should resolve a private application name. Test a known name from both the authorized segment and a second segment. Confirm that the DNS result follows the intended access policy and view.

Validate closest-Region routing and failover

AWS documents core network policy version 2026.10 for closest-Region routing, and its tutorial recommends that version or later. Before upgrading a policy, check its existing version and assess the effect on your network. AWS describes automatic failover between Regions. Validate the actual failover behavior on your own test path.

Before switching production clients, query a known public name and an authorized private name from each relevant site using a private endpoint address. Record the source segment, resolver address, response, and time. For a failed private query, check endpoint reachability, segment authorization, and the hosted zone association in the DNS view before changing production forwarding.

Sources

Frequently Asked Questions

Can I create a Cloud WAN endpoint with one Region?

The AWS tutorial requires at least two Regions for a core network endpoint, both already selected for the resolver.

Can private clients resolve public names when public connectivity is off?

The setting controls public connectivity to the resolver. Authorized clients connecting privately through Cloud WAN can still use it to resolve public DNS names.

Can one Global Resolver connect to two Cloud WAN core networks?

A resolver currently supports one core network endpoint, and an endpoint connects to one core network.