Interface selection for sockets bound to 0.0.0.0 is very likely to fail

Have two hosts DC and SL.
When SL has its management interface bound to 0.0.0.0 (<any-ip-address> ) and it is connecting to the DC, it is sending its IP address to the DC, so that this knows how to talk to the SL.

Now as the mgmt-interface is bound to 0.0.0.0, the server picks one IP address "randomly" and is very likely to pick one interface that has no route to the DC, thus making all interaction with the DC impossible.