CNAME records wont resolve to Siteground

Question

Hello all.

I have two separate AWS accounts connected to two separate sites to use SES as my SMTP.  Both were set up without a problem on my hosting for those sites.  Both sites are hosted by Siteground.  I am attempting to add my new site and I am getting an error message and the cname and txt records wont resolve to the host.  I went through troubleshooting with Siteground tech support and they didn't see any issues on their end.  I was wonderinf what I am doing wrong.  I copied and pasted the records exactly in the right place.  Please help!

re:Post Agent · Answer

Based on the information provided, there are several potential reasons why your CNAME records are not resolving to Siteground for your new site. Here are some key points to consider:

1. DNS Propagation: DNS changes can take up to 24-48 hours to propagate globally. If you've recently made these changes, you may need to wait longer for them to take effect.

2. Name Server Configuration: Ensure that the name servers (NS records) in your domain registrar account exactly match those provided by Route 53 for your hosted zone. This is a critical step that's often overlooked and can prevent proper DNS resolution.

3. Record Configuration: Double-check that you've created the CNAME records exactly as specified by Amazon SES. Even a small typo can prevent validation and resolution.

4. Hosted Zone Setup: Verify that you've created a public hosted zone in Route 53 (not a private one) and that you've correctly added the CNAME records within this zone.

5. TTL Values: Check the Time-to-Live (TTL) values for your records. Consider temporarily lowering this value to allow for faster propagation during your initial setup and troubleshooting.

6. Conflicting Records: Ensure there are no conflicting records or zones for your domain that might be interfering with the CNAME resolution.

To troubleshoot further:

1. Use DNS lookup tools like 'dig' or 'nslookup' to verify that your records are resolving correctly.

2. Compare the setup of your new site with the two existing sites that are working correctly to identify any differences.

3. If possible, try creating a test CNAME record pointing to a different destination to see if the issue is specific to the Siteground resolution.

If after checking these items and waiting for propagation your CNAME records still don't resolve, you may need to review your overall DNS setup more thoroughly or contact AWS Support for further assistance, especially if you suspect there might be an issue with the Route 53 or SES services themselves.

**Sources**  
[No CNAME propagation | AWS re:Post](https://repost.aws/questions/QUpXLFjfEiRWSrah3UAlkTmw/no-cname-propagation)  
[A and CNAME records not working? | AWS re:Post](https://repost.aws/questions/QUV_QW1UvFSxG0mk6qTYU7ZA/a-and-cname-records-not-working)

CNAME records wont resolve to Siteground

Add your answer

Relevant content