From d8080c27d5b21694b45eaa818e07ada25a888dca Mon Sep 17 00:00:00 2001 From: Brian Shumate Date: Thu, 29 Sep 2016 12:42:22 -0400 Subject: [PATCH] correction --- website/source/intro/getting-started/join.html.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/source/intro/getting-started/join.html.markdown b/website/source/intro/getting-started/join.html.markdown index eb28ee3272..b0a8f7d32e 100644 --- a/website/source/intro/getting-started/join.html.markdown +++ b/website/source/intro/getting-started/join.html.markdown @@ -57,7 +57,7 @@ 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 all other nodes in the cluster. While a `bind` address is not strictly necessary, it's always best to provide one. Consul will by default attempt to -listen on the first private IP on a system, but will fail to start with an +listen on all IPv4 interfaces on a system, but will fail to start with an 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.