Client constructor fails if the target host name is not resolvable

Client constructor fails if the target hostname is not resolvable, which IMO is not a desired behavior.
In the dynamic environments (like containers) hostname -> IP mapping can change very fast and sometimes at the construction time the target host name is really not resolvable, but IMO it should be tolerated by the constructor.
Besides the actual mapping can change during runtime, so not sure if static hostname -> IP address resolving makes sense at all.

Locate the Java client constructor and reproduce the failure with a hostname that cannot be resolved at construction time. Determine the current hostname-resolution behavior; done means construction tolerates a temporary DNS failure and the resulting behavior is covered by tests.

Written by the indexing model from the issue text.