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:
- an A record set with my domain and the elastic ip address
- an automatically assigned AWS NS record
- 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 2 I have deleted the 1 hosted zone and created a new: now it looks like this: