- 新しい順
- 投票が多い順
- コメントが多い順
Hello.
Lightsail's VPC is managed by AWS, so AWS accounts are separate.
To tie a VPC managed by another AWS account to a private host zone, you must follow the steps described in the following document.
However, since Lightsail VPCs are managed by AWS, the "AssociateVPCWithHostedZone" API cannot be used to associate a VPC with a private hosted zone.
In other words, I don't think you can use Route53's private hosted zone with Lightsail.
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/hosted-zone-private-associate-vpcs-different-accounts.html
Hello,
No, Route 53 private zones are not inherently incompatible with Lightsail. You should be able to access your private zone domain from Lightsail instances through a peered VPC connection.
Here are some things to check that might be causing the issue:
DNS Resolver Configuration: Ensure the DNS resolver settings on your Lightsail instance are pointing to the Route 53 private hosted zone for the default VPC. Lightsail instances typically use the DNS servers provided by Amazon by default.
Security Groups: Verify that the security groups associated with your Lightsail instance allow inbound traffic on port 53 (DNS) from the default VPC.
Route Table Configuration: Double-check that the route tables in both VPCs have proper routing configured for the private zone domain to be directed to the Route 53 resolvers in the default VPC.
If you've confirmed these settings and the issue persists, consider checking the VPC peering connection status and reviewing the Route 53 private zone logs for any errors.
However Here i provide a documentation link for Working with private hosted zones:https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/hosted-zones-private.html
関連するコンテンツ
- 質問済み 6年前
- AWS公式更新しました 1年前
- AWS公式更新しました 2年前
- AWS公式更新しました 1年前
are you able to telnet a port Ec2 instance in other VPC from Lighsail instance, Where the R53 zone created ?