- 新しい順
- 投票が多い順
- コメントが多い順
Did you update your domain by adding an entry like an A record that points the the EC2 instance IP?
www.mydomain.com A 3.9.243.78 for example?
Also I would recommend that you place the server in a private subnet (within your VPC) and then have a load balancer to direct traffic to your instance. This will provide some security for your instance as it won't be accessible from the outside directly.
You can learn more about this setup from the VPC User Guide example - https://docs.aws.amazon.com/vpc/latest/userguide/vpc-example-private-subnets-nat.html
Hope this helps.
Hi
As the website is accessible via the IP, we can eliminate any network issues relating AWS. Assuming that the A record on your hostinger is configured and pointed to the IP 3.9.243.78. Could you please verify that this record is configured correctly? -> https://support.hostinger.com/en/articles/4468886-how-to-manage-a-records-in-hpanel
Also, note that sometimes the DNS records can take up to 24 hours to propagate.
Even I'm facing exactly same problem. I have added the A record with ip address. I'm able to access my website using Ip address but not through domain name. Can someone please help. I think this problem is specific to hostinger domain names.
関連するコンテンツ
- AWS公式更新しました 1年前
Even I'm facing exactly same problem. I have added the A record with ip address. I'm able to access my website using Ip address but not through domain name. Can someone please help. I think this problem is specific to hostinger domain names.