3 ms·
Your git repository is not reachable over IPv6 despite publishing a DNS AAAA record: $ curl -v https://git.deuxfleurs.fr/Deuxfleurs/garage/issues * T
by iam-TJ 5y ago
Your git repository is not reachable over IPv6 despite publishing a DNS AAAA record:
$ curl -v https://git.deuxfleurs.fr/Deuxfleurs/garage/issues
* Trying 2001:41d0:8:ba0b::1:443...
* Trying 5.135.179.11:443...
* Immediate connect fail for 5.135.179.11: Network is unreachable
$ dig +noquestion +nocmd aaaa git.deuxfleurs.fr
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 46366
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 2
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; ANSWER SECTION:
git.deuxfleurs.fr. 6822 IN CNAME hammerhead.machine.deuxfleurs.fr.
hammerhead.machine.deuxfleurs.fr. 6822 IN AAAA 2001:41d0:8:ba0b::1
This from an IPv6-only network. Since you publish an IPv6 record our DNS64/NAT64 gateway doesn't get involved hence the IPv4 immediate connect fail.
- superboum 5y agoThanks 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 agoLooks 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
- adrn10 5y agoMy bad T_T My colleagues keep picking on me for this. Now that you, complete stranger, you see it too, I'm feeling obliged to improve the situation!