[英]VPC Peering - DNS resolves to public IP
I have configured VPC peering connection between VPC A and VPC B (they are in different accounts but in the same region), and when I try to resolve the domain name of a service (eg sometest.com) that is in the VPC B from an instance VPC A, it is supposed to point to a private IP but it resolves to the public IP. The route tables for both VPCs have corresponding entries for peer connection, also security groups allow traffic from/to the peered VPC, and both VPC have "Enable DNS resolution/hostnames enabled.我已经在 VPC A 和 VPC B 之间配置了 VPC 对等连接(它们在不同的帐户中但在同一区域),当我尝试解析 VPC B 中的服务(例如 sometest.com)的域名时实例 VPC A,它应该指向私有 IP 但它解析为公共 IP。两个 VPC 的路由表都有对应的对等连接条目,安全组也允许来自/到对等 VPC 的流量,并且两个 VPC启用“启用 DNS 分辨率/主机名。
I'm not sure why it resolves to the public IP - what am I missing?我不确定为什么它会向公众解析 IP - 我错过了什么?
you need to have vpc-association-authorization established between 2 VPC's and private zones to be able to resolve private hosted zone addresses from 1 vpc in one region/account to another vpc in another region/account您需要在 2 个 VPC 和私有区域之间建立 vpc-association-authorization 才能将私有托管区域地址从一个区域/账户中的 1 个 vpc 解析到另一个区域/账户中的另一个 vpc
you can follow this step to step guide: https://aws.amazon.com/premiumsupport/knowledge-center/route53-private-hosted-zone/您可以按照此步骤指南进行操作: https://aws.amazon.com/premiumsupport/knowledge-center/route53-private-hosted-zone/
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.