PuppyIP Resource Center
Network & Connection Troubleshooting 5 min Published 2026-11-19

Overlapping AWS private CIDRs? Check 1:1 NAT, routes, and DNS

When two VPCs use the same IPv4 range, Transit Gateway or Cloud WAN can map their attachments to distinct NAT CIDRs. Traffic crossing the networks uses the translated addresses. During a cutover, check the mapping, routes in both directions, and the DNS answer each client receives.

AWS Transit Gateway AWS Cloud WAN 1:1 NAT Overlapping CIDRs Private DNS

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

  • Original and NAT CIDRs must have equal prefix lengths. The mapping preserves host bits and ports.
  • For identical VPC ranges, choose a distinct NAT CIDR for each side in the routing domain.
  • With system routes enabled for BGP attachments, check advertisements for the original range. With system routes disabled, advertise the translated range explicitly.
  • Test the translated address and service port from the actual client, then check the client’s DNS view and application hostname.

Choose distinct translated ranges for the overlapping networks

AWS announced support on October 23 and published examples for overlapping VPCs, Direct Connect multicloud connectivity, and Site-to-Site VPN on November 16. The feature provides static, bidirectional IPv4 translation on each attachment. Each rule maps original and translated CIDRs of equal length while preserving host bits and ports. Use RFC 1918 private space or RFC 6598 shared space for NAT CIDRs, and avoid ranges already used in the relevant routing domain.

Suppose two VPCs both use 10.0.0.0/24. You can map side A to 100.64.20.0/24 and side B to 100.64.21.0/24 if those ranges are available. A client in A connects to the host at 10.0.0.18 in B using 100.64.21.18. B sees a source from A’s translated range, allowing its reply to route back through the gateway.

Check forwarding as well as the attachment rules

When the original ranges are identical, a reply to an untranslated source can match the receiving VPC’s local route. Follow the AWS VPC example by mapping both sides. Check that each subnet route table sends the peer’s NAT CIDR to the gateway. Then check that destination security groups or network ACLs allow the source address they will see.

On a Transit Gateway VPC attachment, a MatchSourceCidr that exactly matches a full VPC CIDR can replace its propagated route with a route for the NAT CIDR. A rule for a subset, such as a /24 inside a /16, can translate traffic without an automatically installed NAT CIDR route. For a subset, check for a static route to that NAT CIDR pointing to the attachment.

Check BGP against the system route setting

For a Direct Connect gateway or a BGP Site-to-Site VPN attachment, enabling system routes installs a route for the NAT CIDR. It still depends on the peer advertising a route that overlaps the original CIDR. Traffic is dropped without that advertisement, and Transit Gateway can show the route as blackhole. Check whether the route is usable even if the NAT rule exists.

With system route installation disabled, advertise the NAT CIDR from your BGP peer and verify the service learned it as a propagated route. Check the matching entry and next hop in the route table or Cloud WAN segment. A longer prefix wins first. A static route for the same prefix can take precedence over the system route and lead to a different attachment.

Verify the translated address and DNS independently

1:1 NAT rewrites packet addresses. The client’s DNS view determines what a hostname resolves to. If a connection to the translated address and expected service port works but the hostname fails, query DNS from the same client. Check for an original address in the answer or a stale cached record.

AWS documents that translation rules and routes can take effect at different times. In a maintenance window, prepare the DNS change and rollback details. Verify the rules, effective routes, and both traffic directions from the affected network before directing the intended clients to the verified address. With multiple DNS views, confirm each cross-network client resolves the address intended for its view.

Sources

Frequently Asked Questions

Do I need to map both sides if the two VPCs have identical CIDRs?

AWS’s example for identical ranges maps both attachments. Mapping only one side can cause replies to follow the other VPC’s local route.

Why is the NAT CIDR unreachable even though the rule exists?

Check the effective route separately. For a Transit Gateway rule covering a subset of a VPC range, check the static route for the NAT CIDR. For BGP, check advertisements for the original or translated prefix based on the system route setting.

Does 1:1 NAT update private DNS records automatically?

The resolver and DNS records determine the answer. Query from an affected client and verify that hostnames used across the network resolve to the translated address.