Comment 11 for bug 1960587

That goes to mapping of Erlang 25672 port and we used really a hack rather then documented option to bind it to management ip. And what goes from my testing is that all tools suppose this port to be accessible through hostname.

Yes, other way would be to disallow using such hosts entries, and yes we don't have them in containers, but tbh I don't see why we need 25672 to be binded to management ip only. Unless there's another rabbit cluster or some other Erlang app on same host, but should be binded to different ip.

I eventually had patch to drop such record in decent way, but that results easily in fqdn change, which can bring other problems.