1 Answer
- Newest
- Most votes
- Most comments
0
The problem was in the registration of the hosted zone that had DNS different from those registered in the domain .com. When I created a new hosting zone, Router 53 did not update the DNS on the domain .com record. I accessed the option "Domains > Registered Domains" and "Name servers > Add or edit name servers", after selecting my domain .com, and I put the same information that was in the NS type record for my hosted zone.
Relevant content
- asked 2 years ago
- AWS OFFICIALUpdated 5 months ago
Here are a few troubleshooting steps that you can try:
Check that the DNS records for your domain are correctly configured. Specifically, ensure that the DNS records created by Certificate Manager are present in your Route 53 hosted zone and that they have the correct values. You can do this by navigating to the "DNS Management" section of your Route 53 hosted zone and verifying that the records match the values provided by Certificate Manager.
Check that your DNS resolver is able to resolve the domain name and that there are no issues with caching or propagation. You can do this by using a tool like dig or nslookup to query the DNS records for your domain and verifying that the responses match the expected values.
Verify that your SSL/TLS certificate request is valid and that it has not been revoked. You can do this by navigating to the "Certificates" section of the AWS Certificate Manager console and checking the status of the certificate request. If the certificate request has been revoked or is otherwise invalid, you may need to request a new certificate.
Check the CloudWatch Logs log group to see if any error messages are being logged that could help you diagnose the issue.
Also, be mindful of region - When you request a public SSL/TLS certificate with ACM, you can choose to use either the Amazon-issued domain validation method or the DNS validation method. If you choose the DNS validation method, ACM will create DNS records that must be added to your domain's DNS configuration. These DNS records can be created in any AWS region where Route 53 is available, regardless of where you requested the certificate.
However, it's worth noting that there are some AWS services, such as Elastic Load Balancing (ELB), that have specific requirements regarding SSL/TLS certificates. For example, when you use an SSL/TLS certificate with an ELB, the certificate must be stored in the same region as the ELB. In such cases, you may need to create and manage SSL/TLS certificates in specific regions to meet the requirements of these services.