First, thanks so much for taking time reading this question. I am new on linux, and I need some guide.
I basically have a Ubuntu 18 server (AWS EC2). I have the static public IP address and the domain name from godaddy.
The thing is that I am not being able to access my server from the internet using the domain I bought on godaddy. The only way I have to access this server is using the IP Address...
Maybe you can help me answering these questions:
I think that nothing should be done on AWS EC2 to accept my new domain. right?
Is it enough to have just a "A" record on DNS configuration on Godaddy?
Finally, what configuration should be done on Ubuntu 18?
When enter "hostname" I get --> "server1"
When enter "hostname --fqdn" I get --> "XXXX.com" (the domain I bought on godaddy)
When enter "dnsdomainname" I get --> "com"
Could you please tell me what I am doing wrong? I just want my webpage to be accessed by everybody on the internet...
Thanks In advice! :)
I am not sure what you mean by static IP address from GoDaddy the domain name makes sense.
Normally you would want to attach an ElasticIP address to your instance as the public IP that it is assigned will change when the instance reboots. Then you configure the A record in the GoDaddy domain to point to the EIP address, the TTL is normally about 10 minutes for the DNS to reflect so be patient. (This should be enough).
If it still not working after some time you make sure you have an IGW (internet gateway) attached to the VPC and your Security groups and NACLs allow inbound and outbound traffic.
Related
I have first reboot the instance. After that when I tried to access instance with domain name, it's not accessible.
I can access with elastic ipaddress (whm and cpanel both i can access with ip address) but with domain name, i am not able to access.
Help me to resolve it.
Can you ping the domain to check if it returns the actual IP address of the server?
ping domain.com
Let me know if it returns the correct IP, otherwise there must be something wrong with the DNS. Or most probably your DNS server is down or misconfigured entries. If you're using Cloudflare or any other 3rd party DNS provider, then you need to turn of proxy bypass for the domain in order to access the server directly through domain name.
Later on found that I have increased instance with cpanel with public ip address instead of using elastic ip address...
Basically it issue regarding ip address only.
After that I have created new instance with cpanel Linux and installed cpanel with elastic ip address, in that case after rebooting this issue didn't happen again. Btw it solved.
I have bought a domain name from GoDaddy and would like to host it on an EC2 instance. I have created the instance and have installed apache. I have added an index.php with phpinfo(); and it is showing correctly when I access the public IP on browser. Now I would like to point my domain name to this instance. For this I have added an A RECORD at Godaddy DNS configuration. But when I access the doamin, it is showing
ERR_CONNECTION_TIMED_OUT
message in the broswer. Is there any additional settings I need to do ?
What you did is what it is needed. SO if it is not working then then you have to check everything again :
- check (for example with ping) if the domain is in fact resolving to correct IP address (from your computer and from instance for example to use different DNS servers). You can also use host command (for example host www.mydomain.com 8.8.8.8 - it will use google's dns (8.8.8.8) as the source of truth
- check if Security Group in aws allows inbound traffic (that's probably true as you can reach the instance directly)
- try to connect from different network (again this should not be problem as IP is reachable using IP).
you can also post the domain name and requested Ip so we can check this for you ;)
I have a specific DNS problem for my website - I can access my website using its static ip address but not its domain name. Here's a description of my situation:
I registered a website name, say, "xxx.com", at GoDaddy.com, but the web app is hosted on a AWS lightsail Ubuntu instance with a static ip;
In the "DNS Management" page of this same on GoDaddy.com, I specified custom name servers as those provided by AWS
On AWS Lightsail, I then created an "A" DNS record that maps "xxx.com" to the ubuntu instance's static ip: "A" - "xxx.com" -> "x.x.x.x"
I was able to reach my website using "xxx.com" last night, but after rebooting the Ubuntu instance this morning, the domain name is unreachable while the website can still be accessed using its ip address
I have 2 questions -
How would AWS' name servers know that I am the rightful owner of this purchased domain name "xxx.com", by allowing me to map "xxx.com" to a certain ip address?
Did I miss something during the process above that made my website unreachable today using "xxx.com"? Why was it working yesterday but not today??
Any thoughts would be appreciated. Thanks in advance!
I can now partially answer my own question #2, and the answer is DNS propagation.
When DNS changes are made, it might take up to 24 hours for the DNS changes to take effect across the internet. Both name servers and one's local DNS cache will need to refresh first before receiving newly changed DNS records.
I have a domain registered at godaddy but want to have webhosting at AWS Amazon. As per the instructions, updated the 'A' record with Elastic IP of AWS. But the website is down and not able to connect. Thanks in advance for any help. Am I missing anything on AWS EC2 VPC? I am not using Route 53 since this is not required as per AWS documentation.
please check your application should hosted in port 80. Can you able to access your application IP:80 from browser..?
Please check the port you are running your application on. If your domain name is somexyz.com and your port is other than 80 (standard TCP port for HTTP service) like 5000 for default Flask werkzeug dev server, you will have to type somexyz.com:5000 on the browser to access your website. Otherwise run it on 80. The stackoverflow discussion here- create a domain name pointing to an IP of port different than 80 should help.
(Also, this may be irrelevant now but the TTL field~600secs etc on godaddy reflects avg time for DNS records to get updated when we edit zone info 'A' field to point to Amazon Ec2 Elastic IP. So waiting for upto an hour or so helps.)
I have a simple question for pointing my Bigrock Domain name to Amazone EC2.
I have Created HostedZone from Hostedzone-create link
I got 4 name servers.
Now what?
Suppose my domain name is example.com on Bigrock.com.
Can anyone explain me how can i point that domain name to EC2?
I asked to Bigrock support but they told me something like this:
The website is not working because the DNS zone for your domain is not
configured properly on your Hosting providers DNS servers ( AWS Server
). Please get in touch with your provider for further assistance.
But I am not getting what they want to say. Please help!!
To move your Name Servers to AWS Route 53 first you have to change the Name Servers in Bigrock follow this steps.
http://support.hostgator.com/articles/hosting-guide/lets-get-started/dns-name-servers/how-to-change-name-servers-with-bigrock
Once that is done go to AWS Route 53 and create two record sets one for the "naked domain" and another for "www" domain and add a A-Record to point to the EC2 IP address (Be Sure the IP address is Elastic just in case for future change in IP address of the server so that you are covered).
This is Route 53 Guide
http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resource-record-sets-creating.html
Now, you will go to your bigrock.com and find your domain. Change the default name servers information with that 4 name servers information provided by Route53 on amazon. save your changes and wait for few hours to be activated properly.