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.
Although, when I reach the website through S3 static website hosting it's working:
Any ideas?
EDIT:
Route53:
I have one A record that traffics to <id>.cloudfront.net:
I have one NS record that traffics to 4 NS URLs.
I have one SOA record.
I have one CNAME record.
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
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.
Related
So, I've created a website xxxxxxx.com (removing from post)
I registered it with Route 53.
Registered Domain - Established Hosted Zone
Established 2 Record Sets one of xxxxxxxx.com and one for www.xxxxxx.com
Record Set Details for one of the paths
But when I go to ping www.xxxxxxxx.com or xxxxxxxx.com - I don't get a response.
When I go to a DNS checker site - it fails all DNS servers.
I've been all over the place trying to get this to work, concerningly, it did work at one time, but then failed. I have deleted the hosted zone twice and rebuilt it. I have NOT touched the named servers.
S3:
setup 2 buckets, named appropriately. xxxxxxxx.com and www.xxxxxxxx.com
Both have two files on them. Block public is unchecked.
Static Web hosting is enabled.
Selected both files and set to Actions --> Make Public
Testing on their own with these addresses:
**edited - I had to remove the direct S3 Web hosting as once posted here they got hammered with hits.
I did try one other thing:
Route 53 --> Traffic Policies --> Create Traffic Policy -->
DNS Type a: IP address in IPv4 format to Endpoint Type S3 website endpoint Value xxxxxxxx.com.s3-website-us-east-2....
This does not appear to have rectified the situation, unfortunately. And they want to charge $10 a month to direct it with www. prefix - which doesn't make any kind of sense, so I didn't do that.
Any advice or help that can be rendered would be helpful! I've covered most of the ground with Amazon and videos setting up domain to S3 to no avail.
Something seems off with your DNS records: https://www.whatsmydns.net/#NS/fojsan.com
Domain registered 2 days ago, should have NS listed in all regions. Leave the S3 for the time being and focus here. If DNS record can not resolve , S3 will not work.
Make sure that DNS entry for NS (name Servers) is set to:
ns-1145.awsdns-15.org.
ns-1694.awsdns-19.co.uk.
ns-20.awsdns-02.com.
ns-576.awsdns-08.net.
It looks like it might have been removed and are expiring.
i have bought a domain, for example examp.com, by hoster x.
A little bit later i have realized that aws is better for me.
I have register a hosted zone with my domain and change the NS-records by hoster x to the NS-Server from my hosted zone.
It works perfect!
But now i would like to whitelabeling my website.
For example a client have a domain abc.de and he would like to access my website with a subdomain sub.abc.de.
My idea was to create a CNAME-Record on sub.abc.de that points to examp.com.
But that not work (Not Found - The requested URL was not found on this server.).
I have read that the target server gotta know from the CNAME-Record that points to him. But i don't know how can i do that. In my hosted zone i can only register subdomains for examp.com for a ALIAS or so but not for another domain.
Can anybody help me?
If they control the domain of abc.de they are able to create the record their side for sub.abc.de as a CNAME record with the value set as your domain (examp.com).
They should never be attempting to CNAME to your NS server records, these are records for where your DNS records can be retrieved from.
Other than you providing the CNAME value of examp.com to them it is upto them to configure their DNS to target your hostname.
Been through a couple of tutorials, AWS official docs and SO questions, and still can't get my Route53 Alias to work.
I've done this in the past, but for some reason on this particular domain – www.tallyhaus.com, the same steps I've taken before just don't seem to work.
I'm 100% sure of the following:
bucket name matches the alias record name
my bucket is reachable: the s3 endpoint offered by the bucket works, and is hittable
the NS entries are the same on my registered domain, as in my NS record on my hosted zone
The domain in question is www.tally.haus.
The only different thing I can think of is that I have a subdomain for my API, which lives under api.tally.haus, and that NS record points to the NSs on my Lightsail instance – but I created a separate hosted zone for that subdomain.
I even tried creating a CloudFront distribution to see if that works, and still nothing.
Ideas?
Thanks
NOTE: Endpoint that I'm talking about, the one that isn't resolving, is www.tally.haus.
Step-by-step example
Create a bucket with the name mysite.tally.haus
Activate static website hosting on the bucket. Website endpoint will be
similar to this: http://mysite.s3-website-us-west-2.amazonaws.com
Add index.html to the bucket
Make the index.html public
In Route53 add an A-Record, click on Alias and type in appropriate S3 Website endpoint depending on your S3 bucket location.
For this use case, it is : s3-website-us-west-2.amazonaws.com.
Record set will look like this:
mysite.tally.haus. A ALIAS s3-website-us-west-2.amazonaws.com.
Amazon Simple Storage Service Website Endpoints:
https://docs.aws.amazon.com/general/latest/gr/rande.html
I have a hosted zone in Amazon Route 53 service and a domain name on a registrar.
In the registrar, my DNS configurations are correctly inserted, with the four address provided by AWS when I create the hosted zone.
In the Route 53 control panel, I have the NS and SOA proper configured as it came configured when I created the hosted zone.
I also created a A Redirection : mydomain.com.br -> xxx.xxx.xxx.xxx (elastic IP)
I'm able to reach my EC2 instance with the A Record: If I type mydomain.com.br on browser it works fine.
My problem is that I'm unable to reach the CNAME's that I've created.
I have a CNAME rule: www.mydomain.com.br -> mydomain.com.br/site but when I put www.mydomain.com.br I get a DNS error on my browser.
The strangest thing is that if I consult www.mydomain.com.br on a site like https://www.whatsmydns.net it points to www.mydomain.com.br/site, which is the correct redirect. The DNS resolution aparently works fine, but I can't get it on the browser.
Any help would be nice. Thanks.
ps: I alredy tried to ipconfig/flushdns and clear chrome's cache
Try this:
Delete that CNAME record
Add an A record in Route53
Name the A record 'www' it should automatically make that www.mydomain.com.br.
Check the ALIAS-yes box
Select mydomain.com.br. from the dropdown box (note there is a PERIOD on the end)
Save and Wait about 5 minutes.
A better (and still very cheap) way to do this might be to set up a 301 redirect in an Amazon S3 bucket. Here is a link to Amazon's tutorial:
http://docs.aws.amazon.com/AmazonS3/latest/dev/how-to-page-redirect.html
Do you have a "www" A record which is pointed to your EIP?
I am moving several sites to S3 to host them as static sites and have moved DNS here as well. I followed the AWS guide step by step, but continually get an error on the CNAME setup for WWW. Here is my setup:
Created bucket jeremyandlauren.com and set up static hosting and permissions.
Endpoint is now jeremyandlauren.com.s3-website-us-west-2.amazonaws.com and this works fine.
Pointed nameservers for this domain to Route 53.
Created an A record pointing to the Alias Target jeremyandlauren.com.s3-website-us-west-2.amazonaws.com.
Created a CNAME pointing www to jeremyandlauren.com.s3-website-us-west-2.amazonaws.com.
Now when you hit the URL either with or without www you get:
Code: NoSuchBucket
Message: The specified bucket does not exist
BucketName: www.jeremyandlauren.com
Does anyone have any ideas how to fix this? I have tried a couple options for the CNAME, but nothing seems to take.
Thanks in advance.
It looks like jeremyandlauren.com works, however, www.jeremyandlauren.com does not work. The reason you are probably running into this is that your DNS name needs to match your bucket name. You probably do not have a bucket with the name of www.jeremyandlauren.com. There are two way easy ways to fix this.
Create a bucket www.jeremyandlauren.com and redirect it to jeremyandlauren.com. (More info here: http://aws.amazon.com/about-aws/whats-new/2012/10/04/web-page-redirects-on-amazon-s3-hosted-websites/)
Create a CloudFront distribution with the origin of jeremyandlauren.com.s3-website-us-west-2.amazonaws.com. Add www.jeremyandlauren.com & jeremyandlauren.com as a CNAME. Update DNS for www.jeremyandlauren.com & jeremyandlauren.com to be an A type alias to your CloudFront Distribution.
Keep both www.jeremyandlauren.com & jeremyandlauren.com buckets in sync with the same data.
Its working fine for me - both with and without the 'www' if its not working for you, it may be because your dns is cached locally, or the propagation has just not made it to your servers yet - give it time.
If you are using chrome you can try clearing your local dns cache:
Navigate to chrome://net-internals/#dns and press the "Clear host cache" button.