Question 18837 in Amazon Web Sevices Question posted in
The official Amazon Web Services documentation can be found here.

I'm getting ERR_NAME_NOT_RESOLVED from my website – Amazon Web Sevices

I have a domain that I got from NameCheap: www.app.flerr.io.

I configured the domain in AWS with Route53, CloudFront and S3.

I uploaded the static website to the relevant S3 bucket.

When I try to reach my website, I get the following error: ERR_NAME_NOT_RESOLVED.

enter image description here

Although, when I reach the website through S3 static website hosting it’s working:

enter image description here

Any ideas?

EDIT:

Route53:

I have one A record that traffics to <id>.cloudfront.net:

enter image description here

I have one NS record that traffics to 4 NS URLs.

I have one SOA record.

I have one CNAME record.

Tags:

2

Answers


  1. 0

    ERR_NAME_NOT_RESOLVED usually refers to a DNS problem.

    You already verified that S3 URL is working correctly.
    Now, verify that Cloudfront is working correctly by pasting the Cloudfront URL in your browser (<id>.cloudfront.com or something similar).

    If both of them are working, means that your problem is indeed DNS (and therefore Route53) related.

    Use any DNS Lookup page to see if your domain (flerr.io) is correctly set up.
    https://mxtoolbox.com/SuperTool.aspx?action=a%3awww.app.flerr.io&run=toolpage

    With the information given that’s the best we can do, if you share your Route53 Hosted Zones we could see if anything is wrong

    Login or Signup to reply.
  2. 0

    If you bought flerr.io. – you dont need to create a new zone for app.flerr.io. (you can, but its not required – this is called DNS delegation). You just need to create a record named www.app inside flerr.io. as an A or CNAME to your destination.

    When i use dig to test the DNS i get the following results:

    • dig flerr.io. shows A records
    • dig app.flerr.io. shows A records – and appears to be its own DNS delegation zone (was that deliberate)?
    • dig www.app.flerr.io. does not return any records – this is why you cant resolve your site.

    I think the solution for you is to create the www.app records in the flerr.io. zone and ignore the app.flerr.io. zone you created. If your trying to use the zone app.flerr.io. (and its been setup properly in flerr.io.) you would just create the www record.

    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search