How do I troubleshoot the Route 53 hosted zone error "ConflictingDomainExists"?

Resolution

Follow these troubleshooting steps for your scenario to resolve the error "ConflictingDomainExists".

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 or associated a private hosted zone in Route 53

This issue occurred because the Amazon Virtual Private Cloud (Amazon VPC) that's specified is already associated with another hosted zone with the same name.

Note: If you have a private DNS name activated for a VPC endpoint, make sure that the hosted zone name doesn't use the same name.

To resolve this issue, specify a different VPC with the private hosted zone or associate the VPC with a different private hosted zone. To delete a hosted zone, see How do I delete a Route 53 hosted zone?

To get a list of VPCs that are associated with a hosted zone, run the following command in the AWS CLI:

aws route53  list-hosted-zones-by-vpc --vpc-id VPC_ID --vpc-region REGION_ID

Note: Replace VPC_ID and REGION_ID with your relevant values.

To get a list of private hosted zones that are associated with specific VPCs, run the following command in the AWS CLI:

aws route53 get-hosted-zone --id VPC_ID

Note: Replace VPC_ID with your relevant value.

Scenario 2: You tried to create a public hosted zone in Route 53

This issue occurs when you tried to create a public hosted zone in the following scenarios:

• The hosted zone has the same name as an existing hosted zone.
• The hosted zone is the parent or child of an existing hosted zone such as example.com and test.example.com.
• You specified a reusable delegation set that shares one or more name servers with the existing hosted zone.

To resolve this issue, make sure that there are no hosted zones with the same name or overlapping namespaces. You can also create a new delegation set with different name servers and then use the new set to create a hosted zone.

Related information

How do I troubleshoot issues with hosted zones in Route 53 that have the same domain names in different AWS accounts?

How do I associate a Route 53 private hosted zone with a VPC on a different AWS account?