openresty.org DNS issues (dnspod.com)

[GUI]

Over the past couple day's I've been experiencing intermittent problems when trying to download the openresty-1.9.15.1.tar.gz package. The problem seems to be that my DNS sometimes can't resolve the openresty.org domain name. After running a few tests, I'm also seeing DNS resolution errors or slowness from other internet connections, so I don't think it's just me.

It looks like the issue is likely on the end of the nameservers openresty.org uses (dnspod.com), so this might not be in your control. But since I believe I've been seeing these DNS issues for the past couple days, I thought I'd let you know.

Here's a couple example results from external DNS checkers:

https://www.ultratools.com/tools/dnsLookup: Timeout

http://mxtoolbox.com/DNSLookup.aspx: Succeeds, but took 20 seconds

[agentzh]

@GUI Thanks for the report. DNSPod's service is known to be unstable. I'll try looking for a better alternative. Alas.

[GUI]

Thanks!

Any reason not to use CloudFlare for DNS? Or since it looks like you're on AWS, I've also had good experiences with Route53 there. But there's obviously a ton of other options too. In any case, thanks for looking into it.

[agentzh]

@GUI openresty.org's DNS requirements are a bit complicated. The alternatives you mentioned do not quite work for this site, unfortunately. I've tried them before.

[GUI]

Gotcha. I don't know all the requirements, but I completely understand it being more complicated.

For a bit more context, this primarily affects me when using configuration management tools (like Chef) to download and install openresty on new servers (or upgrading old servers). Since these scripts currently try to download the different versions directly from the openresty.org site (eg, https://openresty.org/download/openresty-1.9.15.1.tar.gz), when the DNS begins to fail (as is happening for me again right now), this causes our server provisioning to fail when we need to change openresty versions.

We can definitely look into mirroring the download files internally to solve the issues on our end, but I was wondering if there were perhaps any other public mirrors for the downloads out there already. If not, had you considered mirroring the download files in other locations if the DNS issues are a bit of a known issue? Perhaps uploading them as github releases would offer another mirror, or exposing an S3 bucket directly on the default amazonaws.com domain would be another option? Although, both might complicate the release process or other things on your end, so I'm not sure if those would be ideal either.

Thanks!

[agentzh]

@GUI Good suggestion! I've uploaded the latest 1.9.15.1 release to GitHub:

https://github.com/openresty/openresty/releases/tag/v1.9.15.1

I'll always upload to both openresty.org and github for formal releases from now on.

Regarding the DNS server, yes, I'm also sick of it. I'll switch away from dnspod soon.

[GUI]

Perfect, thanks so much!