Whether you're taking your first steps with Kubernetes or you're an experienced practitioner looking to sharpen your skills, our Amazon EKS workshop series delivers practical, real-world experience that moves you forward. Learn directly from AWS solutions architects and EKS specialists through hands-on sessions designed to build your confidence with Kubernetes. Register now and start building with Amazon EKS!
Public IPV4 DNS Address On a Particular Local Zone NOT pingable
Hi, my very first time posting here, and I'm not a native English speaker, so I hope you will be gentle.
The background of MY issue:
- I created a subnet on a Local Zone for a particular region
- I launched an instance on the newly created Local Zone
- It was auto-assigned with a public ipv4 address - it is pingable
- it was auto-assigned with a IPv4 DNS name of ec2-123-123-123-123.ap-southeast-1.compute.amazonaws.com - NOT pingable
- I launched another test instance, but this time, on the particular region that the local zone belongs to, the assigned Public IPv4 DNS name is pingable
What could be the problem here? Where to look into?
Edit, additional info: I missed to include the detail that I have configured the security group and allowed all ports to open -- for the sake of testing. Where all ports 0-65535 tcp/udp are open for inbound, along with All ICMP IPv4 open.
I also made sure Enable DNS resolution and Enable DNS hostnames were enabled before launching the test instances. See my screenshot of the details below.
And to mention again, the parent Region for the particular Local Zone has no IPv4 DNS name issue.
There is a working route to the default IGW (configured by AWS upon enabling the region):
- Newest
- Most votes
- Most comments
Hello.
Is there a route to the Internet gateway set in the route table of the subnet where you started EC2?
Also, does the security group's inbound rules allow ICMP?
By the way, are "DnsHostnames" and "DnsSupport" enabled in the VPC?
I think these settings need to be enabled to use the public DNS hostname of the EC2 instance.
https://docs.aws.amazon.com/vpc/latest/userguide/AmazonDNS-concepts.html#vpc-dns-support
Relevant content
- asked 2 years ago
- AWS OFFICIALUpdated 6 months ago
Ah yes, thanks for asking, and sorry I missed to include the detail that I have configured the security group and allowed all ports to open -- for the sake of testing. Where all ports 0-65535 tcp/udp are open for inbound, along with All ICMP IPv4 open.
I also made sure
Enable DNS resolutionandEnable DNS hostnameswere enabled before launching the test instances. And to mention again, the parent Region for the particular Local Zone has no IPv4 DNS name issue.There is a route to the default gateway provided by AWS. And to mention again, I can ping the Public IPv4 IP address, but NOT the Public IPv4 DNS Name.
Is it possible to resolve public IPv4 DNS names using the "dig" command?
dig and nslookup both reported:
connection timed out; no servers could be reachedIt seems that DNS name resolution is not working properly. Is it possible to perform name resolution by pointing the DNS server to google as shown below? If this is successful, I think there is a problem with the DNS server used by your local PC.
Result:
Not resolving to IP address.