Here are the steps I followed.
I purchased the domain in GoDaddy. I changed the name servers to point to lightsail.
In lightsail, I created a new DNS zone.
Created A record with # pointing to the static ip address.
Created A record with www pointing to the static ip address.
It's been more than 24 hours.
When I access the website with the static ip address, it works fine. But, when I access it from the domain name, I'm getting the below error.
example.com’s server IP address could not be found.
DNS_PROBE_FINISHED_NXDOMAIN
If for some reason you deleted and recreated the domain under lightsail the NS records will change and you will need to update those with GoDaddy.
In case you're trying to access it over https you need to make sure you have opened port 443 in the Lightsail firewall - it is closed by default.
Find it under the networking tab of your Lightsail instance.
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 purchased a domain (expressXXXX.it) in Route53.
After this, I have created a lightsail instance in AWS, and assigned a static ip address to it.
In "hosted zones", i configured as follow, adding only A and CNAME records:
where 99.xxx.xx.x4 is my static ip address.
The url www.expressxxxxxxx.it does not point to my static ip address.
if i ping expressxxxx.it, i can see that it points to 42.525.xxx.xxxx instead of my static ip address 99.xx.xx.xx.
I waited for several hours, but it doesn't work at all.
Thanks in advance for help.
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'm deploying my first app on EC2. I have a domain name registered, lets call it example.com. My ec2 instance has a public ip, lets say, 100.100.100.100. When I got the EC2 instance, I already have a wordpress site installed on it (the blog for my app - blog.example.com). Hitting the public ip directly goes to the blog.
My app is running on the 4000 port of this EC2 instance. I want to assign the example.com domain to this.
I'm using AWS Route 53 for the DNS. I'm clicking on create a record set, where I give the name - www.example.com to the value 100.100.100.100:4000. The type is an IP-v4. However, when I try to assign this, I get the error below:
The record set could not be saved because:
- The Value field contains invalid characters or is in an invalid format.
It's because I've specified the port of the ip in the value. How do I get example.co to point to this app on 100.100.100.100:4000? Thank you for all the help in advance!
Amazon Route53 is a global Domain Name Service (DNS).
DNS services are used to resolve DNS names (eg example.com) to an IP address (eg 100.100.100.100). However, DNS servers do not point to ports on a machine (eg port 4000).
Therefore, to refer to 100.100.100.100:4000, you would use example.com:4000.
I struggle to connect my domain to my ec2 instance, although I have read every post on the internet i could find about the subject:
I am using Route 53 to route my domain to an Elastic IP, which is assigned to an EC2 Ubuntu 13.04 instance. nslookup for the domain from outside shows the Elastic IP address, but returns Server UnKnown.
My setup is as follows:
Domain All four Route 53 delegation set entries added as nameserver,
DNS lookup shows everything is distributed and fine
Route 53: A record sets for domain.com and *.domain.com, pointing to
the Elastic IP
Elastic IP: Assigned to the EC2 Instance
EC2 Instance: Ubuntu 13.04 with LAMP (MySQL disabled), vHost set for
*.domain.com and enabled, added 127.0.0.1 domain.com to etc/hosts file, everything restarted and set up
Entering the Elastic IP or the direct Instance IP works just fine, only use of domain returns "Cannot resolve hostname".
I would really appreciate any help on this.
The EC2 instance and Elastic IP are fine, or else you wouldn't be able to connect with the IP address. The problem is with DNS.
I don't understand how DNS lookup can show everything is fine, but you get "Cannot resolve hostname". That's saying that your local computer cannot convert the name you've assigned to an IP address. That means something is wrong with DNS.
Are you sure that you've registered your name servers with your registrar correctly? You said that DNS lookup says things are fine. If so, then the problem must be in Route 53.
Are you using * as a host name in Route 53? If so, replace it with a simple word (like www) and see if that works.