[Bug] graph-node won't start if DNS does not resolve

[matthewdarwin]

Bug report

We use consul (https://www.hashicorp.com/products/consul) to manage DNS for our RPC servers. Consul will add/remove DNS entries based on health status of RPCs. If all the RPCs are unhealthly the DNS query will return no results.

If the DNS returns no results, graph-node fails to start.

Graph-node should start even if DNS is not resolvable and attempt to resolve IP address from time-to-time just as it normally should do for any other service.

Note: IP addresses change over time. DNS should be re-resolved on a periodic basis anyway.

Relevant log output

No response

IPFS hash

No response

Subgraph name or link to explorer

No response

Some information to help us out

• Tick this box if this bug is caused by a regression found in the latest release.
• Tick this box if this bug is specific to the hosted service.
• I have searched the issue tracker to make sure this issue is not a duplicate.

OS information

None

[github-actions]

Looks like this issue has been open for 6 months with no activity. Is it still relevant? If not, please remember to close it.