- Newest
- Most votes
- Most comments
Hi,
If you have IPv6 connectivity from ISP and if this sometimes works, sometimes stop working and you are using Windows box, most likely the issue is that IPv6 addresses is lost after some time.
After digging a lot in that case, I've found out that network settings needs to be set to Private Network, a specially on Windows 10 boxes, and Windows 11 looks that this fixed but not always, so this is first option what I suggest to try.
Thanks,
Hi,
I've just tested, DNS is fine also EC2 is fine, Apache responding:
> demo-cloud.safetynetscreening.com
Name: demo-cloud.safetynetscreening.com
Address: 2600:1f16:2d5:ffb3:cd81:2118:fe1:51a0
Both telnet working, over IPv6 and also over DNS
telnet 2600:1f16:2d5:ffb3:cd81:2118:fe1:51a0 80
telnet demo-cloud.safetynetscreening.com 80
Do you have IPv6 connectivity from where you are planning to connect? It's mandatory that you have IPv6 from where you connecting, if IPv6 is not present this won't work. To check your ipv6 connectivity you may use:
If this fail for IPv6, you won't connect to IPv6 instance.
Thanks,
First of all thank you for getting back so quickly, Just one more thing is this a problem with my local setup or the connectivity issue comes from the ISP. If you can share any knowledge related to this that would be very much appreciated
Relevant content
- asked 6 months ago
- asked 2 months ago
AWS OFFICIALUpdated 2 years ago- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
Hey, from the flow looks like you are not able to resolve a domain. The error
DNS_PROBE_FINISHED_NXDOMAINindicates that the domain is non existent.Can you share more details about the domain (keeping in mind it is a public forum so don't share anything which shouldn't be public), like is it for a private hosted zone in Route 53. If yes, is it associated with the VPC and so on.
Edit: Adding some links for DNS and IPv6 on AWS
https://docs.aws.amazon.com/whitepapers/latest/ipv6-on-aws/designing-dns-for-ipv6.html#private-dns-resolution https://docs.aws.amazon.com/whitepapers/latest/ipv6-on-aws/designing-dns-for-ipv6.html#dns-resolution-within-a-vpc
Hi Ashish_K sure here are the details we first tried under godaddy and then i set up the dns on cloudflare domain: safetynetscreening.com Record details: Type: AAAA name: demo-cloud content: 2600:1f16:2d5:ffb3:cd81:2118:fe1:51a0 proxy status: DNS only ttl: 5 min
Also if try to ssh to the instance from another EC2 instance in the same vpc i'm only able to reach it when using IPv4
Let me know if need more details thanks
Hi,
What kind of oprating system do you use as AMI? The error comes from EC2 or from outside? If from EC2, what kind of system do you use?
Thanks,
Hi Marcin, We use Ubuntu 22.04.1 LTS (GNU/Linux 6.2.0-1017-aws x86_64) as the OS for the EC2 instance, our guess is that the error is coming from the instance.