Suddenly not able to connect to Flow mainnet.

[Ronak-59]

We are running the docker image on AWS ECS and it ran smoothly but now it's giving the following error suddenly:

msg="Error while handling request" error="client: rpc error: code = Internal desc = failed to send transaction to a collection node: 3 errors occurred:\n\t* failed to send transaction to collection node at collection-081.mainnet15.nodes.onflow.org:3569: rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial tcp: lookup collection-081.mainnet15.nodes.onflow.org on 169.254.169.254:53: no such host\"\n\t* failed to send transaction to collection node at collection-029.mainnet15.nodes.onflow.org:3569: rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial tcp: lookup collection-029.mainnet15.nodes.onflow.org on 169.254.169.254:53: no such host\"\n\t* failed to send transaction to collection node at collection-014.mainnet15.nodes.onflow.org:3569: rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial tcp: lookup collection-014.mainnet15.nodes.onflow.org on 169.254.169.254:53: no such host\"\n\n"

Any idea why this could be happening? This error is triggered only when submitting a transaction.

[Ronak-59]

Quick follow-up:

On retrying/resubmitting the transaction, it went through so we can't replicate this anymore but would still like to understand why this would've happened and best-practices to avoid/handle this?

[Ronak-59]

Further follow-up:

Happens again with next transaction even with multiple retries. I'll try to submit transaction some time later and will provide an update.

[latenssi]

Hi @Ronak-59! Based on the error message that seems like a DNS problem. Are you sure your network is running properly?

[Ronak-59]

Hi @latenssi, apologies for the delayed response. Yes, the network didn't have any issues. Could this error happen if the Flow nodes have network issues?