Hi,

Can you please clarify what you mean by an “answering address”?

You could possibly mean the “EndpointUrl” that is returned in the EndpointDescriptions e.g. during CreateSession service call. Assuming so, our take on that has been that it basically serve no purpose and should be ignored. Clients should use the original connection address they used in the first place, this allows them to e.g. work in environments where the server is behind a NAT.

There is no intended way to configure it, hostnames have been de facto thing to used in EndpointUrls for like the past 15-20 years.
It should be noted that in our implementation at least it doesn’t mean anything vs. what network interfaces are being listened to: by default they are all listened via ip wildcard.

Though, it should be noted that we try to resolve the FQN version of the hostname. So, if you configure your hosts file such that a reverse-dns (because that is how it works in java) would produce an IP address, it might appear there. Or if you somehow make it so that the hostname is already an IP address it might as well, though these should be considered as tricks, not intended ways.