I am using EC2 Amazon Web services, and also I am using route 53. My domain example.com is not resolving, I can see the website if I type elastic IP address. How can I solve this problem. Thanks in advance,
A very nicely written steps to do the config :
http://docs.aws.amazon.com/gettingstarted/latest/swh/getting-started-configure-route53.html
Because you did not add what you have done so far in the route 53, I have to ask below general question and you can verify if you have done these.
Have you created a hosted zone?
Have you added type A record in your recordset to point example.com to your EIP?
Have you created cname for your www.example.com?
Have you logged in your domain name registrar site and updated the nameservers provided by route 53?
Related
I've got a website hosted on elastic beanstalk and a .nz domain on www.sitehost.com.
I need to route the domain to the website. All the documentation I'm seeing tells me to transfer the domain to Route 53... but you can't use .nz domains with Route 53.
I've had a look at setting up DNS records on my current domain host but I'm not 100% which records/information need to be added. Is it as simple as adding DNS records? Or can you only route elastic beanstalk websites through Route 53 and do I need to take my website off AWS and host somewhere else??
Appreciate any advice!
Cheers,
Daniel.
Is it as simple as adding DNS records?
Depends on the capabilities given to you by sitehost and what is your domain. If you want to point subdomain (e.g. www.mysite.nz) to EB, just use CNAME record. If you want to point root domain (e.g mysite.nz) CNAME can't be used, and you may need to contact sitehost if they have any special/custom records for root domains.
Or can you only route elastic beanstalk websites through Route 53 and do I need to take my website off AWS and host somewhere else??
You can host it on AWS. But if the sitehost does not allow you to create CNAME or other records, then you can setup Route53 as your DNS service. This is different then migrating a domain. Your domain is still in sitehost, but all its records are managed by R53. This requires you to setup NS records in sitehost. But again, it depends if sitehost allows you to do it.
I have a domain registered with Route53 (AWS). I'm trying to connect it as my Custom Domain on a Shopify store.
I update the A record and the CNAME record with the following values.
#, A, 23.227.38.65
www, CNAME, shops.myshopify.com
Despite setting these records up and going through the domain verification settings in Shopify, I'm unable to get the DNS to properly resolve and direct traffic to my Shopify store. Instead, the browser always just says:
server IP address could not be found.
Is there something I'm missing on the AWS/Route53 side? It's in a Public Hosted Zone, so I don't believe I need to create any inbound VPC rules or security group configurations.
Any help would be greatly appreciated!
RESOLVED.
In the Name servers settings of the domain, I had to update them to the same NS records that Route53 had generated within the DNS settings. Once done everything started working after a few minutes.
This was caused by the domain not having its matching name servers configured within Route 53.
The OP had migrated his domain to Route 53 and setup a public hosted zone in Route 53, however the connection between the 2 had not been made.
To resolve this take all the values from the NS record of the public hosted zone and add them to the Nameservers configuration in Route 53.
Take a look at the Adding or changing name servers and glue records for a domain page for further step on this action.
So I was to host my main website with Wix, but I want to maintain subdomains in AWS. For example:
example.com -> Wix website
api.example.com -> Load balancer
How can this be accomplished? Thanks in advance!
[Edit] I should mention that the domain is not registered with Wix. It’s actually registered with Google, and the DNS is configured for AWS
I believe you'll need to create a third-level domain (often called a "subdomain") name A record in Wix DNS.
Is this the same scenario here: How to add a subdomain pointing to IP of EC2 instance in AWS where the domain is pointing to the IP of the machine of some other hosting provider?
Thanks,
Daniel
I am following Heroku's instructions on how to get my AWS domain name on Route 53 to point to my Heroku app. The end of the instructions say:
"Go back to the Hosted Zones list and select your new hosted zone. There is a pre-populated Delegation Set section in the sidebar. These are the nameservers you need to provide your domain registrar for Route 53 to resolve your app domain."
I assume that the nameservers they are referring to are the four web addresses with "awsdns" in their name with type NS. My question is, who is my domain registrar and how do I provide these name servers to them? I originally bought this domain through GoDaddy before transferring it to AWS. Is GoDaddy my domain registrar? How do I determine this? Thank you.
Did you transfer the domain to AWS, or did you simply create a hosted zone for the domain name? If you transferred the domain to AWS, which it doesn't sound like you did, the nameservers are configured by Route 53 and are set. It sounds like you need to go to the Domain Settings via the GoDaddy console and set the AWS nameservers as your nameservers for your GoDaddy domain.
I have a simple question for pointing my Bigrock Domain name to Amazone EC2.
I have Created HostedZone from Hostedzone-create link
I got 4 name servers.
Now what?
Suppose my domain name is example.com on Bigrock.com.
Can anyone explain me how can i point that domain name to EC2?
I asked to Bigrock support but they told me something like this:
The website is not working because the DNS zone for your domain is not
configured properly on your Hosting providers DNS servers ( AWS Server
). Please get in touch with your provider for further assistance.
But I am not getting what they want to say. Please help!!
To move your Name Servers to AWS Route 53 first you have to change the Name Servers in Bigrock follow this steps.
http://support.hostgator.com/articles/hosting-guide/lets-get-started/dns-name-servers/how-to-change-name-servers-with-bigrock
Once that is done go to AWS Route 53 and create two record sets one for the "naked domain" and another for "www" domain and add a A-Record to point to the EC2 IP address (Be Sure the IP address is Elastic just in case for future change in IP address of the server so that you are covered).
This is Route 53 Guide
http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resource-record-sets-creating.html
Now, you will go to your bigrock.com and find your domain. Change the default name servers information with that 4 name servers information provided by Route53 on amazon. save your changes and wait for few hours to be activated properly.