now gitlab.com (and on other related domains as packages. ci.) domain provides DNS record for type A (IPv4). But not for AAAA (IPv6)
dig gitlab.com AAAA +noall +answer ; <<>> DiG 9.10.2-P3 <<>> gitlab.com AAAA +noall +answer ;; global options: +cmd
I run into this trouble on machine connected only via IPv6. Is there any reason to not allow IPv6 in 2015? Could you provide AAAA record to your DNS and allow IPv6 connectivity?
When I check the whois information of
gitlab.comI can see that the site is hosted on an amazon ec2 instance. So Amazon should provide any ipv6 functionality:
Spoiler: It's very disappointing...
We understand the need for IPv6 and we are working on implementing this on all of our offerings.
Hmm apparently they (Amazon) work on IPv6 since 2011, or earlier,.. :-D. So no one from gitlab team can't fix it, sorry for this.
Status changed to closedToggle commit list
Could this be reopened now that GitLab will be moving to its own infra?