Associate Amazon EC2 instance with my own domain

0
votes

I tried to deploy a node project into an Amazon EC2 instance and associate it with my own custom domain yesterday.

The application works fine by using public DNS that is offered by EC2. I updated the nameserver of my domain, added domain name and public IP address into Route 53. I tried dig invia.ca command in the terminal, but nothing changed.

domain nameserver

route 53 setting $ dig in-via.ca

Domain name: in-via.ca
Domain status: registered
Creation date: 2017/03/27
Expiry date: 2018/03/27
Updated date: 2017/04/28
DNSSEC: Unsigned

Registrar:
Name: Web Hosting Canada (7081936 Canada Inc.)
Number: 5000080

Name servers:
ns-1350.awsdns-40.org
ns-1824.awsdns-36.co.uk
ns-744.awsdns-29.net
ns-315.awsdns-39.com

% WHOIS look-up made at 2017-04-29 03:36:40 (GMT)
1
amazon-web-servicesamazon-ec2amazon-route53
Take a look at stackoverflow.com/questions/43106716/… - it's not always obvious how to use Route 53. – stdunbar
@Allen -- I've added the current dig output. Is that what you're getting? What do you want to be different? – John Rotenstein
@JohnRotenstein it suppose to display the four nameserver address I entered above under authority section and additional section? and u missed '-' between 'in' and 'via' too.. – Allen Dun
in-via.ca is now resolving to 35.163.97.40 so the DNS looks okay now. – John Rotenstein
@JohnRotenstein yes it's working now thx indeed. i changed nothing. My previous setting is correct. I cannot believe it really takes around 24 hours to get nameserver updated. jesus crist! But currently I have to add ':8080' behind the www.in-via.ca in order to view the website. Do u know how can i get rid of it? – Allen Dun

1 Answers

0
votes

Try dig NS in-via.ca. You need to update the name servers at your registrar (Web Hosting Canada, according to WHOIS). You can see that AWS has the correct info with dig @ns-315.awsdns-39.com in-via.ca.