route53 domain name is not connecting with my ec2 elastic ip


route53 domain name is not connecting with my ec2 elastic ip



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:



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





What is the domain?
– Michael - sqlbot
Jun 29 at 23:21





Check this
– Dusan Bajic
Jun 30 at 11:16





@DusanBajic , thank you for the link. The domain has been purchased on AWS.
– Nactus
2 days ago





@Nactus, still, follow the steps (you have configured the wrong name servers, it can be seen in your pictures)
– Dusan Bajic
2 days ago




1 Answer
1



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


Domain


AWS


name server



So this is how it goes in case of others:



create a Hosted Zone in Route53 which you already did


Hosted Zone


Route53



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


NS


SOA


NS


NS



Add A records as shown in image below
Route54 config


A



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


DNS


Route53



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


TTL



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


A


elasticIP


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.





We don't yet have enough information to know whether this is the solution.
– Michael - sqlbot
Jun 30 at 1:05





@Michael-sqlbot yes you are right but I used to miss the point of updating DNS record on domain provider website. So I thought this might be an issue
– UsamaAmjad
Jun 30 at 1:10





@ UsamaAmjad, thank you for taking the time to answer. Upvoted. My domain was purchased through AWS about a year ago. The domain is in good standing with AWS - according to their dashboard.
– Nactus
2 days ago





My setup is very similar (with the exception of the "www.<domain_name>.com". I figured for a simple "ping" test from the console - the www would be irrelevant. I can ping the elastic ip but the domain does not respond. I will edit my main post and share a screen capture with the records
– Nactus
2 days ago






@Nactus Your NS records are wrong, as you can see in picture name servers mentioned on the top right corner of the image are different than your record NS.
– UsamaAmjad
2 days ago


NS






By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Comments

Post a Comment

Popular posts from this blog

paramiko-expect timeout is happening after executing the command

paramiko-expect timeout is happening after executing the command Can someone help me why timeout is happening after executing the command .I am trying to SSH to a machine and execute a command.I want to store the result of the executed command . I have referred paramiko-timeout but i didn't get my expected result. import traceback try: import paramiko except ImportError: raise Exception("Please install paramiko , pip install paramiko") import pexpect from paramiko_expect import SSHClientInteraction def main(): HOSTNAME = "minion5.net" USERNAME = "root" PASSWORD = "help@432" PROMPT = "root@*:~$s+" try: client = paramiko.SSHClient() client.load_system_host_keys() client.set_missing_host_key_policy(paramiko.AutoAddPolicy()) client.connect(hostname=HOSTNAME, username=USERNAME, password=PASSWORD) with SSHClientInteraction(client, timeout=20, display=True) as interact: ...
Read more

Possible Unhandled Promise Rejection (id: 0): ReferenceError: user is not defined ReferenceError: user is not defined

Possible Unhandled Promise Rejection (id: 0): ReferenceError: user is not defined ReferenceError: user is not defined I have stored data user with AsyncStorage when i want to get it, it renders null in alert and the above error in the console,i don't know why. I can not see why it returns null with user but token all is well profile.js : import React, {Component} from 'react'; import { StyleSheet, Text, View, Image, TouchableOpacity,AsyncStorage} from 'react-native'; import { Container, Content, Header,Right, Left, Body} from 'native- base'; import Feather from 'react-native-vector-icons/Feather'; export default class Profile extends Component { constructor (props){ super(props); this.state = { user: null } } componentDidMount(){ this.fetchData(); } fetchData = async() =>{ let username = await AsyncStorage.getItem('user') this.setState({ user: username }) ...
Read more

Opening a url is failing in Swift

Opening a url is failing in Swift breakpointing inside the callback and logging success shows false. I added itms-apps to my plist: LSApplicationQueriesSchemes and put this in my app delegate: func application(_ app: UIApplication, open url: URL, options: [UIApplicationOpenURLOptionsKey : Any] = [:]) -> Bool { return true } func moreTapped() { let url = NSURL(string: "itms-apps://itunes.com/developer/quantum-productions/id979315877") if #available(iOS 10.0, *) { UIApplication.shared.open(url! as URL, options: [:], completionHandler: {(success: Bool) in }) } else { UIApplication.shared.openURL(url! as URL) } } Are you testing on a real device? – rmaddy Jun 21 at 23:57 I try on a device, get "Cannot Connect to App Store". Device is online ...
Read more