How do I troubleshoot the Route 53 hosted zone error "ConflictingDomainExists"?
I tried to create or associate an Amazon Route 53 hosted zone and received the error "ConflictingDomainExists".
Resolution
Note: If you receive errors when you run AWS Command Line Interface (AWS CLI) commands, then see Troubleshoot AWS CLI errors. Also, make sure that you're using the most recent AWS CLI version.
Scenario 1: You created a private hosted zone or associated a VPC with a private hosted zone in Route 53
You can't have a hosted zone with the same name as another hosted zone that is associated with the same Amazon Virtual Private Cloud (Amazon VPC). Take one of the following actions:
- Remove any private hosted zone from the specified Amazon VPC that has the same name as the new hosted zone.
- Create a new private hosted zone with a different domain name.
To get a list of private hosted zones that you have associated with specific Amazon VPCs, run the list-hosted-zones-by-vpc AWS CLI command:
aws route53 list-hosted-zones-by-vpc --vpc-id VPC\_ID --vpc-region REGION\_ID
Note: Replace VPC_ID and REGION_ID with your values.
When you enable private DNS for Amazon VPC interface endpoints, Route 53 automatically creates and manages AWS managed private hosted zones. Because these private hosted zones are AWS managed, they're not visible in your console. To check for AWS managed private hosted zones, use the list-hosted-zones-by-vpc command in the AWS CLI. If the name conflict results from a private DNS for the interface endpoint, then either turn off private DNS or delete the Amazon VPC interface endpoint.
Scenario 2: You tried to create a public hosted zone in Route 53 with a reusable delegation set
If you have an existing hosted zone, you can't create a new hosted zone with the same name that uses the same name servers from a reusable delegation set. You also can't specify a reusable delegation set if the new hosted zone is the parent or child of an existing hosted zone, such as example.com and test.example.com.
To resolve this issue, you can create a new delegation set with different name servers that don't overlap. Use the new set to create a hosted zone. Or, you can create the hosted zone without a delegation set. Then, Route 53 verifies that existing hosted zones don't share the namespace.
Related information
- Tags
- Amazon Route 53
- Language
- English
GetHostedZone API call returns the information about a specified hosted zone including the four name servers assigned to the hosted zone and the VPCs associated with the specified hosted zone. https://docs.aws.amazon.com/Route53/latest/APIReference/API_GetHostedZone.html https://awscli.amazonaws.com/v2/documentation/api/latest/reference/route53/get-hosted-zone.html
aws route53 get-hosted-zone --id Z1R8UBAEXAMPLE
ListHostedZonesByVPC on the other hand lists all the private hosted zones that a specified VPC is associated with, regardless of which AWS account or AWS service owns the hosted zones.
https://docs.aws.amazon.com/Route53/latest/APIReference/API_ListHostedZonesByVPC.html https://awscli.amazonaws.com/v2/documentation/api/latest/reference/route53/list-hosted-zones-by-vpc.html
aws route53 list-hosted-zones-by-vpc --vpc-id vpc-123456789abcdefgh --vpc-region REGION-ID
Thank you for your comment. We'll review and update the Knowledge Center article as needed.
Relevant content
- asked 2 years ago
- AWS OFFICIALUpdated a month ago
