Curl fails to resolve hostname

[notEvil]

Hi,

I'm facing a DNS issue which is probably not related to Nextcloud AIO but I don't know where else to put it. Since October 16th my logs are full of

ConnectException cURL error 28: Resolving timed out after 5000 milliseconds (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://nextcloud.my.domain/hosting/capabilities
Failed to fetch capabilities: cURL error 28: Resolving timed out after 5000 milliseconds (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://nextcloud.my.domain/hosting/capabilities

from richdocuments. curl https://nextcloud.my.domain/hosting/capabilities on the host works just fine and I have no other issue with Nextcloud, including Nextcloud Office (maybe relevant: IPv6 only, no A record). My investigation so far revealed something odd:

The first execution of curl -I -6 'https://nextcloud.my.domain/' within sudo docker exec -it nextcloud-aio-nextcloud bash responds with http 302 as expected. All subsequent executions within the domain TTL window return curl: (6) Could not resolve host: nextcloud.my.domain. Monitoring the network with sudo tcpdump -i br-121afda26548 'port 53' on the host shows dns requests and responses, a single request response pair for the succeeding curl and 3 pairs for the failing ones, all with the correct response.

I'd highly appreciate any hint towards a solution, but don't expect any :)

[szaimen]

Hi, I fear this is most likely caused by an upstream change in the alpine image that we use internally. You might want to add a comment here: https://gitlab.alpinelinux.org/alpine/aports/-/issues/15690 or create a new issue here: https://gitlab.alpinelinux.org/alpine/aports/-/issues

[Rob-Geebivi]

I'm likely having the same issue as @notEvil...
From that same issues-15690 link, it appears a patch was merged into the 3.20 branch of Alpine, based on comments on https://gitlab.alpinelinux.org/alpine/aports/-/issues/15690 by DerLinkman on October 15th. Can this update to Alpine be included with the next AIO update to hopefully fix the issue?

[Rob-Geebivi]

To clarify my comment: I was referencing the update of the 3.20-stable git branch of Alpine that included the update to c-ares to 1.33.1 (which should supposedly fix the issue), which was done on Sep 27th. (https://gitlab.alpinelinux.org/alpine/aports/-/commit/e0e2025ea57e73d16c78170938d21c92f509a504)

I thought there was a compiled patch available right now, but it appears that the last minor patch release of Alpine, 3.20.3, was done on Sep 6th, and therefore does not include the desired fix.
Given that, it looks like the most realistic solution requires patience until Alpine 3.20.4 and/or 3.21 are released and can be incorporated into AIO.

According to Alpine's website (https://alpinelinux.org/releases/), they aim to release a major version each November, so hopefully it's not too long before it would be available to start working with. I know integration with AIO has the potential to generate its own complications, but for what it's worth, I guess you can consider this a preemptive request to update the base Alpine package used with AIO to (the not yet released) v3.20.4 or above at your earliest convenience. ;)

[szaimen]

I guess you can consider this a preemptive request to update the base Alpine package used with AIO to (the not yet released) v3.20.4 or above at your earliest convenience

Sounds good!

[szaimen]

It will automatically be includes as soon as the base image we are using is updated