ppa.launchpad.net not accessible via IPv6
Bug #1287803 reported by
John Leach
This bug affects 17 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
Low
|
Unassigned |
Bug Description
ppa.launchpad.net is used for ppa repositories but it's not IPv6 enabled:
$ dig -t aaaa ppa.launchpad.net
; <<>> DiG 9.9.3-rpz2+
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 27044
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;ppa.launchpad.net. IN AAAA
;; Query time: 1 msec
;; SERVER: 127.0.1.
;; WHEN: Tue Mar 04 17:01:34 GMT 2014
;; MSG SIZE rcvd: 35
Any chance this can get fixed (as per #241305 :)
affects: | ubuntu-website → launchpad |
Changed in launchpad: | |
status: | New → Triaged |
importance: | Undecided → Low |
tags: | added: feature ipv6 lp-soyuz ppa |
To post a comment you must log in.
I am running multiple labs on an IPv6-only network. The only service I really need that does not work in this environment is Launchpad. While it would be technically possible to set up a proxy server or a NAT64 box, this would not be without cost for me. Besides that: I am involved with many ISPs and enterprises that are looking at the usability of IPv6-only networks, and this is a blocker.
I would really appreciate it if Launchpad would be reachable over IPv6.
Especially since e.g. even Facebook is working on IPv6-only data centres these days (https:/ /www.dropbox. com/s/8n8txdzy3 8yclj6/ day_2_7_ paul_saab. pdf). IPv6 is necessary for production use.