|
|
@ -56,9 +56,10 @@ command-line option](/docs/agent/options.html#_node).
|
|
|
|
We will also specify a [`bind` address](/docs/agent/options.html#_bind):
|
|
|
|
We will also specify a [`bind` address](/docs/agent/options.html#_bind):
|
|
|
|
this is the address that Consul listens on, and it *must* be accessible by
|
|
|
|
this is the address that Consul listens on, and it *must* be accessible by
|
|
|
|
all other nodes in the cluster. While a `bind` address is not strictly
|
|
|
|
all other nodes in the cluster. While a `bind` address is not strictly
|
|
|
|
necessary (Consul will by default listen on the first private IP on a
|
|
|
|
necessary, it's always best to provide one. Consul will by default attempt to
|
|
|
|
system), it's always best to provide one. Production servers often have
|
|
|
|
listen on all IPv4 interfaces on a system, but will fail to start with an
|
|
|
|
multiple interfaces, so specifying a `bind` address assures that you will
|
|
|
|
error if multiple private IPs are found. Since production servers often
|
|
|
|
|
|
|
|
have multiple interfaces, specifying a `bind` address assures that you will
|
|
|
|
never bind Consul to the wrong interface.
|
|
|
|
never bind Consul to the wrong interface.
|
|
|
|
|
|
|
|
|
|
|
|
The first node will act as our sole server in this cluster, and we indicate
|
|
|
|
The first node will act as our sole server in this cluster, and we indicate
|
|
|
|