Suspected dns issue with opm

[David Micallef]

Hi folks

We use the docker image with Dockerfile like so:

ARG OPENRESTY_VERSION

FROM openresty/openresty:${OPENRESTY_VERSION}

RUN opm get ledgetech/lua-resty-http \

openresty/lua-resty-limit-traffic

and today started getting an issue in our Gitlab CI pipelines with:

failed to solve: process "/bin/sh -c opm get ledgetech/lua-resty-http openresty/lua-resty-limit-traffic" did not complete successfully: exit code: 6

 

Debugging a little we started to think it was dns

nslookup opm.openresty.org
Server:         127.0.0.53
Address:        127.0.0.53#53

Non-authoritative answer:
Name:   opm.openresty.org
Address: 52.11.111.175
** server can't find opm.openresty.org: SERVFAIL

vs

nslookup npmjs.com
Server:         127.0.0.53
Address:        127.0.0.53#53

Non-authoritative answer:
Name:   npmjs.com
Address: 104.16.92.83
Name:   npmjs.com
Address: 104.16.93.83
Name:   npmjs.com
Address: 2606:4700::6810:5c53
Name:   npmjs.com
Address: 2606:4700::6810:5d53

Though I noticed  the main website seems okay.

nslookup openresty.org
Server:         127.0.0.53
Address:        127.0.0.53#53

Non-authoritative answer:
Name:   openresty.org
Address: 54.183.167.213
** server can't find openresty.org: SERVFAIL

Our build still only working on our workstations because of docker cache.

Is there anybody else having issues today?

[David Micallef]

Good news the pipelines are now working and the dns now works as expected too. So this seems likely the cause.

nslookup opm.openresty.org
Server: 127.0.0.53
Address: 127.0.0.53#53

Non-authoritative answer:

opm.openresty.org canonical name = v2.openresty.com.
Name: v2.openresty.com
Address: 18.138.237.72
Name: v2.openresty.com
Address: 52.220.196.30