Hosterlabs ipv6 only VPS unable to resolve Github.com
Hi
i took a ipv6 only VPS from hosterlabs during the BF sale .
I am on Debain 10 and I can open/ping all other ipv4/ipv6 websites except github.com
github.com shows
github.com has address 140.82.121.3
github.com has IPv6 address 64:ff9b::8c52:7904
My resolv.conf has
nameserver 2001:4860:4860::6464
nameserver 2001:4860:4860::8888
nameserver 8.8.8.8
But i cannot access github.com . Hosterlabs have not helped, I have created tickets also
Google search also reveals that github has not activated ipv6 but its shows an ipv6 address so .......
Can anyone pls guide me on this
thanks
Comments
i have tried from my other ipv6 vps and i can't connect to github either
https://github.community/t/cannot-reach-any-github-io-page-via-ipv6/10310
so the problem lies with github not hosterlabs.
ThemeForest Profile
ok
so cleared
thanks
You need a NAT64 gateway.
64:ff9b::8c52:7904 is a NAT64 address.
From: https://developers.google.com/speed/public-dns/docs/dns64
The all seeing eye sees everything...
I was trying to install PiHole , even that cannot be installed as it cannot resolve https://pi-hole.net/
let me check that out
thanks
Github does not support IPV6. Maybe try using tunnel?
Most tunnels are ipv4 to ipv6 , can i do ipv6 to ipv4 through any specific tunnel ?
can u check https://pi-hole.net/ also
I cant install pihole
Haven't tried anything yet since my ISP (and half of the country) does not support IPv6. Maybe Wireguard server on VPS with IPv4+6 available can work?
My broadband doesn't have native ipv6 but mobile data does have
So on broadband going through wireguard to access ipv6 VPS but still same errors
Not able to resolve github and pihole is bummer for now
Either a NAT64 or vpn to a dual stack vps
The all seeing eye sees everything...
NAT64 will try but dual stack has to be on Hosterlabs end right ?
Try using vultr with IPv6 enabled to test it
Dont have vultr
Any machine on any hosts. Don't have to be Hosterlabs.
The all seeing eye sees everything...
can't reach it too.
ThemeForest Profile
Try replacing github.com with
2a04:4e42::133which is fastly's ipv6 (GitHub uses fastly's CDN).Swap your DNS to use these resolvers - https://nat64.net/
They take IPv4-only hostnames and proxy the traffic through a public NAT64 gateway. It's slower than a direct connection but gives you enough v4 connectivity to do most stuff.
🦍🍌
Did not work
SSL: certificate subject name (www.github.com) does not match target host name '2a04:4e42::133'
Updating for Posterity
Tried - https://go6lab.si/current-ipv6-tests/nat64dns64-public-test/
nameserver 2001:67c:27e4:15::6411
nameserver 2001:67c:27e4::64
Was not able to resolve both github and pi-hole.net
Failed to connect to install.pi-hole.net port 443: No route to host
Swap your DNS to use these resolvers - https://nat64.net/
Worked perfectly
Will keep checking and updating this
This worked perfectly to resolve both github and pi-hole.net
NAT64 is one method, but most public servers are in EU, so the speeds won't be good from Hosterlabs Canada.
If you happen to have a dual stack server nearby (e.g. Gullo Canada), you can try the VXLAN method in my newly posted tutorial: Enable IPv4 Access in EUserv IPv6-only VS2-free.
Accepting submissions for IPv6 less than /64 Hall of Incompetence.
Hello,
I am sorry about that. I did not see your thread. This was indeed brought to our attention by a support ticket. I believe we already had tried nat64, which was the first step. But if that did not work, sadly, without IPv4 there would be no solution.
So I think I proposed adding an IPv4 or you can indeed do a VXLAN through Private IP's that we support as long as servers are on the same node. Natting or adding VXLAN requires more knowledge and sadly we do not yet provide support on how to do it.
We are working on guides to teach how to NAT or maybe in this case VXLAN (a method i did not know ) through our internal networks.
Sorry to hear some sites are inaccesible, but we can not do much rather than providing an IPv4 (with additional cost) or using another VPS with an IP...
The main idea behind this promotions was for customers to have a main node with IPv4 and IPv6 on the top (which load balances) and then routes all services to IPv6 nodes in a scalable way. So one vm for MySQL, one for apache, and so on… So services lie on the back and thus reduce the "ipv4 footprint"
I dont have any other server at same node . I do have another VPS with another provider with ipv4, so will try VXLAN
My requirement of ipv4 was only for github and pihole script which i was able to do it with NAT64 free providers .
But issue is with Github and pi-hole.net remains
And I am not able to run Wireguard properly with Nyr script https://talk.lowendspirit.com/discussion/comment/51017/#Comment_51017 . Even tried it with other instances of wireguard also but faced same issue
Which works properly with the other VPS which has ipv4 and ipv6
Usually people use Pi-hole because it blocks ads, not because it's challenging to be installed on an IPv6 only VPS.
Anyhow, take a look at https://nextdns.io/. You might find it interesting.
Whats the fun if not challenging ?
Google will keep this thread for posterity