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?
Related
I have recently created a cloudfront distribution (using the LightSail admin area) for a Lightsail instance running Plesk on Ubuntu. I have created custom domains and validated them and they are "Valid, in use".
My domain is hosted through Route 53. When I delete the static IP address value of the apex domain record by changing the "Value/Route traffic to" an "Alias to CloudFront distribution" and then paste the distribution address, (ex: 123456abcdef.cloudfront.net) the entire site goes down.
My cloudfront address (ex: 123456abcdef.cloudfront.net) is resolving to the default Plesk domain. I just seem to have problems with proper Route 53 DNS configuration.
I have followed the instructions here with no success: https://aws.amazon.com/getting-started/hands-on/map-your-domain-at-route53-to-lightsail/4/
I have also looked at a similiar post on Stack Overflow here: How to apply CDN with cloudfront - router 53 => lightsail instance However, I have not configured my cloudfront distribution in cloudfront, but rather in Lightsail.
Here is an image of my apex DNS Record:
Image of my A record entry
Do I need to create another record in my hosted zone? A record that continues to point the apex domain to the static IP?
Any help appreciated. Thanks.
I am responding to my own question with an answer I think addresses the problem in an alternate way.
I have been trying for a month to set up a CloudFront on my WordPress site running on a Lightsail Instance running Plesk using Route 53 as my DNS provider. I have finally been able to get it running. I installed the AWS for Wordpress Plugin. Follow this guide to set up a user.
Plugin Setup AWS Doc
My preferred domain is www.mydomain.ca. My WP site is setup to direct to www.mydomain.ca NOT mydomain.ca. In route 53 my apex domain (mydomain.ca) points to my static ip. The www.mydomain.ca record is set an ALIAS A record and points to the cloudfront domain name (123456abcdef.cloudfront.net). During set up the AWS WP pluging told me to set www.mydomain.ca to a CNAME ALIAS which will not work. I found some more useful documentation in another thread on SO.
It all seems to be working. However, you need to make sure you do not have any other cloudfront distributions connected to the origin (youdomain.ca), active or inactive, in the Cloudfront admin area OR the Lightsail admin area. This causes a conflict and the set up in the WP admin area will fail.
I hope this post helps someone and saves them a month &%$%ing around with Cloudfront Wordpress setup using Lightsail and Route 53.
I'm starting out on AWS and try to host a website on the platform. The S3 bucket and its content is set up and i'm able to access the website via the url s3 is providing.
Permissions and properties are set to accept public traffic and that the bucket is used to host a website. The index document is correct.
Now i want traffic to be redirected to my domain visionranger.com, but it shows the error "IP address could not be found"
I tested this issue on 4 different devices across multiple browsers (including Chrome, Safari and Firefox).
Bucket, domain and hosted zone do have the same name and as AWS recommends, I asked my previous provider if they transferred the dns services to the new provides (in this case route 53) and they did.
I waited longer than 48 hours after settings everything up before writing this so all services should be working by now - but they don't.
The image shows the dns records of route 53.
I am grateful for any help.
By running a DIG command to get the NS value of your domain it returns a SERVFAIL indicating that the configured nameservers for your domain do not contain the record for you domain.
The next step is to run a whois which indicates your configured nameservers are below:
NS1.BDM.MICROSOFTONLINE.COM
NS2.BDM.MICROSOFTONLINE.COM
NS3.BDM.MICROSOFTONLINE.COM
NS4.BDM.MICROSOFTONLINE.COM
As you're trying to use a Route 53 public hosted zone you will need to update your domain registrar to use the nameservers found under the NS record of the public hosted zone.
Follow the instructions here for your specific domain.
I bought a domain through Route 53, oproponitis.com, I have an elastic beanstalk enviroment that works fine, I can open the page through the EBS url. I have a hosted zone where with A record simple record redirecting to this environment, but when I open the page it gives me DNS_PROBE_FINISHED_NXDOMAIN, it drives me crazy as I cant find info about it anywhere, and it is a pretty simple setup.
Any idea what is maybe going wrong?
update
This is as a result of a DNS lookup failing for your Name Servers.
As you purchased your domain in Route 53 and also have a public hosted zone in Route 53 this should be an easy solution to fix.
In the AWS console access your public hosted zone and make a note of the values of the NS record (there should be 4 domains).
Then in the Route 53 console do the following:
Access the Registered Domains link.
Click on your domain
Click Add or edit Name Servers
Specify the values of each of the values you copied earlier from the NS record.
I had the same issue and the problem was that I didn't verify my email.
I'm trying to get the website I've set up in Elastic Beanstalk live. I bought a domain www.semiflex.work from Hover.com. I understand that I need to connect my domain to Elastic Beanstalk via Route 53, but I'm getting a lot of conflicting information as to how I can do this.
I've tried creating CNAME record sets in both Route 53 and Hover as an Alias with a link to my Elastic Beanstalk website, but that didn't work. I then also replaced the nameservers in Hover with the ones in Route 53, but that didn't work either. It's been roughly 4 days and I can't get my site to run on my new domain. How would I go about getting this to work?
Thanks in advance.
Using Route53 to manage your DNS is simple and straightforward.
Go to to Route53 and create a hosted zone for your domain. As soon as you create your hosted zone, Route53 will generate two default entries: a SOA entry, and an NS entry with 4 nameservers that you assign to your domain in order for Route53 to manage your zone file.
Next go to your domain registrar, in this case Hover, and update the nameservers of your domain to the nameservers provided by Route53.
Now that Route53 is managing the zone file for your domain, you can create an appropriate entry for your ElasticBeanstalk app. Open your domains hosted zone and select “create record set”. On the right hand side, you’ll be able to enter a sub-domain (optionally), like www, next you’ll be able to select the type of record this is, such a an A, CNAME, MX, TXT or other. If you’re using your domain with another AWS service like Elastic Beanstalk, CloudFront, or S3, you’ll want to leave the type as an A record and then in the next section you’ll set Alias to yes. Now, in the target, you’ll either select where you want Route53 to Alias to from the available option in the current account, or if you’re aliasing to a supported service in another account you’ll enter the target such as the ElasticBeanstalk or CloudFront URL.
Click “save record set” and the entry will be live within seconds (assuming the DNS has propagated).
Now that Route53 is managing your DNS, and because IP addresses for services can change, your DNS will not need to be updated because Route53 will automatically take care of updating the destination for the record if/when it changes.
We went through your issue and noticed that you must have misconfigured your route53 settings. You do not need to create an CNAME record for routing your domain through elastic beanstalk environment. Just need to create a record set by enabling Alias and selecting Alias target as your environment URL in the dropdown list.
To do so go through -->> Create Record set -->>Click on Alias -->>Select Alias Target.
This will resolve your problem assuming that you have updated name servers in domain registrar.
Ended up solving this the old fashioned way.
AWS part
On Route 53, create a hosted zone. In that hosted zone, create a record set that is Type A - IPv4 - address, Alias Target = your elastic beanstalk url. Save record set. Then click on that record set, and then click on the button "Test Record Set." Then click "Get Response." Copy the I.P address "in Response returned by Route 53"
Hover part
Set Nameservers on hover = ns1.hover.com, ns2.hover.com. Then click on "DNS" and add two records where Type = A, Host = *, Value = your Route 53 I.P address & Type = A, Host = #, Value = your Route 53 I.P address.
Can take up to 48 hours to work, but it works!
I have been trying to connect my domain with my elastic beanstalk instance.
My domain was purchased off GoDaddy and I have updated the nameservers to point to AWS and verified through dig. If dig comes up with the NS, it means GoDaddy is properly configured to point to the DNS right?
The Test Record Set function also does not show any error and has a proper response returned which has NOERROR
Problem is I still receive an ERR_NAME_NOT_RESOLVED everytime I try to load the website on browsers even tried on different devices
I have also checked the alias used in my Hosted Zone and its up and running
What I have already done:
Initialized and created Beanstalk environment - Up and Running
Public Hosted Zone - Created A record for www.mysite.com
GoDaddy DNS NS - updated with AWS 4 nameservers
Checks I have done:
Internal Test Record for A www.mysite.com
Dig Command
What could I be missing?
UPDATE***
So I figured "www.mysite.com' was working but 'mysite.com' alone was not. I'm assuming route53 will automatically use the www A record? But seems like its not?
Hope ya'll could help
Thanks!
Got it to work.
Looks like besides creating a www A record, I had to create a record for the root domain i.e mysite.com in the Record Set of my Hosted Zone
Solved!