Cloudfront Distribution domain name to resolves to "Not found"

0

I was just doing our quarterly checks on the services we have on AWS ( don't have many, but the numbers are growing ).

This time I was checking our CloudFront distributions and I noticed when in one of our Distributions.

  

The Distribution domain name URL ( e.g.   dgk******oprh.cloudfront.net   ) resolves to "Not found"

I checked the Origin name / Origin domain URLs, and that URL (   links.iterable.com   - same value for both Origin name & domain ) resolves properly.

  

I'm fairly green with AWS and after 2 hours of running in circles I thought I'd ask if anyone has any idea on anything I might have missed?

Or is this a fairly normal occurence? ( that the Distribution domain name URL doesn't resolve )?

2 Answers
0

If you have verified if the origin domain URL is operational or not, kindly let us know which services are being used at the origin. Please enable the necessary permissions and public access if you plan to use an S3 bucket. and you looked up the origin or S3 bucket URL. after which you check the CDN URL and integrate with Cloudfront. Please let us know if it doesn't work in the comment area.

profile picture
kamal
answered a month ago
0

Please chech the following.

  • Verify that the correct name servers are registered with your domain registrar and point to the hosted zone in Route 53 where you've created the DNS records. It can take time for changes to propagate, so check back after waiting for the DNS time-to-live (TTL) period.
  • Check that you have the proper DNS record types (A, AAAA, CNAME etc.) created in Route 53 that point your domain or subdomains to the appropriate AWS resources like CloudFront distribution or S3 website.
  • Review any health checks configured in Route 53 for the DNS records. An unhealthy check could cause failures
  • Run a DNS lookup tool like dig or nslookup and check for NXDOMAIN responses which indicate the record is not found.
  • Consider temporarily reducing the TTL value to speed up troubleshooting if changes don't seem to be propagating.
  • Check for issues with subdomain delegation if using subdomains.
profile picture
EXPERT
answered a month ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions