route53 domain name is not connecting with my ec2 elastic ip

1
votes

I'm running an ec2 instance. If I ping the instance based on its elastic IP I get a response. If I use my registered domain I can not access that elastic IP address anymore. In Route 53 (under the DNS Management) I have 1 hosted zone with 3 record sets:

  1. an A record set with my domain and the elastic ip address
  2. an automatically assigned AWS NS record
  3. an automatically assigned AWS SOA record

So, basically the only entry I added was the A (that corresponds to the name of my domain and the elastic IP address as a value. Not sure why it's not binding.

My ec2 instance has no firewall and for the time-being both (the inbound and the outbound) sections of my aws firewall are set to "all traffic".

when I use a domain validator I do not get anything back. It behaves as if the domain did not exist. The domain was created over a year ago (so this is not a new domain). I checked in the dash-board and as far as I can tell all the information (contact info, verification info) looks fine.

Furthermore, the "test-record" feature in the Route 53 does return the IP address on a "UDP" port.

What am I missing? Do I need anything else?

Edited enter image description here

enter image description here

Edited 2 I have deleted the 1 hosted zone and created a new: now it looks like this: enter image description here

1
amazon-web-servicesamazon-ec2amazon-route53
What is the domain? – Michael - sqlbot
Check this – Dusan Bajic
@DusanBajic , thank you for the link. The domain has been purchased on AWS. – Nactus
@Nactus, still, follow the steps (you have configured the wrong name servers, it can be seen in your pictures) – Dusan Bajic

1 Answers

3
votes

If you bought the Domain from other than AWS then you need to manually update its name server from their portal (godaddy,etc).

So this is how it goes in case of others:

create a Hosted Zone in Route53 which you already did

NS and SOA records will be auto-generated however, it's important to note that the auto-generated NS will NOT update the domain's NS automatically. You need to update it manually

Add A records as shown in image below Route54 config

Then go to your domain portal and change DNS, use auto-generated DNS from Route53

Changes will be refreshed as per your selected TTL but it usually updated in 5 mins

OR

If your Domain provider gives you the access to setup records in their portal then you can skip all the above steps and simply create A record there with your elasticIP to point your domain to ec2

EDIT

As you can see in picture nameservers mentioned on the top right corner of the image are different than your record NS, your NS records are wrong. It's better that you delete this hosted zone and create new Public Hosted Zone. You will get new NS after creating a Hosted Zone then just go to domain editing and update nameservers with the new one on domain.