Route .nz domain to elastic beanstalk (can't use Route 53) - amazon-web-services

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.

Related

how to let web application use the purchased domain name through ROUTE 53 in AWS?

I have purchased a domain name through ROUTE 53.
2) I have created a EC2 instance and put my web application inside it that is supposed to be hosted.
3) I have configured the Gunicorn and nginx as my WSGI and web server.
How to use the purchased domain name to integrate with my application to see over the internet. I have seen many documents post on stackoverflow, and youtube videos. But I am not able to get the clear picture of what am suppose to do next.
I get that once the domain is registered I have 4 ns records generated inside the ROUTE 53. But where to use them? how to configure them.
It be helpful if somebody can give me exact steps to perform the tasks.
Thank you,
Route53 is similar to other DNS servers with extra features, in your case, you will need to assign your ec2 instance a public IP address and to be safe an Elastic IP to avoid IP change on reboot, then you need to grab this public IP and assign it to your domain root A record and www CNAME record to point to that domain
I get that once the domain is registered I have 4 ns records generated
inside the ROUTE 53. But where to use them? how to configure them.
Normally it's not required but it's helpful to control your DNS configuration from route 53 instead of the DNS registrar.
Create Hosted zone in route 53, for example if your domain name is example.com then create Hosted zone in route with name example.com, it will generate name server record.
Open newly created hosted zone and copy Name server (NS) record and replace the NS record in your DNS setting.
When you create a hosted zone, Route 53 automatically creates a name server (NS) record and a start of authority (SOA) record for the zone. The NS record identifies the four name servers that Route 53 associated with your hosted zone. To make Route 53 the DNS service for your domain, you update the registration for the domain to use these four name servers.
Add these record in DNS Name server, for example the below one is used for Godaddy
migrating-a-domain-to-amazon-route53

how to point AWS Route53 subdomain to AWS Lightsail instance?

I have setup a Wordpress on Lightsail, and have created a static IP which I can access WP ok.
I have migrated my .co.uk domain across to Route53 from another provider and am trying to point blog.example.co.uk to my Lightsail instance.
In Lightsail I have setup a DNS record like this:
A example.co.uk 12.34.56.78
A blog.example.co.uk 12.34.56.78
It then lists these DNS servers in Lightsail:
ns-849.awsdns-42.net
ns-1643.awsdns-13.co.uk
ns-341.awsdns-42.com
ns-1516.awsdns-61.org
I've taken those DNS servers and set on the root of my domain in Route 53 under Domains > Registered Domains
I am not sure if that was the correct thing to do, as I will have other subdomains eventually that will point elsewhere, should the Lightsail DNS servers be added at that level? If not, what do I set them back to be?
I have also created a Route53 Hosted Zone, and have created an "A" entry that links blog.example.co.uk to 12.34.56.78, is that required?
As mentioned in the comments, I was facing the same challenge.
What ended up working for me was simply creating an Alias Record (A) for my subdomain, subdomain.example.com, that points to the static IP of my Lightsail instance.
I did not add Lightsail's DNS servers anywhere on Route53.
I made sure that the NS entries for my root domain – example.com – pointed to the Name servers entries on my registered domain in Route53.
You can find the name servers associated with your Route53 registered domain by going to Registered domains > mydomain.com; they're located on the upper-right corner.

Trouble getting domain name associated with AWS to point to Heroku app

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.

Custom client domains for my web service

I have a web service running on EC2 behind an elastic balancer. I would like to allow my clients to point their A record to my web service so they could have their domain on my server. Similar to shopify or github pages.
However, I don't want to give them the IP of the web service, I'd like the request to go though the load balancer. How can I achieve this? Should I create a small server to forward requests? How does that work?
Many thanks!
If you are running your service behind an Elastic Load Balancer, you usually do not want to use ELB DNS name (which is something like your-service-ELB-1122334455.us-east-1.elb.amazonaws.com). Instead you will configure (probably using Route53, but any DNS service will do) CNAME or ALIAS record with some friendly name, like yourservice.yourdomain.example (this way, name will be easier to remember, and you have the freedom to change load balancer if needed).
All your customers have to do is to create CNAME DNS record pointing their name to your friendly service DNS name, like:
foo-service.theirdomain.example CNAME yourservice.yourdomain.example.
You also need to be aware that HTTP requests will have Host: header containing name entered by user (in case your server/service relies on that info)
You need to consider using Route53 as your clients's DNS service provider might not be supporting this feature beacuse of DNS rule.
See s3.6.2 of RFC 1034
Amazon created a new aliasing system for Route 53. You can now map the apex of a hosted zone to an Elastic Load Balancer using an Alias record. When Route 53 encounters an Alias record, it looks up the A records associated with the target DNS name in the Alias, and returns the IP addresses from that name.
In order to allow all of our customers to benefit from this new feature, there is no charge for queries to alias records when the target is an Elastic Load Balancer.
Associating Your Custom Domain Name with Your Load Balancer Name.
You can also create a Subdomain That Uses Amazon Route 53 as the DNS Service without Migrating the Parent Domain.

How to use Route 53 and VPS service of aws to run my website?

I have my domain name in godaddy's account. And I want to host that site on aws.
So for that I have created the EC2 instance and it is working fine with the public address they have given
http://ec2-23-20-10-132.compute-1.amazonaws.com/
I want to open the same thing with my domain name. How can I do that.
Need more context on this. Does Route 53 already have control of your domain name?
If your domain is in Route 53 and the NS (nameserver) values are using AWS name servers, then the process of routing your EC2 enviornment to your domain is quite easy.
In that case, all youll do is a create an A-level record set with the alias target of your raw EC2 url. Normally you set your A-level record set to be DOMAINNAME.com ...
After that, for posterity and canonical redirect purposes--you'd create a CNAME record for www.DOMAINNAME.com...this could point to your A-level record set of DOMAINNAME.com...
Hopes this helps!
Make sure your web server responds on domain.com
Point your DNS record (root records and/or www record) to the web server I.P