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 个月前

您未登录。 登录 发布回答。

一个好的回答可以清楚地解答问题和提供建设性反馈,并能促进提问者的职业发展。

回答问题的准则