- Le plus récent
- Le plus de votes
- La plupart des commentaires
Hi peterskandar
The error you’re receiving “ConflictingDomainExists” might be because you have private DNS option enabled for one of your VPC endpoints.
When you create a VPC Interface Endpoint with Private DNS option enabled, a Private Hosted Zone with the same name as the regional DNS gets associated with the VPC.
So, if you manually try to create a new Private Hosted Zone with the same name and associate it with the VPC then it will result in the same "ConflictingDomainExists" error.
Thus, to resolve the problem, you will need to disable Private DNS option for the VPC endpoint . Once that has been done, the domain name of the hosted zone you are trying to create will be removed from the VPC endpoints Private DNS Names and you will be able to create Private hosted zone with domain name in Route 53 service and successfully associate it to the VPC.
Please follow below steps to disable Private DNS name for a VPC endpoint:
* Open the Amazon VPC console at https://console.aws.amazon.com/vpc/
* In the navigation pane, choose Endpoints
* Select your VPC endpoint.
* Choose the Actions button, next to Create endpoint and select Modify Private DNS names.
* To disable the private DNS option for the interface endpoint, for Enable DNS Name, select the check box.
* Click on save
I hope this helps
References
1] Private DNS for interface endpoints - https://docs.aws.amazon.com/vpc/latest/privatelink/vpce-interface.html#vpce-private-dns
Contenus pertinents
- demandé il y a 7 mois
- demandé il y a 10 mois
- demandé il y a un an
- Réponse acceptéedemandé il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans