5 ms·

Thanks for reporting the problem. I just deleted the AAAA entry for this machine. In the meantime, if the result is cached for you, you can pass the `-4` argum

Thanks for reporting the problem. I just deleted the AAAA entry for this machine. In the meantime, if the result is cached for you, you can pass the `-4` argument to force IPv4: git clone -4 git@git.deuxfleurs.fr:Deuxfleurs/garage.git And, in a second time, we will work on a better/working IPv6 configuration for our Git repository and all of our services (we use Nomad+Docker and did not find a way to expose IPv6 in a satisfying way yet).

iam-TJ 5y ago
Looks like the TTL on the records is still affecting local resolution. I'm aware of the git protocol work-around to force IPv4 but that doesn't help when using a regular web-browser to visit the published URL for issues (first thing I evaluate for a new-to-me project): https://git.deuxfleurs.fr/Deuxfleurs/garage/issues https://git.deuxfleurs.fr/Deuxfleurs/garage/issues