Mega-cmd-server hangs due to DNS issues

[Domcikas]

Hello,

We run into a problem with Mega-CMD app when running it in a Docker container. The problem is, the mega-get command sometimes hangs indefinitely. Upon further investigation, mega-cmd-server debug logs show errors with Mega DNS servers, or more specifically - ERRCONNREFUSED. See the repeating logs below:

[API:debug: 10:58:58] c-ares info received [API:warn: 10:58:58] c-ares error. code: 11 [API:debug: 10:58:58] Waiting for the completion of the c-ares request [API:debug: 10:58:58] c-ares info received [API:warn: 10:58:58] c-ares error. code: 11 [API:debug: 10:58:58] Unable to get the IP for g.api.mega.co.nz [API:warn: 10:58:58] Retrying cs request in 4 ds [API:debug: 10:58:58] cs Retrying the last request after code: 1 [API:debug: 10:58:58] Req command counts: us0:1 [API:debug: 10:58:58] Error in c-ares. Reinitializing... [API:info: 10:58:58] Using custom DNS servers: 2001:678:25c:2215::554,89.44.169.136,2001:678:25c:2215::559,89.44.169.141,2a0b:e40:3::14,66.203.127.16,2a0b:e40:3::16,66.203.127.14

These logs repeat for hours and days with no end, the only change is the wait time.

Please do keep in mind, that while this process hangs indefinitely, a separate container is able to normally use the mega-get command. Is it possible to prevent the server from hanging indefinitely and either to restart itself or to simply crash? Maybe there is an extra option, that prevents this infinite wait loop and crashes instead?