AWS Certificate Won't Validate with GoDaddy after adding CNAME Record ---

Question

This is my first time using AWS and I am wanting to validate my domain / certificate. Very unexperienced, but I have added the CNAME name and value into GoDaddy's records for the particular domain I am working with. I have done it twice, and the validation has failed twice after waiting 72 hours each time.

I would greatly appreciate anyone who can point me in the right direction to resolve this issue.

Riku_Kobayashi · Answer

Hello.

If you manage your domain with GoDaddy, the validation will fail if you simply copy and use the CNAME record issued by ACM.  
As mentioned in the stackoverflow answer below, try registering only the necessary parts of the CNAME record copied from ACM.  
https://stackoverflow.com/a/54836562

re:Post Agent · Answer

It sounds like you're experiencing a common issue with DNS validation for AWS Certificate Manager (ACM) when using GoDaddy as your DNS provider. Here's how to fix it:

When adding the CNAME record to GoDaddy for ACM validation, you need to truncate the apex domain (including the period) at the end of the NAME field. For example, if ACM provides you with:

```
NAME: _ho9hv39800vb3examplew3vnewoib3u
VALUE: _cjhwou20vhu2exampleuw20vuyb2ovb9.j9s73ucn9vy.acm-validations.aws.
```

Make sure you're entering it exactly as provided by ACM, with the exception of removing the apex domain from the NAME field.

After your validation has failed twice, you'll need to:

1. Delete the failed certificate request in ACM
2. Create a new certificate request
3. Add the new CNAME validation record to GoDaddy with the truncated NAME format
4. Verify the DNS resolution is working correctly using tools like nslookup or dig before proceeding

ACM typically attempts to validate a domain for up to 72 hours. If validation fails within this period, the certificate status changes to "Validation timed out."

Also, ensure that:
- You've added the CNAME record to the correct domain in GoDaddy
- You've copied the VALUE field exactly as provided by ACM
- There are no Certification Authority Authorization (CAA) records blocking certificate issuance

If you continue to experience issues after following these steps, you might consider using email validation as an alternative method, though DNS validation is generally preferred for its automatic renewal capabilities.  
**Sources**  
[Troubleshoot DNS validation problems - AWS Certificate Manager](https://docs.aws.amazon.com/acm/latest/userguide/troubleshooting-DNS-validation.html)  
[I have a problem verifying my request for aws certificate. | AWS re:Post](https://repost.aws/questions/QUSFuavjxeQ4mslFzL0fPPww/i-have-a-problem-verifying-my-request-for-aws-certificate)  
[AWS Certificate verification pending | AWS re:Post](https://repost.aws/questions/QU1aRlx6WaT0aJZq2zl0JgQw/aws-certificate-verification-pending)  
[AWS Certificate Manager DNS validation - AWS Certificate Manager](https://docs.aws.amazon.com/acm/latest/userguide/dns-validation.html)

AWS Certificate Won't Validate with GoDaddy after adding CNAME Record ---

Add your answer

Relevant content