AWS Amazon Route 53 Error Codes

This CIDR block is already in use.

A CIDR collection with this name and a different caller reference already exists in this account.

This CIDR collection is in use, and isn't empty.

The CIDR collection version you provided, doesn't match the one in the ListCidrCollections operation.

Another user submitted a request to create, update, or delete the object at the same time that you did. Retry the request.

The cause of this error depends on the operation that you're performing: Create a public hosted zone: Two hosted zones that have the same name or that have a parent/child relationship (example.com and test.example.com) can't have any common name servers. You tried to create a hosted zone that has the same name as an existing hosted zone or that's the parent or child of an existing hosted zone, and you specified a delegation set that shares one or more name servers with the existing hosted zon

You tried to update a traffic policy instance by using a traffic policy version that has a different DNS type than the current type for the instance. You specified the type in the JSON document in the CreateTrafficPolicy or CreateTrafficPolicyVersionrequest.

A delegation set with the same owner and caller reference combination has already been created.

The specified delegation set has already been marked as reusable.

The specified delegation contains associated hosted zones which must be deleted before the reusable delegation set can be deleted.

You can create a hosted zone that has the same name as an existing hosted zone (example.com is common), but there is a limit to the number of hosted zones that have the same name. If you get this error, Amazon Route 53 has reached that limit. If you own the domain name and Route 53 generates this error, contact Customer Support.

A reusable delegation set with the specified ID does not exist.

The hosted zone doesn't have any DNSSEC resources.

The health check you're attempting to create already exists. Amazon Route 53 returns this error when you submit a request that has the following values: The same value for CallerReference as an existing health check, and one or more values that differ from the existing health check that has the same caller reference. The same value for CallerReference as a health check that you created and later deleted, regardless of the other settings in the request.

This error code is not in use.

The value of HealthCheckVersion in the request doesn't match the value of HealthCheckVersion in the health check.

The hosted zone you're trying to create already exists. Amazon Route 53 returns this error when a hosted zone has already been created with the specified CallerReference.

The hosted zone contains resource records that are not SOA or NS records.

The specified HostedZone can't be found.

The specified hosted zone is a public hosted zone, not a private hosted zone.

The hosted zone nameservers don't match the parent nameservers. The hosted zone and parent must have the same nameservers.

The resource you're trying to access is unsupported on this Amazon Route 53 endpoint.

Amazon Route 53 doesn't have the permissions required to create log streams and send query logs to log streams. Possible causes include the following: There is no resource policy that specifies the log group ARN in the value for Resource. The resource policy that includes the log group ARN in the value for Resource doesn't have the necessary permissions. The resource policy hasn't finished propagating yet. The Key management service (KMS) key you specified doesn’t exist or it can’t be us

Parameter name is not valid.

This exception contains a list of messages that might contain one or more error messages. Each error message indicates one error in the change batch.

The specified domain name is not valid.

The input is not valid.

The key-signing key (KSK) name that you specified isn't a valid name.

The key-signing key (KSK) status isn't valid or another KSK has the status INTERNAL_FAILURE.

The KeyManagementServiceArn that you specified isn't valid to use with DNSSEC signing.

The value that you specified to get the second or subsequent page of results is invalid.

Your hosted zone status isn't valid for this operation. In the hosted zone, change the status to enable DNSSEC or disable DNSSEC.

The format of the traffic policy document that you specified in the Document element is not valid.

The VPC ID that you specified either isn't a valid ID or the current account is not authorized to access this VPC.

You've already created a key-signing key (KSK) with this name or with the same customer managed key ARN.

The key-signing key (KSK) is specified in a parent DS record.

The key-signing key (KSK) that you specified can't be deactivated because it's the only KSK for a currently-enabled DNSSEC. Disable DNSSEC signing, or add or enable another KSK.

A key-signing key (KSK) with ACTIVE status wasn't found.

The VPC that you're trying to disassociate from the private hosted zone is the last VPC that is associated with the hosted zone. Amazon Route 53 doesn't support disassociating the last VPC from a hosted zone.

This operation can't be completed because the current account has reached the limit on the resource you are trying to create. To request a higher limit, create a case with the Amazon Web Services Support Center.

A change with the specified change ID does not exist.

The CIDR collection you specified, doesn't exist.

The CIDR collection location doesn't match any locations in your account.

There is no CloudWatch Logs log group with the specified ARN.

A reusable delegation set with the specified ID does not exist.

Amazon Route 53 doesn't support the specified geographic location. For a list of supported geolocation codes, see the GeoLocation data type.

No health check exists with the specified ID.

No hosted zone exists with the ID that you specified.

The specified key-signing key (KSK) doesn't exist.

There is no DNS query logging configuration with the specified ID.

No traffic policy exists with the specified ID.

No traffic policy instance exists with the specified ID.

Associating the specified VPC with the specified hosted zone has not been authorized.

If Amazon Route 53 can't process a request before the next request arrives, it will reject subsequent requests for the same hosted zone and return an HTTP 400 error (Bad request). If Route 53 returns this error repeatedly for the same request, we recommend that you wait, in intervals of increasing duration, before you try the request again.

You're trying to associate a VPC with a public hosted zone. Amazon Route 53 doesn't support associating a VPC with a public hosted zone.

You can create only one query logging configuration for a hosted zone, and a query logging configuration already exists for this hosted zone.

The limit on the number of requests per second was exceeded.

This health check can't be created because the current account has reached the limit on the number of active health checks. For information about default limits, see Limits in the Amazon Route 53 Developer Guide. For information about how to get the current limit for an account, see GetAccountLimit. To request a higher limit, create a case with the Amazon Web Services Support Center. You have reached the maximum number of active health checks for an Amazon Web Services account. To request a high

This operation can't be completed either because the current account has reached the limit on the number of hosted zones or because you've reached the limit on the number of hosted zones that can be associated with a reusable delegation set. For information about default limits, see Limits in the Amazon Route 53 Developer Guide. To get the current limit on hosted zones that can be created by an account, see GetAccountLimit. To get the current limit on hosted zones that can be associated with a r

You've reached the limit for the number of key-signing keys (KSKs). Remove at least one KSK, and then try again.

This traffic policy can't be created because the current account has reached the limit on the number of traffic policies. For information about default limits, see Limits in the Amazon Route 53 Developer Guide. To get the current limit for an account, see GetAccountLimit. To request a higher limit, create a case with the Amazon Web Services Support Center.

This traffic policy instance can't be created because the current account has reached the limit on the number of traffic policy instances. For information about default limits, see Limits in the Amazon Route 53 Developer Guide. For information about how to get the current limit for an account, see GetAccountLimit. To request a higher limit, create a case with the Amazon Web Services Support Center.

This traffic policy version can't be created because you've reached the limit of 1000 on the number of versions that you can create for the current traffic policy. To create more traffic policy versions, you can use GetTrafficPolicy to get the traffic policy document for a specified traffic policy version, and then use CreateTrafficPolicy to create a new traffic policy using the traffic policy document.

You've created the maximum number of authorizations that can be created for the specified hosted zone. To authorize another VPC to be associated with the hosted zone, submit a DeleteVPCAssociationAuthorization request to remove an existing authorization. To get a list of existing authorizations, submit a ListVPCAssociationAuthorizations request.

A traffic policy that has the same value for Name already exists.

There is already a traffic policy instance with the specified ID.

One or more traffic policy instances were created by using the specified traffic policy.

The VPC that you specified is not authorized to be associated with the hosted zone.

The specified VPC and hosted zone are not currently associated.