When the ip address changes for the hostname EthSigner continues to use the original ip address even when using a custom hosts file.
These are the details we have from Kaleido:
"we are investigating an issue where web3j HTTPService object is not aware of IP changes in the target node, this means when using EthSigner with a remote downstream node using a hostname, and the node’s IP has changed, EthSigner still tries to contact the original IP address. we tell JVM to use a custom hosts file, which has been updated on the container where EthSigner is running. but that’s not getting picked up. I’m looking into a fix in web3j, but want to give you a heads up in case this is a known problem that is being investigated elsewhere"