OpenResty.org inaccessible on any host that has IPv6 enabled

[Paul Buonopane]

openresty.org currently has a bad AAAA record; any HTTPS requests to it time out.  This prevents IPv6-enabled hosts from falling back to IPv4 in a timely manner, and some are completely unable to connect.

Currently, I'm using Chrome on a laptop that has both IPv4 and IPv6.  Attempts to visit openresty.org usually time out after a few minutes; sometimes, Chrome will fall back to IPv4, but it takes a while.

Servers attempting to use the OpenResty APT repo also fail to pull updates if they're configured to prefer IPv6.

I opened a bug on GitHub as well: https://github.com/openresty/openresty.org/issues/255