[wp-meta] [Making WordPress.org] #3090: WordPress.org API not accessible over IPv6

[Making WordPress.org]

#3090: WordPress.org API not accessible over IPv6
-------------------------+-------------------------
 Reporter:  deaky        |       Owner:  (none)
     Type:  enhancement  |      Status:  closed
 Priority:  normal       |   Milestone:
Component:  API          |  Resolution:  maybelater
 Keywords:               |
-------------------------+-------------------------

Comment (by ott):

 api.wordpress.org does not have an AAAA RR in the DNS. Therefore, it is
 not reachable over IPv6. This is a problem for hosts that are IPv6-only.
 As a result, the admin dashboard contains multiple errors message and
 (automatic) updates seem to be broken. This decreases the confidence in
 WordPress and can lead to security problems.

 IPv6-only hosts are becoming more important as IPv4 address depletion
 continues and the cost of IPv4 addresses increases. Example of scenarios
 where IPv6-only hosts are deployed today are public web hosting, in
 particular with load balancers or other address translators that connect
 IPv6-only networks to the IPv4 Internet, and internal networks that
 already IPv6-only. IPv6-only networks lower the operational costs and
 complexity for networks that do not need IPv4 and some larger
 organizations have even run out of RFC 1918 address space.

 It's a larger topic but I hope this explanation suffices to justify the
 need for IPv6 connectivity for api.wordpress.org. If the justification
 does not suffice, please contact me via email and I can mention concrete
 example of IPv6-only networks and use-cases in private correspondence. The
 topic has also been discussed in public conferences and it is possible to
 find recordings of presentations that discuss this topic in far more
 detail and also mention concrete use-cases and deployments.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/3090#comment:8>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org