When my server tries to sync from "2607:fad0:3404:1::10" it fails, other IPv6 and IPv4 addresses work fine.
Is anyone else have issues syncing from 2607:fad0:3404:1::10 or is it just me?
Thanks, Adam
On 24/05/17 17:11, Adam Ring wrote:
When my server tries to sync from "2607:fad0:3404:1::10" it fails, other IPv6 and IPv4 addresses work fine.
Is anyone else have issues syncing from 2607:fad0:3404:1::10 or is it just me?
Thanks, Adam
Thanks for the notification : our monitoring system has no issue connecting to that node over ipv6, but it's also running from the same continent/country (USA) that this particular host.
So I tried from another of our hosts in Europe (tested from Germany) and I confirm an issue at the ipv6 level itself : seems there is a loop between the involved hops.
Just to confirm : your server is located in .us, right ? (that would explain why our geoip dns would return that ipv6 address from our .us pool back to you)
On 26/05/17 16:57, Adam Ring wrote:
Just to confirm : your server is located in .us, right ? (that would explain why our geoip dns would return that ipv6 address from our .us pool back to you)Yes we are located in the US.
Thanks, Adam
Ok, as that seems an ipv6 routing issue between your server and that node, can you inform your ISP about that ipv6 unreachable node so that they can investigate and eventually reports that to one of their upstream link providers (with a mtr reported maybe included in your report)
Cheers,
-
Adam Ring -
Fabian Arrotin