Change logic for hostname resolution #5670
Comments
6 tasks
jwilder
added a commit
that referenced
this issue
Feb 17, 2016
This fixes several issues related to the bind address and hostname: * Allows bind addresses where a hostname or IP is not specified to work correct and bind to all interfaces by default. * Fixes the top-level "hostname" config option to allow overridding all bind address hostnames. This allows a node to advertise a different hostname than what is defined in the bind address setting. * Adds the -hostname command-line option back to allow specifing both -join and -hostname as command-line flags. * Enforces a configuration precedence and overriding ability defined as config file is overridden by env vars which are overriden by command-line flags. Fixes #5670 #5671
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We need to have a consistent way of determining hostname for all of our services when they start up. Currently you can specify the hostname in the config, but when you specify a bind address with just a port, it doesn't pick up that host name in all services.
Also, we should bind to
0.0.0.0instead oflocalhostor127.0.0.1if no hostname is specified.The text was updated successfully, but these errors were encountered: