Public IPv4 DNS not accessible

0

Hi, without changing anything to my instance settings, all of a sudden, the public IPv4 DNS became not accessible. I can SSH fine, I have a wireguard tunnel setup between the EC2 and a router and the tunnel works (i pinged in both directions and it worked), I don't understand what happened.

jbouget
已提問 2 個月前檢視次數 207 次
2 個答案
2

Unless you use a purchased elastic IP which is assigned to a EC2, the. Public IPs change when you stop and start an instance.

Double check and confirm if the public IP dns name has now changed.

profile picture
專家
已回答 2 個月前
profile picture
專家
已審閱 2 個月前
0

Hello,

As you didn't change anything on the instance directly, there might be some networking problems. The first problem you might encounter is that you have a security group, which means you cannot reach your instance. The second reason that caused this is that you have changed some settings on the VPC that do not allow any Public IPv4 DNS addresses.

Here is the link to the VPC DNS Hostnames: https://docs.aws.amazon.com/vpc/latest/userguide/vpc-dns.html

Another user also had a similar problem https://repost.aws/questions/QUHr9s-6NkQDmsjEP9M6ttWw/cannot-reach-ipv4-public-ip-or-public-dns-ipv4

profile picture
Julian
已回答 2 個月前
profile picture
專家
已審閱 2 個月前

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南